Unable to open properties in a page and Unable to edit a component | Community
Skip to main content
sai_santhosht50
Level 2
May 14, 2020
Solved

Unable to open properties in a page and Unable to edit a component

  • May 14, 2020
  • 4 replies
  • 7700 views

1) When i click on "open properties" am redirecting to page which contains error.

 

Error:- 

Cannot serve request to /mnt/overlay/wcm/core/content/sites/properties.html in /libs/granite/ui/components/foundation/form/field/field.jsp

 

2) when i try to click on configure of a component, dialog box is not opened and i can see an error in console.

 

Error:- Cannot serve request to /mnt/override/apps/componentpathl/_cq_dialog.html/pagepath/jcr:content/par/carousel in /libs/granite/ui/components/foundation/form/field/field.jsp

 

aem- v6.4.5

acs-aem commons- v3.17.4

How to overcome these errors?

Thanks in advance.

 

Best answer by Shashi_Mulugu

@sai_santhosht50 from two errors i can see the issue reported is with /libs/granite/ui/components/foundation/form/field/field.jsp. Can you please check if you have overrided any nodes related to that field.jsp

4 replies

Ankur_Khare
Community Advisor
Community Advisor
May 14, 2020

Make sure your custom code is not overriding any custom node.

Have you try to override any node?

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity AdvisorAccepted solution
Community Advisor
May 15, 2020

@sai_santhosht50 from two errors i can see the issue reported is with /libs/granite/ui/components/foundation/form/field/field.jsp. Can you please check if you have overrided any nodes related to that field.jsp

September 27, 2023

@sai_santhosht50  This issue is commonly observed if one of the cq:Page has missing/no jcr:content node.

April 10, 2024

How to resolve this issue. I mis-spelled  the sling:resourceType in crxde while creating content root. Now When I am creating it, opening page properties throwing error.

pavrda
Level 4
January 27, 2025

In my case, the error occurred in the "Advanced" tab of the page properties for a newly generated project. I discovered that my page components were using the "sling:resourceSuperType" value "core/wcm/components/page/v3/page". When I downgraded the version to "core/wcm/components/page/v2/page", the error disappeared.