Hello everyone,
today I updated getPage from 1.1.0-pl to 1.2.0-pl on my page (revo 2.1.3-pl).
Before the update everything worked very good, now I have a big problem with the pagination. At the beginning of the output of my getPage-Call, there's a raw output of the pagination controls (only if there are more items than the limit per page). It looks like this:
array(3) {
["pages"]=>
string(377) "<li><a class="active" href="index.php?id=2&page=1">1</a></li>
<li><a href="index.php?id=2&page=2">2</a></li>
<li><a href="index.php?id=2&page=3">3</a></li>
<li><a href="index.php?id=2&page=4">4</a></li>"
["next"]=>
string(119) "<li class="control"><a class="next pagecontrol" href="index.php?id=2&page=2">Nächste Seite</a></li>"
["last"]=>
string(91) "<li class="control"><a href="index.php?id=2&page=4">Last</a></li>"
}
After the array, everything is shown correctly, even the pagination controls.
This is how calling page looks like:
<ul class="uebersicht clearfix">
[[!getPage@?
&elementClass=`modSnippet`
&element=`getResources`
&parents=`[[*id]]`
&limit=`2`
&pageVarKey=`page`
&where=`{"template:=":2}`
&sortby=`createdon`
&sortdir=`DESC`
&includeContent=`1`
&includeTVs=`1`
&processTVs=`1`
&tvPrefix=``
&tpl=`objektThumbTpl`
]]
</ul>
<div class="paging">
<ul class="pageList">
[[!+page.nav]]
</ul>
</div>
I don't see, why this doesn't work, especially because everything was ok before this. Does anybody else have similiar problems? Did I stumble upon a bug? Did something break while updating?
I'd be pretty happy, if someone of you can help me.
With kind regards,
Marc
[ed. note: boundaryfunctions last edited this post 15 years, 1 month ago.]
MODX Staff
