Maybe try something like this for the glob:/content/dam(/.*/)renditions/original(/.*\.zip)

I can't offer a fix because i don't believe there is one for this issue (it get's posted a lot), but, a somewhat work around to make this easier on your authors would be to add a "Preview" link to the page some where, maybe affixed to the footer, that when clicked opens the current page URL with ?wc...

That is correct.

Remove the "value=true".  This sets the value every time.

This is an AMS test to make sure the servers are running correctly, it's part of their health check.  Typically when we do a release with AMS, we have them change the health check to an actual page, rather than a non-existent page for the exact reason you've posted about.They do sometimes push back ...

Thanks Sam.  The code in there is actually pretty much what I have, and that too does not persist the login after the browser is closed.

Sorry for the late reply here.  A cookie is created "login-token" but it's a session cookie, so when the browser closes out, the cookie also goes bye bye.  I need to change this to keep the cookie.

This is because when you include it that way, the "text" resource is technically null and not available.  Since you're including it in your page component, modify the associated template and pre-set the text node.  Example:<?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.ap...

It's just using the standard AEM login by posting to j_security_check.  We don't have anything custom in the login what so ever.

I have a site where a user logs in and the request object is authenticated, i can also see that the user is authenticated by checking the CQ_Analytics object and checking the user profile data to see that isLoggedIn is true.If the user closes their browser and navigates back to the site, the request...