Hi,
Not sure if this is a good idea, but if you're using a dispatcher you might have luck to shut the door by denying access to /editor.html. Seems a little harsh IMHO.
/0091 { /type "deny" /glob "GET /editor.html/*" }
Probably a more elegant solution would be to have a apache rewrite rule to control access to the editor url.
You could also overlay the component responsible for the editor, /libs/cq/gui/components/authoring/editor. By overlaying the editor component's head.jsp script you could create a redirect here to whatever page you like.
<%@page session="false" import="com.day.cq.wcm.api.AuthoringUIMode, com.day.cq.wcm.api.AuthoringUIModeService"%><% %><%@taglib prefix="cq" uri="http://www.day.com/taglibs/cq/1.0"%><% %><cq:defineObjects /><% %><head> <% String suffix = slingRequest.getRequestPathInfo().getSuffix(); AuthoringUIModeService authoringUIModeService = sling.getService(AuthoringUIModeService.class); String editorUrl = authoringUIModeService.getEditorURL(AuthoringUIMode.CLASSIC); String url = editorUrl + suffix; String xssUrl = xssAPI.getValidHref(url); response.sendRedirect(url); %> </head>
Essentially you can do whatever you like at this point, redirecting to the classic mode is just one example. I hope there is something here that you can utilize for your environment.
Cheers!
