Migrating Content Manager extensions to the Add-ons feature
The Add-ons feature, introduced in SDL Tridion Sites 9.1, lets you combine one or more extensions to the product into a package, an Add-on, which represents a complete functional addition to the product. If your implementation still contains extensions that don't use the Add-ons feature, RWS recommends that you migrate your extensions into one or more such Add-on packages.
The Add-ons feature makes it easier to manage your extensions:
- Extensions that are functionally interdependent (for example, a GUI extension and an Event Handler that jointly add some functionality to Content Manager) can be combined into a single Add-on.
- Managing Add-ons (uploading, updating, configuring with a separate configuration file) is more user-friendly thanks to the Add-ons user interface.
Content Manager extensions that are not deployed through the Add-ons feature will continue to work but the way they are deployed is deprecated. RWS recommends that you migrate your extensions in the following way:
- Remove Content Manager extensions from their old configuration locations (taking care to back up how you configured them).
You can find the configurations in the following locations:
Extension Path to configuration file (relative to %TRIDION_HOME%)Configuration location Event Handler config\Tridion.Content.Manager.config <extensions>sectionCustom Resolver config\Tridion.Content.Manager.config <resolving>sectionGUI extension web\WebUI\WebRoot\Configuration\System.config <Editors>or<Models>section (or both) - Create one or more Add-on packages (ZIP files) containing one or more Extensions each (applying the same configuration)
- Add a manifest file to each package.
- Upload the packages to the product using the Add-ons user interface.
Refer to the installation and implementation documentation for Add-ons for more information.