Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.

Issue in quick publish using aem sites console

Avatar

Level 5

Hi all,

I'm currently using the AEM 6.5.17 and trying to publish the page via sites console by using the quick publish option but when i try to publish a page i'm getting this below error, and the current page is in locked state is it possible to publish the page without unlocking it? or is it the default behaviour of aem?

 

image.png

 

 

Thanks

Nandheswara

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

3 Replies

Avatar

Community Advisor

Hi @Nandheswara ,

Lock page feature is to prevent any modifications by other users ( apart from owner) to get published.

So you need to either ask the owner or person who locked the page to publish it or unlock it .

Ref : https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/classic-ui/authoring/....

 

Thanks

Himanshu Jain

Avatar

Employee Advisor

Hi Team,

Permissions:
- Ensure the user has the necessary permissions (e.g., replicate and modify).
- Check page node permissions in CRX/DE for the relevant users or groups.



 Locked by another user:
- If the page is locked by another user, only that user or an administrator can unlock it.
- Inspect the lock status through the page properties or the `jcr:lockOwner` property in CRX/DE.

Force Unlock:
- If the page is stuck in a locked state (due to a process crash or other issues), an administrator can manually remove the lock by:
- Navigating to the page node in CRX/DE.
- Deleting the `jcr:lockIsDeep` and `jcr:lockOwner` properties from the node.

Regards,

Manvi Sharma

Avatar

Level 3

Hi @Nandheswara , There could be a multiple trouble-shooting steps you can try:

1) Ask the page owner to publish the page.

2) Ask owner to unlock it, Make sure you have replicate permissions for template -> then  you can publish page as well as template policies.

3) Or else get Modify permissions to the page to unlock and publish it.

 

Try anyone of these steps to fix your issue.