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

How does one switching from classic UI to touch UI?

Avatar

Level 2

I was asked to configure our CQ v5.6.1 authoring instance so that it would always land an author in the classic UI.  I did that via the appropriate configuration change in Felix configurations.  Now there are a couple of authors that want to explore use of the touch UI.  Is there a way for a user whose already in the classic UI to get back to the touch UI?

I have read in the documentation that authors have functionality to configure there own personal preference for their UI but it seems to me the only access to that functionality is through the touch UI which my current set-up is set to more-or-less ensure no author sees.

I already asked if they just would rather I set the instance wide default back to the touch UI but the answer was no because they don't want to have to educate all the authors as to how to work with the touch UI even if it's just to show them how to get out of it or set their default personal UI preference.  I did tell them that I'm kind of getting the feeling that there might not be a way for an author forced to the classic UI by and instance level directive to get back to the touch UI and that might be by design.  Some organizations using AEM might not want anything to do with the touch interface and those folks would need a configuration that eliminates any chance of an author ever getting into the touch UI but... I said I'd at least put the question to the Adobe AEM forum so here I am with that question.  Is there a way for a user whose already in the classic UI to get back to the touch UI?

1 Accepted Solution

Avatar

Correct answer by
Employee

I may have misunderstood, but you can always point directly to http://localhost:4502/projects.html

Authors can bring up the new touch page editor manually by swapping 'cf#' for 'editor.html' in the URL. For example:

Classic: http://localhost:4502/cf#/content/geometrixx-outdoors/en.html

Touch: http://localhost:4502/editor.html/content/geometrixx-outdoors/en.html

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

I may have misunderstood, but you can always point directly to http://localhost:4502/projects.html

Authors can bring up the new touch page editor manually by swapping 'cf#' for 'editor.html' in the URL. For example:

Classic: http://localhost:4502/cf#/content/geometrixx-outdoors/en.html

Touch: http://localhost:4502/editor.html/content/geometrixx-outdoors/en.html

Avatar

Level 2

Bruce Lefebvre wrote...

I may have misunderstood, but you can always point directly to http://localhost:4502/projects.html

Authors can bring up the new touch page editor manually by swapping 'cf#' for 'editor.html' in the URL. For example:

Classic: http://localhost:4502/cf#/content/geometrixx-outdoors/en.html

Touch: http://localhost:4502/editor.html/content/geometrixx-outdoors/en.html

 

I was thinking more a UI artifiact some where in the classic UI that took you over to the touch UI something like the touch UI has that little icon you click to the right of the left hand menu items BUT... I think this will work for our purposes.  The two authors that want to play with the touch interface can just learn to fiddle with the URL to get there.  Thank you....