You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm always confused when I add content to Backdrop CMS, because it does not show up for quite a while. Clearing the cache does not help, but the content eventually shows up. I'm not sure if this is Backdrop CMS caching at play, server caching, or if we are using Cloudflare to cache content.
But, I'm experiencing this when logged in with Developer and Editor roles.
This is much more aggressive caching than I am used to. I would like:
At least to understand what is going on here (maybe I should be doing this on my other sites).
Possible create a way for content editors to bypass this cache to view the content they have just created (instead of having to come back 30 minutes later to verify that it's displaying as expected).
The text was updated successfully, but these errors were encountered:
stpaultim
changed the title
Clarify (and improve) caching on BackdropCMS.org
Clarify (and improve) caching of content on BackdropCMS.org
Oct 30, 2020
OK, to clarify. I was being silly and trying to post events that were dated in the past (which meant that my content did not appear for logical reasons). So, this does not seem to be a problem with events or mentions that are properly created. However, I do experience this for external notifications and some other types of content. At least, I would like to better understand what is happening.
I'm always confused when I add content to Backdrop CMS, because it does not show up for quite a while. Clearing the cache does not help, but the content eventually shows up. I'm not sure if this is Backdrop CMS caching at play, server caching, or if we are using Cloudflare to cache content.
But, I'm experiencing this when logged in with Developer and Editor roles.
This is much more aggressive caching than I am used to. I would like:
The text was updated successfully, but these errors were encountered: