Smart Crops getting cached on pages | Community
Skip to main content
A
ankushd75501011
Level 2
September 16, 2020
Solved

Smart Crops getting cached on pages

  • September 16, 2020
  • 3 replies
  • 2434 views

Hi,

 

I uploaded an image to my DAM and used it on a page with the default smart crops that AEM generated for my profile.

Now, I went back to DAM and changed some selection in the smart crop for one of my sizes where in for my small size smart crop I wanted to focus more on the object.

But after saving and re-publishing the image, the page still shows the old smart crop. If I hit the image url directly on the browser, then also it gives me the cached image, but if I append a query parameter to the url, it gives me the changed image.

 

Could someone please help?

 

Regards,

Ankush Dhingra

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

@ankushd75501011 OOTB scene7 CDN will cache assets based on TTL. I remember it as 10 hours of browser cache and 1 hour of server cache.

As of I know you have couple of options,

 

Option1: if you have limited number of assets or limited number of authors, you can use scene7 classic ui now changes to desktop app to invalidate CDN cache..

https://docs.adobe.com/content/help/en/experience-manager-64/assets/dynamic/invalidate-cdn-cached-content.html

 

Option2: write a custom replication agent or replication preprocessor or sling job or replication event handler or workflow process step to perform programmatic cache clear.

 

Option3: while generating scene7 url append current timestamp as queryparam by which if we clear aem pagecache if it will fetch latest scene7 files across the page.

 

Hope this helps.

 

3 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
September 16, 2020

Can you check cache invalidation rule in dispatcher?

Or the Dispatcher Flush agent

https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/page-invalidate.html

 

Arun Patidar
    A
    ankushd75501011Author
    Level 2
    September 16, 2020
    No, there is no dispatcher. And the url of scene7 server is cached. Not the aem server.
    Shashi_Mulugu
    Community Advisor
    Shashi_MuluguCommunity AdvisorAccepted solution
    Community Advisor
    September 16, 2020

    @ankushd75501011 OOTB scene7 CDN will cache assets based on TTL. I remember it as 10 hours of browser cache and 1 hour of server cache.

    As of I know you have couple of options,

     

    Option1: if you have limited number of assets or limited number of authors, you can use scene7 classic ui now changes to desktop app to invalidate CDN cache..

    https://docs.adobe.com/content/help/en/experience-manager-64/assets/dynamic/invalidate-cdn-cached-content.html

     

    Option2: write a custom replication agent or replication preprocessor or sling job or replication event handler or workflow process step to perform programmatic cache clear.

     

    Option3: while generating scene7 url append current timestamp as queryparam by which if we clear aem pagecache if it will fetch latest scene7 files across the page.

     

    Hope this helps.

     

      OlegMM
      OlegMM
      Level 2
      July 21, 2021

      Just fixed this with the great support people of Dynamic Media. The issue was that the default invalidation template of <ID> only takes care of the main asset, and doesn't flush the smart crops. The solution was either to add the specific path to the required refocused smart crop in the confirmation dialog ("The following URLs will be invalidated in the CDN"), including the crop name, or to modify the template so that it mentions the main asset plus all possible smart crops:
      <ID>

      <ID>:crop_1_name

      <ID>:crop_2_name

      ...

      <ID>:crop_N_name

       

      Edit: adding screenshots. Other instructions are standard, found under the link in the accepted answer.

        Shashi_Mulugu
        Community Advisor
        Shashi_MuluguCommunity Advisor
        Community Advisor
        July 22, 2021
        Happy to know the solution. Can you please publish more information for the sake of community, how you created invalidation template with screenshots if possible.
        Terms & ConditionsAccessibility statement

        Loading footer...