Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

AEM 6 Overlay Page Dialog

Avatar

Level 8

I have an existing page component in 5.6.1 that overlays the dialog to provide a custom tab.  Moving this over to 6 and using the new UI, the dialog that is rendered is the base page dialog and does not include my new tab and fields.  Anybody know a possible solution to this?

1 Accepted Solution

Avatar

Correct answer by
Level 2

The new dialog interface uses a new format for Dialogs.  By default you can view this at: /libs/wcm/foundation/components/page/cq:dialog

This can be overlayed in the same way as the other dialogs.

You can also preview the dialog because it is a component of type (cq/gui/components/authoring/dialog): http://localhost:4502/libs/wcm/foundation/components/page/_cq_dialog.html/content/geometrixx/en/jcr:...

The part after the _cq_dialog.html/ is a suffix of the page to pull in the properties for.

There is some docs on the Coral UI that is the front-end of this: http://dev.day.com/docs/en/cq/current/touch-ui/coral-ui/

Not sure how to get around the double dialogs for pages.  For components it appears to revert to the Ext JS dialogs if a cq:dialog component isn't present.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 2

The new dialog interface uses a new format for Dialogs.  By default you can view this at: /libs/wcm/foundation/components/page/cq:dialog

This can be overlayed in the same way as the other dialogs.

You can also preview the dialog because it is a component of type (cq/gui/components/authoring/dialog): http://localhost:4502/libs/wcm/foundation/components/page/_cq_dialog.html/content/geometrixx/en/jcr:...

The part after the _cq_dialog.html/ is a suffix of the page to pull in the properties for.

There is some docs on the Coral UI that is the front-end of this: http://dev.day.com/docs/en/cq/current/touch-ui/coral-ui/

Not sure how to get around the double dialogs for pages.  For components it appears to revert to the Ext JS dialogs if a cq:dialog component isn't present.