I know years have passed, but for other people seeing this I will say this. In my experience the system properties have highest precedence for determining runmode. Somewhere above on this page I added a 'full test report' with all my test cases and their results to prove it. So according to my exten...

I am sorry, but it seems that this needs to be verified again by one of your sysadmins as I get the impression that incorrect information is being copied over and over, even in the documentation. It is still like this in https://docs.adobe.com/content/help/en/experience-manager-65/deploying/configur...

Unfortunately I can't attend at that date/time. Will a recording be made available for watching it later? And do you need to register anyway to be able to access it?

I stated in my post "in our project" so ofcourse there is no path in this configuration. The screenshots above are not related to my project and the url I posted points to your own running AEM instance?Furthermore I believe that the screenshots with the black rectangles is flawed in a sense that it ...

Sorry, no not at all. As you normally want this feature active in all runmodes (author and publish) this shouldn't be in a runmode specific folder in my opinion. Even if it was, I stated that it works and doesn't work with 2 urls patterns on AUTHOR.I think I fixed it though. In our project we had an...

HiI am on AEM 6.4 too. For me it is even stranger... I seems to work with a node of type nt:unstructured, but only on AUTHOR instance with a url which contains the /editor.html/ for triggering the authoring widgets in it. If I leave out the /editor.html, the md5 hashes disappear from all the clientl...