# Latest update requires cache purge in CloudFlare

**URL:** https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166
**Category:** Self-hosting
**Created:** [31 oktober 2017 om 20:05 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166 "2017-10-31T20:05:05Z")
**Posts on this page:** 12
**Page:** 4

<div class="post-metadata">

### Author: ![misterdude](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/misterdude/32/87377_2.png) [@misterdude](https://meta.discourse.org/u/misterdude)
#### Post date: [3 november 2017 om 02:28 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/62 "2017-11-03T02:28:58Z")

</div>

This totally saved me. Thank you!

---

<div class="post-metadata">

### Author: ![nsuchy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nsuchy/32/166530_2.png) [@nsuchy](https://meta.discourse.org/u/nsuchy)
#### Post date: [3 november 2017 om 20:45 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/63 "2017-11-03T20:45:03Z")

</div>

That’s odd that CSS minification would break things. Doesn’t it just remove all spaces and new lines in the CSS + gzip it?

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [3 november 2017 om 21:05 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/64 "2017-11-03T21:05:14Z")

</div>

I don’t know. The information has been shared with CloudFlare engineering via @RyanK, I’d assume he’ll be able to give more details once he has them.

---

<div class="post-metadata">

### Author: ![nsuchy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nsuchy/32/166530_2.png) [@nsuchy](https://meta.discourse.org/u/nsuchy)
#### Post date: [3 november 2017 om 21:07 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/65 "2017-11-03T21:07:08Z")

</div>

Ryan K has been pretty good with resolving issues when I’ve brought them up with him via email/twitter (over screennames) so I guess he’ll be able to find a fix.

---

<div class="post-metadata">

### Author: ![mmiada](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mmiada/32/78441_2.png) [@mmiada](https://meta.discourse.org/u/mmiada)
#### Post date: [5 november 2017 om 09:15 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/66 "2017-11-05T09:15:21Z")

</div>

ok, but if i use discourse as subdomain, and i don’t want to disable css minify for main domain. what can i do? because there is no option in cloudflare page rules to disable minify?  
thanks

---

<div class="post-metadata">

### Author: ![nsuchy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nsuchy/32/166530_2.png) [@nsuchy](https://meta.discourse.org/u/nsuchy)
#### Post date: [5 november 2017 om 19:07 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/67 "2017-11-05T19:07:26Z")

</div>

Easy peasy:  
https://www.youtube.com/embed/ee-N4R1yttI?feature=oembed&wmode=opaque

---

<div class="post-metadata">

### Author: ![mmiada](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mmiada/32/78441_2.png) [@mmiada](https://meta.discourse.org/u/mmiada)
#### Post date: [5 november 2017 om 22:51 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/68 "2017-11-05T22:51:20Z")

</div>

i have ask something else. pls read again my question

---

<div class="post-metadata">

### Author: ![Carlo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/carlo/32/79036_2.png) [@Carlo](https://meta.discourse.org/u/Carlo)
#### Post date: [7 november 2017 om 14:34 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/69 "2017-11-07T14:34:19Z")

</div>

Add the page rule “Disable performance” ( for your forum only ).

In your case it should be sth like:

`http://discourse.domain.com/*`

More info here:  
[https://support.cloudflare.com/hc/en-us/articles/200172336-How-do-I-create-a-Page-Rule-](https://support.cloudflare.com/hc/en-us/articles/200172336-How-do-I-create-a-Page-Rule-)

Then **purge cloudflare cache**. **Delete your browser cache** and you’re done. 👍

---

<div class="post-metadata">

### Author: ![mmiada](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mmiada/32/78441_2.png) [@mmiada](https://meta.discourse.org/u/mmiada)
#### Post date: [7 november 2017 om 15:11 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/70 "2017-11-07T15:11:22Z")

</div>

> [@Carlo](#):
>
> [http://discourse.domain.com/](http://discourse.domain.com/)\*

yes, in this way works.

---

<div class="post-metadata">

### Author: ![Ian\_Paterson](https://avatars.discourse-cdn.com/v4/letter/i/bb73d2/32.png) [@Ian\_Paterson](https://meta.discourse.org/u/Ian_Paterson)
#### Post date: [12 november 2017 om 16:47 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/71 "2017-11-12T16:47:36Z")

</div>

Just to share the fruits of a few hours of debugging before finding this thread, the following syntax is the source of this incompatibility. The CSS is _truncated_ after this block (specifically, the CSS terminates in `height:100%`) leaving about 1/2 of the Discourse styles missing.

```plaintext
@supports (--custom:property) {
	aside.onebox .onebox-body .aspect-image{max-height:170px;max-width:20%;float:left;margin-right:10px;width:100%;height:auto}
	aside.onebox .onebox-body .aspect-image img{width:100%;height:inherit;max-width:initial;max-height:initial;float:none;margin-right:none}
	aside.onebox .onebox-body [style*="--aspect-ratio"]{position:relative}
	aside.onebox .onebox-body [style*="--aspect-ratio"]::before{content:"";display:block;padding-bottom:calc(100% / (var(--aspect-ratio)))}
	aside.onebox .onebox-body [style*="--aspect-ratio"]>:first-child{position:absolute;top:0;left:0;height:100%}
}

```

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [5 december 2017 om 04:28 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/72 "2017-12-05T04:28:28Z")

</div>

Completely forgot to update here, sorry! Been chatting with our contacts at CloudFlare. They’ve confirmed the issue, and have pushed out a temporary workaround. CloudFlare will detect if the site is Discourse based, and if it is force-disable minification (users cannot override).

They’re working on a new minifier, once ready they’ll remove the force-disable setting so you can minify files again.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5 mei 2019 om 06:36 UTC](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166/73 "2019-05-05T06:36:40Z")

</div>



[Previous page](https://meta.discourse.org/t/latest-update-requires-cache-purge-in-cloudflare/73166.md?page=3)
