As described on the parent Repository Restructuring in AEM 6.5 page, customers upgrading to AEM 6.5 should use this page to assess the work effort associated with repository changes impacting the AEM Sites Solution. Some changes require work effort during the AEM 6.5 upgrade process, while others can be deferred until a future upgrade.
With 6.5 Upgrade
Prior to Future Upgrade
Previous location | /etc/segmentation/contexthub |
New location(s) |
|
Restructuring guidance | If any new or modified ContextHub Segments are intended to be edited in source control rather than being edited in AEM, they must be migrated to the new location:
The following QueryBuilder query locates all references to ContextHub Segments in the Previous Locations. |
Notes | ContextHub Segments persisted to the previous location display as read-only in AEM > Personalization > Audiences. If ContextHub Segments are to be editable in AEM, they must be migrated to the new location ( AEM Sites Page Properties only allow either the Previous Location ( Any unused ContextHub Segments from AEM reference sites can be removed and not migrated to the New Location:
Note: If ClientContext is in use, it is recommended to convert to ContextHub. |
Previous location |
|
New location(s) | /libs/cq/analytics/clientlibs/analytics |
Restructuring guidance | Any custom use of these Client Libraries should reference the Client Library by category, and not by path:
|
Notes | Editing of these Client Libraries was never supported. To obtain the Client Library categories, visit each
|
Previous location | /etc/designs/wordDesign |
New location(s) |
|
Restructuring guidance | For any Designs that are managed in SCM, and not written to at run-time via Design Dialogs.
For any Designs that NOT managed in SCM, and modified run-time via Design Dialogs:
|
Notes | N/A |
Previous location |
|
New location(s) |
|
Restructuring guidance | Any new Mobile Device Emulator Configurations must be migrated to the New Location.
|
Notes | Mobile Device Emulator Configurations resolution occurs in the following order:
|
Previous location | /etc/blueprints |
New location(s) |
|
Restructuring guidance | Any new or modified Multi-site Manager Blueprint Configurations must be migrated to the New Location (
|
Notes | All AEM provided Multi-site Manager Blueprint Configurations exist in the New Location in Content does not reference the Multi-site Manager Blue Configurations therefore there are not content references to adjust. |
Previous location |
|
New location(s) |
|
Restructuring guidance | Any new or modified Multi-site Manager Rollout Configurations must be migrated to the New Location.
Remove migrated Multi-site Manager Rollout Configurations from the Previous Location. |
Notes | Failing to remove migrated Multi-site Manager Rollout Configurations from the Previous Location results in duplicate rollout options displayed to AEM authors. |
Previous location |
|
New location(s) |
|
Restructuring guidance | The only supported new Page Event Notification E-mail Templates are to support new locales. Page Event E-mail Template resolution occurs in the following order:
|
Notes | Any new or modified Page Event Notification E-mail Templates must be migrated to the new location under
|
Previous location | /etc/scaffolding |
New location(s) | /libs/settings/
/apps/settings/
|
Restructuring guidance | Scaffolding created under the Previous Location uses the legacy Scaffolding framework and cannot be migrated to the New Location. To align with the New Location any legacy Scaffolding must be re-developed using the supported Scaffolding framework. |
Notes | N/A |
Previous location | /etc/clientlibs/wcm/foundation/grid/grid_base.less |
New location(s) | /libs/wcm/foundation/clientlibs/grid/grid_base.less |
Restructuring guidance | Any references to the Previous Location in custom LESS files must be updated to import from the New Location.
|
Notes | Referencing a non-existing grid_base.less file results in the Layout Mode of the Page and Template Editor not working, and a disruption of page layout. |
Previous location | /etc/designs/<custom-site> |
New location(s) | /apps/settings/wcm/designs/<custom-site> |
Restructuring guidance | For any Designs that are managed in SCM, and not written to at run-time via Design Dialogs.
For any Designs that NOT managed in SCM, and modified run-time via Design Dialogs:
|
Notes | The recommended approach is to build AEM Sites and Pages using Editable Templates which use Structure Content and Policies in lieu of Designs. |
Previous location |
|
New location(s) | /libs/cq/testandtarget/clientlibs/testandtarget |
Restructuring guidance | Any custom use of these Client Libraries should reference the Client Library by category, and not by path.
|
Notes | Editing of these Client Libraries was never supported. To obtain the Client Library categories, visit each cq:ClientLIbraryFolder node via CRXDELite and inspect the categories property:
|
Previous location |
|
New location(s) | /libs/wcm/foundation/clientlibs |
Restructuring guidance | Any custom use of these Client Libraries should reference the Client Library by category, and not by path.
|
Notes | Editing of these Client Libraries was never supported. To obtain the Client Library categories, visit each
|