• We have multiple versions of a page using different URL parameters:

    https://…/post
    https://…/post?ver=10

    If we modify the post the first URL gets purged from the cache but the old ver=10 versions stays in the cache. Therefore only the URL without parameters is up-to-date.

    We are using the basic disk cache. Having different versions in the cache is perfectly fine but as soon as the post gets modified all versions shall be purged.

    Is this a known issue? How can we solve this?

Viewing 6 replies - 1 through 6 (of 6 total)
  • bgdstr

    (@bogdanstratulat)

    I am sorry for any inconvenience. Please navigate to Page Cache > Preload options and make sure that the following option is enabled:

    Preload the post cache upon publish events

    Also, if the issue persists, as a workaround, you may want to disable database caching. I hope this helps and if there is anything else, please feel free to ask.

    Thank you for using W3 Total Cache!
    Kind regards!
    Bogdan S.”

    Thread Starter Christoph Bratschi

    (@cbratschi)

    I tried this setting but it did not change anything.

    Plugin Contributor gidomanders

    (@gidomanders)

    You could try adding a filter on post update to call something like w3tc_flush_page_url($url) on all versions of the page. I could give you the details when I’m back on my computer.

    Thread Starter Christoph Bratschi

    (@cbratschi)

    The problem is we do not know all parameters being used. Some are related to Google Analytics source parameters, others are navigational parameters. For a live ticker we add dynamic timestamps. All these URLs are cached.

    We checked the W3 Total Cache source code and in basic mode there is no way to get the list of URLs because hashed URLs are used by the cache. It will be hard to fix this architecture. In the meantime we switched to LiteSpeed Cache which works fine but we have other sites which are not based on LiteSpeed.

    Plugin Contributor gidomanders

    (@gidomanders)

    Caching so many different URLs per page without knowing what URLs there are will clutter your directory and make the storage used by the website grow exponentially.

    I think it’s better to use JavaScript for dynamic content like that. That way it’ll be possible to cache the basics of a page with W3 Total Cache using Disk: Enhanced to speed up the website and still have dynamic content based on the parameters in the URL.

    Thread Starter Christoph Bratschi

    (@cbratschi)

    This is a workaround for a mobile Safari bug. With the same URL all data is delivered from cache. We are already using AJAX calls and all caching headers are correct. A mixture between Basic and Enhanced would be the right solution for us.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Post update das not purge URLs with parameters’ is closed to new replies.