• Resolved bugbearcreative

    (@bugbearcreative)


    When creating a custom crop for an image, the new crop appears in the “Crop Featured Image” pop-up window, but the new version of the image does not appear elsewhere on the site. For example, if the thumbnail size (or all square crops) are updated, the new version of the crop only appears in the “Crop Featured Image” pop-up window, not on the front end of the site or in the Media Library. This behavior appears on multiple WordPress installations, including a test site with no other active plugins. Plugin quick-test indicates that the plugin is functioning normally. Please advise.

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

    (@volkmar-kantor)

    Please have a look at: the FAQ page -> “I’ve cropped the image, but the new version do not appear in the frontend.”

    In a nutshell: if the image appear cropped in the crop-editor, then the image-size is definitively cropped. If you do not see this on the page it means:

    • You need to refresh your Browser-Cache (as the new image is saved on top of the old image)
    • OR – you do not use that specific image-size on that position
    Thread Starter bugbearcreative

    (@bugbearcreative)

    Thanks. I understand about the use of specific image sizes, and clearing browser cache. One site had server-level caching issues that contributed to the worst display glitches. I’m still not clear on the thumbnails in the Media Library not updating when the ‘thumbnail’ size is recropped. Shouldn’t a new crop of the ‘thumbnail’ size appear in the Media Library?

    Plugin Author Volkmar Kantor

    (@volkmar-kantor)

    Its normally not the server that leads to that specific problem. If the image has already served to the browser, the browser do not request it again (or in the same way) but use the cached version. I tried multiple times to fix this issue server sided (with some headers or disable caching), but did not had any success (using an apache server).

    If you found a solution, great, let me hear about it.

    The only thing that worked for me (and this is exactly as the crop-editor is working) is to add an additional parameter – a cache-breaker – to the image-url.

    casper

    (@caspervoogt)

    I ran into the issue reported by the OP, and was able to solve it by clearing my site’s Varnish cache. This site is hosted with Cloudways and uses their Breeze cache, which uses Varnish. That plugin clears Varnish cache for a post when a post is updated (for example) but it doesn’t know to do that when a new crop is saved, so it has to be purged manually.

    I also want to note that the images on my site do not include a cache-busting parameter (on the frontend anyway). I don’t know if they’re supposed to, but the previous message in this thread made it sound like they are supposed to. I’m using Elementor and it embeds the image without cache-busting parameters. That could also explain why I have to manually purge the Varnish cache.

    • This reply was modified 2 weeks, 6 days ago by casper.
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.