The Debug tab can be used for system debugging, i.e. finding and fixing performance or settings issues on your website. Debugs are also particularly useful in case that you are reporting an issue to our support department. Every extra bit of information related to your issue that you find in the debugs can significantly shorten the time needed to solve the issue.
The debugging interface is divided into several sub-tabs. Only the following two tabs are displayed by default. Click the name of the tab to learn more.
The other sub-tabs are displayed only after adding a dedicated key into the AppSettings section of your web.config file. Here again, click the name of the tab to get detailed information.
You can also add one of the following bulk keys to the AppSettings section of your web.config file in order to enable all the debugs with a single key.
|•||<add key="CMSDebugEverything" value="true"/> - enables all debugging sub-tabs in the administration interface|
|•||<add key="CMSDebugAllForEverything" value="true"/> - enables all debugging sub-tabs, while UI operations are debugged too|
|•||<add key="CMSDebugEverythingLive" value="true"/> - enables all debugging on the live site (the debug log will be displayed at the bottom of the page)|
|•||<add key="CMSDebugEverythingLogLength" value="20"/> - limits the maximal length of the debug log (number of preserved log records)|
|•||<add key="CMSLogEverythingToFile" value="true"/> - logs all possible operations (including Event log and E-mail sending log) into .log files stored in ~/App_Data/|
These keys enable all the debugs listed above, while the dedicated keys for particular debugs have higher priorities. This means that you can for example enable all debugs using CMSDebugEveryting with the value set to true and hide one particular sub-tab by using its dedicated key with the value set to false at the same time.