Feature Request: cache busting

  • Hello –

    Loving and appreciating your plugin. Works fantastic and especially helpful to have the “Grouping” feature to crop all squares at once, all 3:2 at once, etc.

    One thing we’re having trouble with is that new versions get stuck in the edge caching since they have the exact same URL as the old version. If you upload and the crop immediately it usually works, but if an image has been up and available publicly for a while and then you go back and revise the cropping, it can be stuck in the static file caching for a very long time. I wonder if there could be an option added when you execute the “save crop” action to either change the filename or add a cache busting url parameter after that.

    So transform /wp-content/uploads/2024/09/my-image-400x400.jpg to /wp-content/uploads/2024/09/my-image-400x400_crop2.jpg or else find a way to tag it on in the front end output, like /wp-content/uploads/2024/09/my-image-400x400.jpg?crop=v2

    Maybe you’ve run into this before and have a suggestion on how we could accomplish it already with a small snippet?

    Thanks for considering it.

Viewing 1 replies (of 1 total)
  • Plugin Author Volkmar Kantor

    (@volkmar-kantor)

    Hi @squarecandy,

    yeah, the browser cache is always a real problem. Sadly there is no good solution to this.

    The plugin is designed to have the image on the same spot as before. You may try to implement some custom code to rename the image and change the metadata. I do not know if wordpress will get the filename of the image-size purely from the image-metadata. But you may try this. Have a look on the github page of my plugin to find actions and hooks that may be helping you. The corresponding code ist in the “functions\save.php”. If this is working – i may add this as an experimental feature. I would not activate this be default as some other plugins may depend on the image exact name.

    About the second way (add a version string). I use this in the backend to always get the latest version of the image. But for the frontend its not that easy, as every theme is different and there a infinit ways to load an image in wordpress – depending on your theme. So this is even worse.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.