[MGNLIMG-49] Flush generated-images cache upon configuration changes Created: 26/May/09  Updated: 11/May/17  Resolved: 02/Mar/17

Status: Closed
Project: Imaging
Component/s: cache
Affects Version/s: None
Fix Version/s: 3.3.1

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Jaroslav Simak
Resolution: Fixed Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLSITE-78 Flush generated-images cache upon con... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: Kromeriz 85
Story Points: 5

 Description   

Ideally, we'd only flush the images that were generated using the generator whose configuration was just modified.



 Comments   
Comment by Christopher Zimmermann [ 05/Dec/13 ]

Verify if a mechanism was introduced already to flush this cache.

Comment by Michael Büchele [ 26/Aug/15 ]

Hi, what's the current status of this ticket?
Are there any workarounds available at the moment?
We have exactly this issue, that images are still delivered with wrong size after having changed the image variation config.
How come this ticket is 6 years old...?

Comment by Federico Grilli [ 17/Sep/15 ]

Hello Michael, thanks for your comment and sorry for the late reply.

We are looking again into this and get back to you as soon as we know more.

Cheers,

Federico

Comment by Federico Grilli [ 17/Sep/15 ]

mbperi regarding the workaround, one thing you could do is running a simple Groovy script removing all images under a given theme in the imaging repository. E.g.

session = ctx.getJCRSession('imaging')
themeRoot = session.rootNode.getNode('my-theme')
NodeUtil.collectAllChildren(themeRoot).each {it.remove()}
session.save()

Should the images also be cached by Magnolia, the cache needs to be flushed, of course. As of Magnolia 5.4 you can do this selectively on a public instance via Cache Browser app https://documentation.magnolia-cms.com/display/DOCS/Cache+Browser+app
Finally, when you're not in production you may want to use /server/filters/servlets/ImagingServlet@storeGeneratedImages=false so that the dynamic variant generation to the imaging workspace is disabled, e.g. during development or testing.

Hope this helps.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Comment by Espen Jervidalo [ 10/Jan/17 ]

This is an annoying issue. You have to login to the public instance and manually delete the cached images from the imaging-workspace. And as explained in the description, just blindly wiping it on publication is far from an ideal solution. Re-opening it.

Comment by Vivian Steller [ 11/May/17 ]

Congrats and Thanks for Fixing this. ....after almost 8 years! But it's the proof: just because a ticket is old it doesn't mean it never gets solved!

Keep on the great work @Magnolia!

Generated at Mon Feb 12 02:11:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.