Page property issue

[AryaBa1]

Hey, is anyone else facing an issue where the page properties dialog in AEM doesn’t open after migrating to AEMaaCS? It just shows a blank overlay and nothing loads.

[SantoshSai · Accepted solution]

Hi @AryaBa1,

I’ve seen that happen - in my opinion, it’s usually tied to either missing clientlibs or some JavaScript error in the cq.authoring.dialog layer. A few things you could check:

1. Browser console errors - anything failing like a missing .js or .css file?

2. Policy inheritance or broken cq:dialog node - if the dialog node is missing or misconfigured, the overlay opens but nothing renders.

3. Custom clientlibs not loading? If you’ve overridden or added clientlibs for dialogs, make sure those are properly included and categorized under cq.authoring.dialog.

Also, make sure the page component is extending a core component correctly - especially if you’re using proxy components.

If you share a snippet of your component structure or any console logs, I’m happy to take a look with you.

Hope that helps you!

Regards,
Santosh

[AryaBa1]

Yes, it did work! Thanks a lot - the issue was indeed due to the broken page properties dialog. Turns out there was a JavaScript error in the console "Uncaught TypeError: Cannot read properties of undefined" that was preventing the dialog from rendering properly. Fixing that resolved the problem. Appreciate the help!