Support » Plugin: Varnish HTTP Purge » custom.css not purging

Viewing 8 replies - 1 through 8 (of 8 total)
  • You should press the ‘purge all’ button on the main admin dashboard.

    As the FAQ mentions, no, it doesn’t purge CSS. Never has, probably never will, since that isn’t content.

    Why doesn’t my cache purge when I edit my theme?
    Because the plugin only purges your content when you edit it. That means if you edit a page/post, or someone leaves a comment, it’ll change. Otherwise, you have to purge the whole cache. The plugin will do this for you if you change your theme, but not when you edit your theme.

    That said, if you use Jetpack’s CSS editor, it will purge the whole cache on save.

    I’ll try some curl then, according to DreamHost:

    $ curl -X PURGE “http://mydomain.com/wp-content/themes/mytheme/style\.css”

    That works too 🙂

    The plugin’s just for content, as the logic behind it is we shouldn’t be messing with our CSS that much. Not that I don’t have the same problem. Command line will give you the best control for that 🙂

    Ok cool. Thanks Mika

    I know that technically Varnish has never purged CSS, but I was actually using it to do so.

    Since the latest WordPress update, or something, I can no longer use Varnish to purge my CSS. Is there any other way that I can do that? I’ve tried clearing my browser cache manually, but it isn’t working at all.

    jptdesrosiers – This post is resolved, so generally you should NOT post in it but make a new one for yourself. 🙂

    That said, in the month since this was resolved, there is a Purge All button. However it only works if you have regex purging in Varnish.

    Oh shoot, so sorry!

    How do I get regex purging?!

    It has to be set up in your Varnish config. No idea how to do it myself :/

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘custom.css not purging’ is closed to new replies.