Does anybody know which order are the pages of a list processed when
looping thru it using the foreach Render tag?
This is the code I'm using:
...
Name: <%!! Store:item[Int32:counter].Headline !!%>
...
Keep in mind that any changes made in the Page Order of
And don't forget to use
GetElementByName() instead of Elements.GetElement() if you want to improve
Performance in your projects (at least of you use a current V10 or V11
system, was introduced in V10 SP1 HF1).
Best,
Hilmar
Am Mittwoch, 13. März 2013 09:44:37 UTC+1 schrieb Mario:
> Thanks ,
Thanks , that works!
Mario
Am Mittwoch, 13. März 2013 schrieb Wolfgang Roiter :
> Hi Mario,
>
> I once stumpled upon a similar problem and found out, that the element
> that you would like to access, must be present in any template that is used
> when navigation manager loops through the page hi
Hi Neil,
you could try the following (not sure if it works in 7.5 as well, but worth
giving a try):
<%!!
Context:CurrentPage.MainLink.OwnerPage.Elements.GetElement(Str:con_body).Value
!!%>
With ".MainLink" you will get the anchor/container/list element where
CurrentPage is attached to - ple
Hi Mario,
I once stumpled upon a similar problem and found out, that the element that
you would like to access, must be present in any template that is used when
navigation manager loops through the page hierarchy.
Please also add "Str:" when using element names:
GetElement(Str:element_name)
R