Block ClassicUI(cf#) pages to authors and show/redirect them to TouchUI(editor.html) pages for editing content pages. | Community
Skip to main content
Level 2
February 3, 2023

Block ClassicUI(cf#) pages to authors and show/redirect them to TouchUI(editor.html) pages for editing content pages.

  • February 3, 2023
  • 1 reply
  • 1504 views

Hi All,

 

Recently we migrated from ClassicUI to TouchUI and we dont want our authors to edit the content in ClassicUI. So either we need to redirect them to TouchUI editor.html or block/restrict access to cf#. We are doing this because we did not delete the classic dialogs. We kept them and may be at a later point we will delete them. Any solutions is highly appreciated.

 

Thanks

 

cc @indrasenareddy 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Peter_Puzanovs
Community Advisor
Community Advisor
February 3, 2023

Hi Manikanta,

 

First of all we can configure AEM to open in Touch UI by default [1]

 

In addition we can configure Sling Redirect to redirect any request into cf to editor.html

Thus any content author who may have bookmarked old page will be redirected to TouchUI alternative.

 

[1] user interface - AEM 6.2 How to switch from classic UI to Touch - Stack Overflow

 

Regards,

Peter

 

Level 2
February 3, 2023

hi @peter_puzanovs ,

We already did [1]. Now we are looking for sling:redirect solution. I tried to implement in my local but not working.

Below is the screenshot

 

Peter_Puzanovs
Community Advisor
Community Advisor
February 7, 2023

Hi Manikanta,

 

Would suggest,

 

sling:match="(.*)cf#(.*)"

sling:redirect="http://localhost:4502/editor.html$2"

 

Regards,

Peter