Best practices for debugging browser-based GUIs
The tables in this topic describe some common bugs that might occur in Content Manager's browser-based user interfaces along with the typical causes in each areas and the tools you use to fix the bugs.
Basic best practices
- Test on different browsers
-
Check if your problem also occurs if you use a different browser.
-
Use
mode=jsfor the Classic GUI -
If the Classic user interface (Content Manager Explorer and Experience Manager) is only partially rendered and/or shows errors in the Info Bar, add the property-value pair
mode=jsto the query string or your URL to reveal errors that are otherwise not displayed. - Check logs
-
You can check the following logs to zoom in on the cause of your problem:
Log name Location Content Manager Explorer server log %TRIDION_HOME%\web\WebUI\WebRoot\*Tridion.Web.trace IIS server log %SystemDrive%\inetpub\logs\LogFiles\WEBSITEID, where WEBSITEID is the ID of the website Tridion Sites Windows Event Logs - %SystemRoot%\System32\Winevt\Logs\Tridion.evtx
- %SystemRoot%\System32\Winevt\Logs\Tridion Content Manager.evtx
- Check your configuration files
- If you modified configuration files, such as System.config in the web\WebUI\WebRoot\ subfolder of your Content Manager root location, check your configuration changes to see if they are correct. Try reverting them or commenting them out, and check if your problem reoccurs.
Bugs related to JavaScript on the webpage
| Types of error | Causes | Tools to use |
|---|---|---|
|
|
|
Bugs related to the Content Manager server
| Types of error | Causes | Tools to use |
|---|---|---|
|
|
|
Bugs related to communication between the webpage and the server
| Types of error | Causes | Tools to use |
|---|---|---|
|
|
|