Hi Wolfgang, Excellent observation and good question.
Actually, all rendertags, when used inside a regular template (not the navigation template) are cached. That includes, .Headline, .Elements.GetElement, .GetElementByName, Foreach... The cache is refreshed when a content element's change (container, list, regular text placeholder) causes the page to be to updated. Basically, any placeholder update that causes the page to look difference from before. Note: placeholder changes cause page update, content retrieved via rendertag, even when changed, do not cause page update because there isn't a mechanism in place to notify rendertags that content has changed. Hence the issue of rendertag cache I have been so vocal about in this forum. Why is GetElementByName better than Elements.GetElement? Well because the document says so and in theory, GetElementByName do not have to enumerate all elements of a Page object before getting a sepecific element. Hope that clarifies the issue. Best, -Jian On Monday, March 18, 2013 3:41:55 AM UTC-4, Wolfgang Roiter wrote: > > The documentation says that this function caches for 365 days, so maybe > it's not the best solution for values that can be changed by editors. > > Am Donnerstag, 14. März 2013 17:50:35 UTC+1 schrieb Jian Huang: >> >> Oopps, use GetElementByName instead of Elements.GetElement for >> performance reasons >> > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
