AEM 6 Overlay Page Dialog | Community
Skip to main content
Level 8
October 16, 2015
Solved

AEM 6 Overlay Page Dialog

  • October 16, 2015
  • 1 reply
  • 1392 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by msullivan-r2i

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:content

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.

1 reply

msullivan-r2i
msullivan-r2iAccepted solution
Level 2
October 16, 2015

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:content

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.