Make author instace "Preview as Published" navigateable

jlanssie-lnl · 2022-03-02T14:24:15+00:00

Request for Feature Enhancement (RFE) Summary: We would propose to have an out of the box way to always add the "?wcmmode=disabled" url slug to urls inside the author "Preview as published" environment because without it, we experience custom components breaking in the "Preview as Published". If it was always added, the author instance's "Preview as Published" could be fully navigateable for an author, which is good for demo's to stakeholders or business or testing UX flows. Use-case: An author wishes to test or demonstrate a UX flow to stakeholders on the author's "Preview as Published" to include the most recent visual changes. Current/Experienced Behavior: An author clicks a link on a "Preview as Published" page and is redirected to the correct URL, but without the "?wcmmode=disabled". The new page features components that visually break, visually misbehave or do not load content from content fragments. Improved/Expected Behavior: An author clicks a link on a "Preview as Published" page and is redirected to the correct URL, with the "?wcmmode=disabled". All components on the page render well. The author can gets a perfect visual representation of all components, with the latest changes present. Environment Details (AEM version/service pack, any other specifics if applicable): Adobe Experience Manager 6.5.8.0 Customer-name/Organization name: National Lottery Screenshot (if applicable): Code package (if applicable):

Forum|Forum|4 years ago
March 2, 2022
2 replies
1185 views

Request for Feature Enhancement (RFE) Summary:	We would propose to have an out of the box way to always add the "?wcmmode=disabled" url slug to urls inside the author "Preview as published" environment because without it, we experience custom components breaking in the "Preview as Published". If it was always added, the author instance's "Preview as Published" could be fully navigateable for an author, which is good for demo's to stakeholders or business or testing UX flows.
Use-case:	An author wishes to test or demonstrate a UX flow to stakeholders on the author's "Preview as Published" to include the most recent visual changes.
Current/Experienced Behavior:	An author clicks a link on a "Preview as Published" page and is redirected to the correct URL, but without the "?wcmmode=disabled". The new page features components that visually break, visually misbehave or do not load content from content fragments.
Improved/Expected Behavior:	An author clicks a link on a "Preview as Published" page and is redirected to the correct URL, with the "?wcmmode=disabled". All components on the page render well. The author can gets a perfect visual representation of all components, with the latest changes present.
Environment Details (AEM version/service pack, any other specifics if applicable):	Adobe Experience Manager 6.5.8.0
Customer-name/Organization name:	National Lottery
Screenshot (if applicable):
Code package (if applicable):

C

Cedric_LATIMIER

Employee

Hello @jlanssie-lnl

As mentioned by @anmol_bhardwaj this will have quite a big impact on the current behavior, and will require a large refactoring of the Editor.
Engineering will unfortunately not consider this at this point, so I would recommend you to explore the sling mapping option mentioned above.

Anmol_Bhardwaj

New Participant

Good Idea! Couple of suggestions: - You can add a sling mapping to redirect to ?wcmmode=disabled always in a particular environment, which will behave the same way. - How are you planning to use authoring, is this supposed to be a mode like preview? Just one concern, if something like this happens, it will have a big impact on the already present code which takes leverage of wcmmode=disabled in HTL.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded