Company Name: Assa Abloy Opening Solutions (Americas Division)   Company URL: https://www.assaabloy.com/   Example Website: https://www.hesinnovations.com/   Your Name: Pawan Gupta   Your Title: Sr. Tech Program Manager   Our company is the leader in door & security solutions. The implementation whi...

Thank you. let me try that.

Thank you very much. QQ: so what is the best way to handle two types of sites where 1. first site need longer TTL cache because modification into site pages are very low (weekly)2. second site need pages to be modified frequently & upto date with latest data (as ecom site) now, as we have same fastl...

Hello, Is there a way to flush/burst Fastly CDN cache once the modified page republished before the TTL of page on CDN. Currently i have not seen any article or approach how it should be done. I understood that at dispatcher you can set header for CDN to burst the cache via setting TTL based on path...

Thanks for adding that, i think i missed mentioning. My intention about sharing those properties to mainly query from AEM console to find out those pages from authoring/local search into site path.

Hi Abhishek, I think you answer the question. if those properties are not available then you can use that as condition to know the pages which are not published because when you publish pages, these two properties should populate corresponding values. I hope you understand it now. Thanks!!

so, i think you now know the issue area. some time even broken DOM structure and client side failure cause these weird issues. so check on that and i hope you solve it.

Hello, here are my suggestion. for first issue: it should be making layout container as small width, probably try to see if somehow the width has been adjusted for layout container via switching into layout container mode (similar like edit or preview mode) and find out. for second issue: some time ...

Hello, Can you check if one of below property helps you there?? cq:lastReplicated_publishcq:lastReplicatedBy_publish Thanks!!

Hello, I think its depend on your approach how you are planning to implement it. If, you are cross verifying via managing some validation that the person who is accessing this URL is same who requested for reset password then you are doing ok because you can easily stop those unwanted hit during val...