|
Group: Forum Members
Last Active: Wed 18 May 2016
Posts: 12,
Visits: 145
|
On our Cactushop websites we had added a selection tick box to the left of each order in the orders list screen which enabled us to select multiple orders at a time and perform an action against them e.g. print off invoices.
This was particularly useful during busy periods, you can imagine if you get 100 orders over a weekend, going into each order to print off each invoice could take a long time.
What we also found useful was being able to select multiple orders and then printing off an abbreviated picking list so someone could easily pick the products from the warehouse without trawling through a pile of invoices, we even added warehouse locations to the products so the picking list could be sorted in location order.
With Cactushop, the problem we found with making such major changes to the code meant whenever a new version of Cactushop came out we had a lot of work to do to adapt it.
So with Kartris we are keen if possible to restrict our changes to the skins.
Is there any chance of a multiple order select box ?
|
|
Group: Administrators
Last Active: Tue 10 Sep 2024
Posts: 807,
Visits: 2,748
|
There is batch processing of orders to let you change/update the status of multiple ones in one go. Select 'batch process' under the 'orders' menu. At present you cannot export to a file, but it could be possible to add something like that in from what is already there.
Regarding mods, the nature of ASP.NET makes it far easier to separate code out than in the old classic ASP. Where possible, when we write custom code for particular web sites, we modify or create new user controls for this. If they are new ones, we generally put them into the Custom usercontrols folder, to help separate them. If there are SQL changes, we generally script these too. For example, adding extra fields or records can all be scripted so you can easily run the mod on a new Kartris db.
We've had a few sites which we've upgraded from older Kartris to newer versions, and found it far easier to then run the SQL customizations and import the changed code to add the mods back into the new version. The key is to document your changes as you make them so you know which files have changed, to comment changes to existing files with a comment you can easily find such as 'CACTUSOFT MOD' (or whatever your company name is), and also add some description to the comment to describe what it does, why it was customized and any info about other areas it links into.
For db changes, Management studio can help write the script updates, if you right click a table or sproc, you can script to a file or new window a 'CREATE' or 'ALTER'. We then save them on the web in a DATABASE folder, named with date and description of what the script does, eg:
2015-04-08_Extra_field_XYZ_to_Versions_table.sql
Also, Kartris has some design aspects which are useful in developing new features without change database design. For example, object config settings are very useful for mods that previously would require you add a new field to products, categories or versions. Instead, you can create a new object config to hold some new information or setting for any of these, and then use an existing function to retrieve the value. You can script the db change that adds this new object config record.
More info:
http://userguide.kartris.com/Default.aspx?headID=309
One last thing is to use source control if you're not already doing so. This helps you maintain a development history of your site web, so you can roll back changes or view historical changes, as well as providing a good backup. With Visualstudio.com or TFS express, this is now free for small dev teams so there is no excuse not to be using this.
--
If my post solves your issue, can you 'Mark as Answer' so it's easier for other users to find in future.
If you would like to be informed of new features, new releases, developments and occasional special bonuses, please sign up to our mailing list: http://bit.ly/19sKMZb
|