Particles configuration / cache in YAML about docs HOT 9 CLOSED

Basically the static caching caches the particle instances by configuration. If configuration changes, new cache key is used and the instance gets updated in the page. Nothing else affects the caching and there's no specified timeout on the cache.

So static means that it'll be cached (up to) indefinitely and only either clearing cache or changing the configuration of the particles clear the cache.

from docs.

Awesome. Will get to it next.

from docs.

There's really only one caching mode (aside for not caching/being dynamic): static. I also added menu, but it has still some issues with some configurations, so it's not being used.

Static caching is permanent caching which only takes account of particle configuration. Basically, it caches the particle until the configuration of the particle changes.

Static caching only works for particles which have no changing content. You cannot cache particles with a date in it, nor can you cache any particles, which use platform content or methods with changing values. This is why caching has been disabled by default.

For changing content, I need to add caching with a timeout. The support is kind of there already, I've just not had time to add and test it out.

from docs.

@mahagr @w00fz I have a question on the static caching configuration because I'm not 100% sure what is actually does. Are only the values of the particle cached or is any content generated by the particle cached? Let's assume a particle with static configuration values that generates dynamic content e.g. from Joomla or fetched from a JS API. Is in this case the dynamic content cached or is it written out as it is?!

from docs.

@mahagr thanks for your answer. So static caching should only be used for particles that display completely static content? Am I understanding that right? So dynamic content generated by an API would be cached the first time the particle is loaded and then kept until the particle configuration changes or the cache is cleaned? sorry for my demand but I want to clearly understand when to use it and when not :)

from docs.

Yes, it should only be used when there are absolutely no changes from view to view. Caching gets disabled in development mode, BTW.

from docs.

@mahagr Alright :). Thanks for you patience!

from docs.

http://docs.gantry.org/gantry5/particles/particles#caching

from docs.

Looks good!

from docs.