Moving a page to rename, but AEM reverts the name back to original | Adobe Higher Education
Skip to main content
May 27, 2020
解決済み

Moving a page to rename, but AEM reverts the name back to original

  • May 27, 2020
  • 3 の返信
  • 4274 ビュー

I am trying to rename a page by using the move function and changing the 'name' field. When I change the name, click 'Next', the 'Move' button is greyed out. 

When I click back, the name still appears as changed. But I am unable to proceed. 

I tested moving the page to another location and the name didn't change. 

How do I fix this issue? I've renamed pages using this method before with no issues. 

このトピックへの返信は締め切られました。
ベストアンサー raghavc

@pduncan please confirm the AEM version you are using.

 

When you try to move a AEM page , the move button will be disabled if the path does not allow the template of the page you are moving to be a child of the page under which you are moving. You would face this issue even if you are moving under the same parent path, if the allowed templates definition of the parent page was changed after the child page was initially created. 

 

 

3 の返信

BrianKasingli
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 27, 2020

@pduncan,

Do you have any custom Workflow launchers enabled? or services like JCR listeners enabled? Maybe automated tasks are adding strange behaviours when pages are renamed, within your AEM instance.

Can you replicate this in a fresh AEM instance on startup, with sample content? let's try to understand if this is the AEM product, or your custom code itself. 

Adobe Employee
May 27, 2020

There were few known bugs with page move/rename feature.

The issues are now resolved in 6.4.8 and 6.5.4. Make sure you test with the latest service packs.

Regards,

Vishu

raghavc
raghavc回答
Level 4
May 27, 2020

@pduncan please confirm the AEM version you are using.

 

When you try to move a AEM page , the move button will be disabled if the path does not allow the template of the page you are moving to be a child of the page under which you are moving. You would face this issue even if you are moving under the same parent path, if the allowed templates definition of the parent page was changed after the child page was initially created.