From here you can restart Kartris. This works by making a minor change to the web.config file and saving it – ASP.NET will restart a site when this file is changed. Therefore it only works if your site has write permissions to the root. If you need to restart Kartris and this does not work, you can manually change the web.config via FTP.

Kartris keeps logs of certain actions by admins such as logins and changes to config settings.

Kartris will log ASP.NET errors within the Uploads/Logs folder. This tab allows you to view these errors more conveniently from the back end of Kartris. In the event an error means the site is unavailable, you can view the error logs via FTP, in the following location:

Uploads/Logs/Errors/

Error logs are created with a .config extension to ensure the raw files cannot be served to web users (even if they know the location and name of a particular log file).

The presence of errors does not automatically indicate an issue with your site. 404s (file not found), cancelled orders and some other events will be recorded, as well as errors due to partially formed pages being submitted (for example, if a visitor has a slow internet connection and only receives part of the page before pushing a button). The logs are designed to be a useful tool to provide information to help resolve issues rather than a digest of problems on your site that need to be resolved.

In Kartris versions up to 1.4xxx, the records in the database are protected from casual deletion or modification by a series of triggers. The various stored procedures that update data disable a trigger, update the data and then re-enable it again.

To edit data within the database either via your own query or directly into the database tables, you will need to disable either the specific trigger(s) protecting that data, or all triggers - this can be done from this section. Typically triggers will be reactivated over time automatically when queries on those tables next fire up, although you can also reactivate all triggers here too.

If you need to modify data in the database directly and the back end is not accessible, or is on error, you can run the following stored procedure instead:

_spKartrisDB_DisableAllTriggers

To find this, expand 'Programmability > Stored Procedures' for your database in SQL Management Studio, and then right click and 'Execute Stored Procedure'. Then click 'OK' on the popup that appears. The 'Results' window should appear with a return value of zero.

This provides an easy way to clear data related to products, orders or sessions. It's important not to attempt to clear data directly from Kartris by just blanking all the tables in the database, as some hold data such as config settings and language strings that is vital to the operation of Kartris.

This provides an easy way to run a query against the database. A non-expert would typically only use this if Kartris support staff provide a query for them to run to perform a task such as to alter the database in some way, or find some information that is required for a support issue.

From time to time, you may need to export data from Kartris to a file. This might be anything from a customer list, order details, product inventory or statistical data for external analysis. Kartris provides both a built-in export for customers/orders, as well as a flexible export system that lets you write your own custom exports and save them within Kartris.