Hi Dan, Glad you have found your answer, and thanks for replying to this thread with the answer.
I have been working with rendertags since 7.5 when it was first available and once thought it was the solution to all programmatic problems. However, I have since discovered quite a few cases rendertag would fail, or worst, being inconsistent. Here are a couple of cases one might want to watch out for when using the said solution. 1. Escape:HtmlDecode is not needed unless the content needs to be assigned to a preexecution variable 2. Assuming Store:testList is within a foreach rendertag, [Int32:listCounter] is not needed, Store:testList.GetUrl() should do 3. The rendertag only works if pages are connected to the list. It fails if the list references another list. 4. Caution from #3, if a page is connected to multiple locations with multiple publication packages, the page is published multiple times to multiple locations. 5. Due to a rendertag caching issue, if you add another page to "Info within container", rendertag do not know a page has been added, so it continues to display from old cache, same thing goes for another element content changes. I notice that the site is already using javascript; is it possible to use javascript/ajax to pull and display the content from child pages? On Jan 6, 6:22 am, DanFookes <[email protected]> wrote: > Hi Tim > > Thanks for the response, but I've just found what I was after. If > interested: > > "<%!! Escape:HtmlDecode(Store:testList[Int32:listCounter].GetUrl) !! > %>" > > Thanks -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
