Purge not working

Resolved joceboi
(@joceboi)

4 months ago

Hi,
I had issue with plugin. I added pull zone id and api key, but purge doesn’t work.
When I purged on bunny.net console, it works.

Viewing 15 replies - 1 through 15 (of 16 total)

1 2 →

Plugin Author BoUk
(@bouk)

4 months ago

Hi @joceboi,

When you enable logging, what exactly does it say in the log?

Thanks

Thread Starter joceboi
(@joceboi)

4 months ago

Hi,
[2026-02-12 09:25:44] cdn-purge.INFO: Starting purge on [publish -> publish]: Triggered by Post ID: 158 [2026-02-12 07:32:05] cdn-purge.INFO: Starting purge on [publish -> publish]: Triggered by Post ID: 6640

Thread Starter joceboi
(@joceboi)

4 months ago

And problem is with .css files

Thread Starter joceboi
(@joceboi)

4 months ago

Hmm weird, I tested it again with new page, tested to change background-image and purged it. I think I will just monitoring that and see what will happes 🙂 Thanks and great plugin! 🙂

Plugin Author BoUk
(@bouk)

4 months ago

I see and that makes sense. Plugin intentionally doesn’t purge the whole pull zone as I was finding that inefficient. Static assets such as js / css / images are not purged at all. Only dynamic content is purged from the cache.

If you introduce some cache busting mechanism to js/css and update with each release, you should be fine.

Also can I just ask what is the URL of the site you are testing the plugin on?

Thanks a lot

Thread Starter joceboi
(@joceboi)

4 months ago

Hi,

https://resaco.fi
Plugin Author BoUk
(@bouk)

4 months ago
Thanks for sharing. I see that static assets are correctly cached, but dynamic content is not, which is likely because of the Cache-Control header set to no-cache. Is it intentional?
- This reply was modified 4 months ago by BoUk.
Thread Starter joceboi
(@joceboi)

4 months ago

Hi, we store only assets on website and html is configured by wp super cache.

Plugin Author BoUk
(@bouk)

4 months ago

Fair enough, but you are missing out here a bit. Caching the whole page at the edge would be surely better and you can use that in conjunction with other caching plugins just fine. Personally I am using W3TC.

Plugin Author BoUk
(@bouk)

4 months ago

In fact, if your intention is to cache only static assets at the edge and handle the rest on your server, you don’t really need this plugin as the primary purpose is to make sure that dynamic URLs are refreshed when you update the content on the site.

Thread Starter joceboi
(@joceboi)

4 months ago

Hmm okay! So you say that I can cache html with bunny without problem?

Plugin Author BoUk
(@bouk)

4 months ago

Hi @joceboi,

Absolutely and that’s the main reason for this plugin. I am using it personally on few sites and so far it seems to work ok.

Best
Petr

Thread Starter joceboi
(@joceboi)

4 months ago

Hi, okay! I will test it also 🙂

Thread Starter joceboi
(@joceboi)

4 months ago

How plugin works with woocommerce when there is /cart etc…
Or /wp-admin page.

Plugin Author BoUk
(@bouk)

4 months ago

Haven’t tested that on WooCommerce site yet, but you just need to make sure, correct headers are sent and check the response. Also you can exclude certain URLs using Edge rules and basically tell Bunny to bypass cache for cart etc.

Viewing 15 replies - 1 through 15 (of 16 total)

1 2 →

You must be logged in to reply to this topic.