Configuring after the upgrade
Depending on your upgrade scenario, you may need to perform some configuration tasks after the upgrade. This section lists those tasks. Note that after you have completed these tasks, you must instruct users of the Content Manager Explorer interface to clear their Internet cache
- Reconfiguring the Content Manager Explorer website
Several steps may be required to restore Content Manager Explorer. - Reinstating your logging directory for the Transport Service
Running the installer has set the logging directory for the Transport Service to a new default value: a new logs\ subfolder within the bin\ subfolder of %TRIDION_HOME%. If you want to change this new default value, or if you want to reinstate your old logging directory, modify the logback.xml file. - Updating default Template Building Blocks in your Templates
Because some default Template Building Blocks have changed, you need to update the default Template Building Blocks in the Templates you have created for your Experience Manager implementation. Only do this if you intend to migrate to the new publishing framework (using Topology Manager). If you intend to keep using the deprecated old publishing framework (using Publication Targets), ignore this topic. - Restoring FormatAreaStyles.css
Because the file FormatAreaStyles.css has moved to a new location, restore your original from your backup location to %TRIDION_HOME%\web\WebUI\Editors\Base\Configuration\. - Hiding workflow-related GUI controls after upgrade
As of SDL Tridion 2013, by default, the Content Manager Explorer and Experience Manager GUIs show a Things To Do panel, used for workflow-related functionality. If you do not use, nor intend to use, workflow in your implementation of SDL Tridion Sites, you can hide this panel. - Showing the Publishing Management node
As of SDL Web 8, the old publishing framework has been deprecated in favor of a new one, and as a result, the Publishing Management node in the Administration tab of Content Manager Explorer is hidden by default. You can make it appear again by changing a configuration setting. - Indexing or reindexing search after the upgrade
After your upgrade, (re)indexing of the search index is required. - Content configuration after an upgrade
After an upgrade of the Content Manager Explorer from an earlier version, you may need to perform one or more tasks to configure content in the system. Whether you need to perform a individual task depends on the specific upgrade scenario. - Enabling high-availability storage for Import Export service items in a scaled-out Content Manager setup
If you are upgrading a system in which your Content Manager instance is scaled out, enable high-availability storage for import package, export packages and undo packages produced by the Import Export service. - Upgrading Safeguard
If you were using Safeguard (now a deprecated feature), the upgrade has removed this feature from your system. If you nevertheless want to continue using it, refer to the separate SDL Tridion Sites legacy documentation to learn how to request an installer and install it again. - Re-enabling user interface tracing
Prior to SDL Tridion Sites 9.1, user interface tracing was switched on by default. This release removes UI tracing configuration, because it could cause performance degradation. Only if you have pressing reason to do so, re-enable tracing by editing the file Web.config in the web\WebUI\WebRoot\ subfolder of %TRIDION_HOME%. - Reconfiguring the Monitoring feature after the Content Manager server upgrade
If you use the Monitoring feature, update the Monitoring configuration file on the Content Manager server.