Purge on updates – Webp with older browsers

  • Resolved mike8040

    (@mike8040)


    1 year, 10 months ago

    So I would like to not open to separate threads. First question is. The webp description says “it servers webp whenever possible”

    Does it mean the feature has a hook to check if browser is compatible with webp format and shows the original files instead?

    Second question. According to the docs auto purge happens on plugin updates. Unfortunately I had several times a broken layout after updating plugins and had to clear minify cache myself. Is there anything I can do about?

Viewing 5 replies - 1 through 5 (of 5 total)

  • I have the same issue especially on sites where I use Elementor.

    Thread Starter mike8040

    (@mike8040)

    Failed purge on updates? Well happened for me yesterday where I updated Elementor/Pro. Broke frontend layout. Actually those issues where always presented with WP-Optimize for me. I had Litespeed Cache active for weeks now and the auto purge feature was great. Never had a borken layout after updating. But CSS/JS tweaks are problematic with LC.

    I would like to know about the Webp integration.

    Plugin Contributor Venkat Raj

    (@webulous)

    WebP
    1. Checks if webp conversion tools are available on your server
    2. Checks if webp format can be served using redirect method (only .htaccess is supported)
    3. If redirection is not possible, it will change src attribute to have webp format (only when the browser has support for webp format)

    Failed purge on updates
    You are saying that you have to clear minify cache yourself. But the page cache is purged, right? If so, It is expected behavior.
    Since html page cache is purged, it will be regenerated and serve new page. My guess is that the old minify assets are served instead of new one because the update doesn’t contain a version bump for its static assets such as js/css files. If they have it, then new set of minify assets are generated which in turn referenced in newly cached pages.

    Thread Starter mike8040

    (@mike8040)

    Thanks for your feedback.

    I will then try out the webp feature.

    Failed purge on updates

    I’m not sure if the page cache was purged really as this is not happening all the time and I moved on to not trust the automatics purge anyway on the live site. Better safe then sorry. Anyway what you say makes sense. But the last happening was Elementor and I’m quit sceptical that they do forget something that obvious. I try to replicate it on the staging.#

    //Edit: Quick question. How can I verify that jpg version were loaded if the browser does not support them? I tested Firefox 92 which should not support webp but the images are visible and the dev tools show webp versions in the html code. Does it happen on the Server side and does not get reflected in the html code?

    Will the webp version load side by side with the jpg version in that case?

    • This reply was modified 1 year, 10 months ago by mike8040.
    Plugin Contributor Venkat Raj

    (@webulous)

    @mike8040 When viewing source code if the HTML doesn’t contain webp but the devtools says so, then it is because of redirection method at work. So, yes, it is happening on the server side.

    One it won’t load side by side, it will only load one version either jpg or webp

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Purge on updates – Webp with older browsers’ is closed to new replies.