Good suggestions. I thought he was until I saw a placeholder <%anc_page1%> in his sample code
On Thursday, January 31, 2013 11:10:01 AM UTC-5, Hilmar Bunjes wrote: > > Hi, > >> Elements.GetElement is known to cause performance and memory issues on >> the MS system when used too often. It is best to avoid it. >> >> Instead of using >> <%!! Context:CurrentPage.Elements.GetElement(opt_Class).GetHtml() !!%> >> >> You can simply use the placeholder as it is >> <%opt_Class%> >> > If I understand the message of Paul correctly he is using this code within > a navigation content class. There you need to use the RenderTag or make > another structure of the menu. > > However, you can improve the performance of the RenderTag by using > CurrentPage.GetElementByName(String:name) instead of > CurrentPage.Elements.GetElement(String:name). > > You can even more improve the performance by using a standard field > instead of an option list. The option list can slow down your page in > SmartEdit and Publication pretty heavily if you use it a lot (there are a > lot of DB queries going on to find the current value). To fill the standard > field you could use a plugin that fills the element (e.g. by using SmartAPI > or directly RQL). > > Best, > Hilmar > -- 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.
