Dear All,
I searched the forums and saw a number of threads about article pagination; most quite old.
I may have missed something, but I could only find the article pagination snippet that requires
an editor to manually insert a {BREAK} tag in each article, at pagination points.
Is there anything in Evo or Revo (specifically Evo for now) that automatically paginates articles
based on a setting like word counts, i.e. every 500 words?
Thanks,
Peter Brown
Hi All,
I worked on the pagination module in Evo, and have gained the distinct impression that it doesn't work unless the article pages are not cached.
Yet, if we don't cache the articles, then the snippets become cached, and that's not good at all, since some of the snippets need to be uncached. This behavior was mentioned on Bob Ray's website.
Based on that, I'm under the impression that article pagination will NOT work in Evo, but will work in Revo.
Anyone have any comments or thoughts?
Thanks,
Peter
TBH, I don't know if pagination works in Evo or not, but it does in Revo using the getPage snippet.
Dear Bob,
Thanks... your comment that I mentioned was on this page:
http://bobsguides.com/modx-cache.html
"It is a quirk of MODx Evolution that when you have a document designated as uncached (the cacheable? checkbox is unchecked) and you put an uncached snippet tag on that page, the snippet is actually called cached so the results the user sees may be out of date."
It seems to be a deal breaker with pagination because of the fact that the content is cached, thus not returning the correctly split page content. The pagination plugin only worked when I uncached the page, which of course would then mess with the snippets, which were supposed to be uncached.
I guess the answer is "switch to Revo".
I'm looking forward to your book! Thanks for writing it.
Peter
My comment may be somewhat misleading. The caching is not quite as reliable or sensible in Evo, but usually, you can get what you want by reversing the logical cache settings at each level as you progress through nested calls. IOW (IIRC), if the page is uncached, a snippet marked as cached on the page will be called uncached.
It is true that in Evo, only snippets can be specified as uncached. In Revo, any element tag can be specified as uncached (including chunks and TVs).
Dear Bob,
Oh! Then perhaps pagination *will* work, by marking the page uncached, and the snippet cached, so that it will actually be uncached, as you pointed out. Hmmm. That sounds like the way to go.
Each page has a number of snippets, including ditto, etc.
I'll have to test it. Thanks!
Peter
Dear Bob,
I've created an article that is uncached, and then added a DateTime snippt on the page, in both cached and uncached forms. With the page cached, I get two different results, but with the page uncached, both instances of the snippet return updated results:
cached: 08-09-2011 19:48:17
uncached: 08-09-2011 19:48:17
each time I reload the page.
Is this unreliable behavior in Evo, or do you think I can count on this working?
I would think it would be safer to leave the snippets [!uncached!], just in case the page is left cached by mistake.
Thanks,
Peter
