the properties of pages is disabled

Hi @elmopro ,

If the properties of pages are disabled in Adobe Experience Manager (AEM) and you are unable to edit the properties of any page, there could be several reasons for this issue. Here are some common troubleshooting steps and solutions to address this problem:

1. Check Permissions

Ensure that you have the necessary permissions to edit page properties:

1. Access Control Lists (ACLs):

   • Go to Tools > Security > Users (or Groups).
   • Find your user or group and check the permissions assigned to them.
   • Make sure the user or group has read, modify, and create permissions on the relevant paths.

2. Permissions on the Page:

   • Navigate to the page in the CRXDE Lite (http://localhost:4502/crx/de).
   • Check the permissions set on the page node (jcr:content).
   • Ensure that your user or group has the appropriate permissions on the jcr:content node of the page.

2. Check for Locks

Ensure that the page is not locked by another user:

1. Navigate to the Sites console.
2. Find the page and check if there is a lock icon next to it.
3. If the page is locked, you might need to unlock it using the Lock button in the Page Information menu, or ask the user who locked it to unlock it.

3. Check the Page Template Configuration

Ensure that the page template allows property editing:

1. Template Configuration:

   • Navigate to Tools > General > Templates.
   • Find the template used by your page.
   • Ensure that the template has the correct policies and configurations to allow property editing.

2. Page Properties Dialog:

   • Check if the dialog for editing properties is correctly configured in the template.
   • Ensure that all necessary fields are included and that there are no errors in the dialog configuration.

4. Inspect Page Policies and Policies Configuration

Ensure that policies assigned to the template or the page do not restrict editing properties:

1. Editable Templates:

   • Navigate to Tools > Templates > Policies.
   • Check the policies assigned to the template used by your page.
   • Ensure that the policies do not restrict editing page properties.

2. Page Component Configuration:

   • Inspect the page component configuration in the template editor.
   • Ensure that the component allows editing the necessary properties.

5. Check for Customizations or Overlays

Custom code or overlays might be affecting the ability to edit page properties:

1. Custom Components:

   • Review any custom components or scripts that might be overriding the default behavior of the page properties dialog.
   • Check if there are any overlays of the page properties dialog in /apps or /libs.

2. Error Logs:

   • Check the AEM error logs for any errors that might be related to editing page properties.
   • Look for any stack traces or error messages that can provide clues.

6. Verify Configuration in OSGi Console

Ensure that OSGi configurations are correctly set up:

1. Go to the OSGi console (http://localhost:4502/system/console/configMgr).
2. Check relevant configurations like:
   • Day CQ WCM Page Manager Factory.
   • Adobe Granite Page Manager Configuration.
3. Ensure that these configurations are not restricting property editing.

Example: Enabling Permissions via ACLs

Here’s how to set permissions via ACLs:

1. Navigate to http://localhost:4502/crx/explorer/index.jsp.
2. In the CRX Explorer, go to Access Control.
3. Select the path where your pages are located (e.g., /content/my-site).
4. Add your user or group.
5. Set the permissions to read, modify, and create.
6. Save the changes.

Example: Unlocking a Page

1. Go to the Sites console (http://localhost:4502/sites.html).
2. Navigate to the page that is locked.
3. Click on the page and open the Page Information menu.
4. Click Unlock.

By following these steps, you should be able to identify and resolve the issue preventing you from editing page properties in AEM. If the problem persists, consider reaching out to your AEM administrator or support team for further assistance.

@elmopro 

Do you have any components associated with these pages?

Do you see these issues happening on we.retail as well?