AEM Sites: Rename button in new editor does not rename content fragments
Learn how to resolve the issue where the rename button in the AEM Sites new editor doesn’t rename content fragments.
Description description
Environment
- Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)
- Adobe Experience Manager Sites (AEM Sites) (all versions)
Symptoms
- When content authors attempt to rename a content fragment using the Rename button in the new editor, the operation appears to complete, but the fragment name doesn’t change.
- No error message is displayed.
- However, using the Move function in the Assets view allows the fragment to be renamed, and any name conflicts are flagged for the author to resolve.
- This results in inconsistent behavior between the new editor and the Assets view.
Cause
The Rename action in the new editor starts a background job and reports completion as soon as the job begins, not when it finishes. If the new name is already in use by another fragment in the same folder, the background job fails silently and doesn’t notify the author, resulting in no visible change.
Resolution resolution
Follow the steps below to resolve the issue:
- Open the Assets view in AEM.
- Locate the content fragment you want to rename.
- Select the fragment and choose the Move option.
- In the move dialog, enter the new name for the fragment.
- Complete the move operation. If the new name is already in use, AEM will display a message and allow you to resolve the conflict.
- Verify that the fragment name has changed as expected in the Assets view.
recommendation-more-help
experience-cloud-kcs-help-kbarticles