I tried that, to no avail. Actually, since then, the problem has
worsened. Now that I've finally managed to set up a complete duplicate
of our LiveServer project, RedDot project, web server, etc. and
started to publish content out, I find that NONE of those values are
populating. They show up fine in RedDot, just not when the page is
published.

It looks as if, while the count of list items is correct, the for loop
fails to iterate. Any ideas?

- Bobby

On Jul 18, 1:02 am, RedDotExpert <[email protected]> wrote:
> Yes, please
>
> On Jul 17, 4:06 pm, bobbykjack <[email protected]> wrote:
>
> > Hi RDE,
>
> > Thanks for the tip, but I must be doing something wrong still: that's
> > not working :-(
> > I've done as you say - do I need to put the commented-out placeholder
> > in a <!IoRangeList> tag?
>
> > Cheers,
>
> > - Bobby
>
> > On Jul 17, 3:11 pm, RedDotExpert <[email protected]> wrote:
>
> > > Hello,
>
> > > it is a known cache issue regarding rendertag.
>
> > > Example,
>
> > > You have page A and page B.
> > > page B pulls headline of page A via rendertag.
> > > Page A headline changed.
> > > page B still displays old headline of page A because CMS will only
> > > update page B cache if content (placeholder) in page B have been
> > > changed.
>
> > > Fix:
> > > Even though you might not be using your list in your template.  Place
> > > the list placeholder in the template (just comment it out <!-- -->),
> > > so when the list changes, the page cache is forced to update.
>
> > > On Jul 17, 5:12 am, bobbykjack <[email protected]> wrote:
>
> > > > I have a page containing a list whose pages are assigned by keyword.
> > > > The base template uses render tags to obtain data from those sub-pages
> > > > and vbscript to sort and display it.
>
> > > > When I add a new page to the list, it doesn't show up immediately in
> > > > the base page. I have a render tag in the base page which outputs the
> > > > number of items in the list; this confirms that the correct number of
> > > > items is being identified, if not displayed.
>
> > > > If I update the base page's template with a trivial change, the new
> > > > sub-page IS then displayed. This feels like a caching issue of some
> > > > sort, so:
>
> > > > a) does anyone know if such a caching issue exists, and how it can be
> > > > resolved? Does it relate to 'pre-execute' tags in some way?
>
> > > > b) can anyone confirm whether this will only happen in RedDot mode
> > > > (which would be inconvenient but not a disaster) or if the published
> > > > page will be affected similarly (which would mean revising the entire
> > > > approach for the umpteenth time)?
>
> > > > Many thanks,
>
> > > > - Bobby
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to