Content Fragments don't work anymore after upgrade | AEM 6.4

Пошук

Останнє оновлення: 21 трав. 2021 р. | Також застосовується до Experience Manager 6.3, Experience Manager 6.4

Issue

After upgrading from AEM 6.2 to AEM 6.4, content fragments no longer work.

Environment

6.2 to AEM 6.4 upgrade.

Cause

The upgrade fails to upgrade the custom content fragments.

Resolution

Go to http://aemhost:port/crx/packmgr/index.jsp and log in as admin.
Upload and install the attached package.
Go to http://aemhost:port/crx/de/index.jsp#/apps/tools/components/fixContentFragments
Log in as admin.
Open /apps/tools/components/fixContentFragments/POST.jsp and modify the sling:resourceType that is set by the script.
Go to http://aemhost:port/apps/tools/components/fixContentFragments/run.html
Enter the path you need to run the tool against (not /content/dam/..., the path of the pages referencing the content fragments).
Click start.

The tool outputs all output to the error.log file at INFO level. For example

03.08.2018 22:38:50.000 *INFO* [Thread-1665] org.apache.jsp.apps.tools.components.fixContentFragments.POST_jsp$FixContentFragmentsThread Running content fragments fix.
03.08.2018 22:38:50.547 *INFO* [Thread-1665] org.apache.jsp.apps.tools.components.fixContentFragments.POST_jsp$FixContentFragmentsThread Fixing: /content/aetnacom2/en/health-guide/jacksonville-gardener-ron-pauline/jcr:content/content_section/articleform/descriptionsections
03.08.2018 22:38:52.297 *INFO* [Thread-1665] org.apache.jsp.apps.tools.components.fixContentFragments.POST_jsp$FixContentFragmentsThread fixContentFragments completed, total time: 2297ms