I'm having issues with the Cache plugin on pages in my public space using the Content Publishing Plugin.
The structure of my pages are a source page and a main page. The content in the main page is included from the source page via a multi-excerpt macro. The multi-excerpt macro is wrapped in a cache macro
Here is the sample code:
Immediately after publishing, a few (not all) pages are not showing their content that is contained within the cache macro. Refreshing the page does nothing. The content on the main page in draft space is rendering fine.
It is only after I edit the source page in the public space, then refresh the main page in the public space that the content renders. Of course this is not ideal as the whole idea of having the publishing plugin is so that you can prepare draft content and publish it to a public space when ready.
Does anyone know of any reason why this would be happening aand how to fix it? Is it something to do with the size of the cache? (I don't understand the instructions on the Cache plugin page "The capacity property equal to 100 means that 100 distinct renderings of the cache macro will be cached", but I do have more than 100 pages with the cache macro - is this an issue? and how do I fix it if I don't have access to the server?).
The cache macro renders the data at a point in time. The rendered data will not change until the cache expires or you edit the content within the cache macro (slightly different behavior if not using cache plugin 4.1.1). You can decrease the expiration time or you can add a refresh button on the main page (showRefresh=true).
Thanks for the reply Bob,
I do have a refresh button on the page, but clicking it in the public space does nothing - it does not show the page content at all. (The cache content is showing in the Draft space, but not in the public space).
Is there a limit as to how much content can be in the Cache? Would that be why the cache is not refreshing?
(and how do I fix it if I don't have access to the server?).
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs