Content Fragments fail to save in AEM 6.5.2 LTS after migration due to /libs folder overwrite
Content Fragments cannot be saved in Adobe Experience Manager (AEM) 6.5.2 LTS after a repository migration when the /libs folder is overwritten. To fix the issue, exclude the /libs folder during migration or restore it to its original state.
Description description
Environment
- Adobe Experience Manager 6.5.2 LTS (Author instance)
Issue/Symptoms
- Saving Content Fragments fails for both migrated and newly created fragments and models.
- You could see the following error: com.adobe.cq.dam.cfm.impl.servlets.ContentPostServlet$UpdateException: No element ‘variationTagIds’ defined.
Cause
Including the /libs folder in the repository migration overwrites essential system files, resulting in missing or incompatible definitions required for Content Fragment operations.
Resolution resolution
To fix the the issue, follow these steps:
-
Review your repository migration process to determine if the
/libsfolder was included in the migration. -
When running the oak-upgrade command for repository migration, ensure that the /libs folder is excluded to prevent overwriting system-provided files. For example:
- java -jar oak-upgrade.jar --exclude-paths /libs [ other options] -
If the
/libsfolder was already migrated and overwritten, restore your AEM instance from a backup taken before the migration, or perform a clean reinstallation of the product to ensure the/libsfolder contains only the original system files.- Warning: Restoring from backup or reinstalling will overwrite any changes made since the backup or installation. Ensure you have a current backup of your content and configurations before proceeding.
-
After restoring or reinstalling, create or edit a Content Fragment and verify that the save operation completes successfully.