A client of mine using this platform is having trouble re-uploading an image that has been modified and the website keeps showing the old image. She already cleaned the cookies of her browser, and the problem keeps persisting… We now know it is related to octobercms and I’m not sure what can be done for this situation. For uploading the images, she selects the image through media manager, and also here the old image remains in the thumbnail, even if the image has been modified, but when clicked on the image link in media manager, it does display the modified image, but strangely enough it doesn’t show this in the front-end of the website. Is there a way to clean the cache of media manager? or the whole system itself? I have already tried “php artisan cache:clear” command, but the problem remains…
Hi @daftspunk thanks for the quick reply! I tried this and unfortunately it didn’t work, is there perhaps also another solution that the images uploaded through media manager don’t get cached by the system? I have checked the htaccess and it isn’t related to this, even clearing the cookies of my browser didn’t work…
hello @daftspunk
I’m facing the same problem by the way running php artisan october:util purge resizer does solve the issue, but it clears the entire resizer cache.
In our case, we are looking for a way to handle a more specific scenario: when an image is updated while keeping the same filename, it would be useful to invalidate or remove only the resized versions related to that specific image, rather than purging and regenerating the cache for all images.
Is there a recommended way to achieve this, or a method to selectively clear the resized versions for a single media item?
Isnt it that all your images are cached within users browser cache and changing them is not the best idea. There will be still images from cache shown. So all the resized versions are normally served with cache headers. I’d say renaming is good.
When replacing a file that is piped through |resize there is no way to invalidate that one file in the resizer cache, you can only purge everything (works but is resource intensive at scale).
i had to implement a plugin where using october cms media & resize events the solution where already used outside october the fix is appends the source file’s mtime to the cache key i will use it hope in next realse of octobercms comes with this feature