Enable new functionality in migrated themes
When we migrate the themes, migration moves the existing themes to the new server. Migration does not upgrade themes from an earlier version to use new functions introduced in more recent versions of the product.
When migrating modular themes, the modular theme architecture makes it easy to enable new functions in the themes by turning on and off the modules or versions of the modules. For example, to update the theme to use the current version of Dojo, replace the dojoxx.json file in the capabilities folder, where xx is the version number. Your Dojo meta-modules load the newer version of Dojo as specified in the dojoxx.json file.
WebSphere Portal provides an optimized, modular theme architecture from version 7.0.0.2 onward. Non-modular version 6.1.x, such as Portal, PortalWeb2, and Tab Menu - Page Builder themes were deprecated in version 8.0 and are no longer supported in v8.5.
Non-modular version 7.x (Page Builder) themes are still supported on v8.5 but are also deprecated and will be unsupported in the next version of WebSphere Portal. It is either required (6.1.x themes) or recommended (7.x themes) that you upgrade to a modular theme. If we are starting a new project, we must start with a copy of the 8.5 theme. If we must migrate a previous project, the older non-modular themes can physically be migrated. But, we must then manually update the themes to the modular architecture, which allows us to enable any new features. See Update a 6.1.x theme to be modular.
- Migration - Removing the site toolbar in an 8.0 theme
- Migration - Add the v8.5 site toolbar to a version 8.0 theme
- Enable the 8.5 site toolbar
- Update the theme to use simple context menus