Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

How to Extend the AuthoringModeUIService Implementation (AuthoringUIModeServiceImpl)

bethtia
Level 1
Level 1

We have an upgraded AEM version 6.4.8.4 and still have a  lot of  pages built from classic templates.  We now have a growing number of pages built from touch UI templates.  We have this request from authors to have the smarts to open a page correctly on either the classic or touch ui mode. We cannot set the authoring mode site-wide nor by user preference.  We are trying to see if we can extend this authoring mode service to look at the template of the page and set the mode to touch or classic accordingly.  How should I go about this implementation?

 

 

1 Accepted Solution
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

One of the approaches would be, redirecting user to classic UI via custom SlingFilter if a page created using a classic template.

View solution in original post

3 Replies
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

One of the approaches would be, redirecting user to classic UI via custom SlingFilter if a page created using a classic template.

View solution in original post

bethtia
Level 1
Level 1
Hi Arun - Please confirm my understanding: we will set the authoringmode sitewide to touchui and add custom sling filter to check if a page is created using a classic template?
Arun_Patidar
Community Advisor
Community Advisor
yes, you can restrict filter based on path e.g. /editor.html/content/group/yoursite and redirect to /cf#/content/group/yoursite if criteria met