Custom code deactivation
When troubleshooting a Content Manager issue, first deactivate your own code or third-party code to rule out any issue that may be caused by it.
The main extension areas in Content Manager are:
- Event System
- You may have written custom Event Handler code to catch and respond to certain events. Remove these Event Handlers to rule them out as a possible cause of your problem.
- Core Service
- If you have custom code interacting with the Core Service, deactivate that code and see if the problem keeps occurring.
- Templates
- Could your template code be responsible for the problem? Start by removing any calls to third-party software or back-office systems. If your problem persists, try using one built-in default Templates that SDL Tridion ships with. If your template code does turn out to cause the problem, remove as much code as possible to zoom in on your problem.
- Legacy components (TOM)
- If you have upgraded from an older version of SDL Tridion, you may still be using legacy components such as the TOM API or the TOM-based Event System. Make sure to disable these, too. Using the old TOM-based Event System and the new TOM.NET-based Event System at the same time can also cause unexpected behavior.