Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache not cleared after native-craft edit of image asset #245

Open
renzo-s opened this issue May 18, 2019 · 3 comments
Open

Cache not cleared after native-craft edit of image asset #245

renzo-s opened this issue May 18, 2019 · 3 comments

Comments

@renzo-s
Copy link

renzo-s commented May 18, 2019

When editing an image assets' crop, rotation etc. via the native Craft tools, the cache is not invalidated. Even after manually using 'Clear Imager transforms' it keeps the cached version.

It will only update after a full imager-cache wipe.

@aelvan
Copy link
Owner

aelvan commented May 19, 2019

Still works for me, can you please provide some more information about your setup. Which platform? What versions of PHP, Craft and Imager? Which transformer are you using? Where do you store your assets?

@renzo-s
Copy link
Author

renzo-s commented May 22, 2019

It happens on both local Valet and on production. Both behind nginx 1.15. php 7.3.x. I have updated Craft and your plugin to the latest versions as of writing (3.1.27 and 2.1.10).

I'm now also using your preparse field plugin, to create transforms on save. But this also won't invalidate the cache with the (for example) cropped image.

If you want I could grab a screenrecording if you want, but only privately.

@aelvan
Copy link
Owner

aelvan commented Sep 16, 2019

Revisited this, and I'm still not able to reproduce.

Was thinking that maybe it was a race condition with preparse (if it's on the asset itself), but it doesn't make sense that the Clear Imager transforms wouldn't work either.

Did you check the folder on your disk after doing Clear Imager transforms? Did the files get recreated or did nothing happen? Also, there's a fair amount of logging in those methods, did you check your logs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants