getPage returns invalid total pages when use pageOneLimit

10 Posts

sofasurfer Reply #1, 14 years, 5 months ago

Not sure what I'm doing wrong.

Tried to use the pageOneLimit functionality as follow:

[[!getPage?
	&elementClass=`modSnippet`
	&element=`getResources`
	&parents=`8`
	&depth=`10`
	&pageOneLimit=`2`
	&limit=`3`
	&sortby=`menuindex`
	&sortdir=`ASC`
	&tpl=`page.item`
]]
<div class="pageNav">[[!+page.nav]]</div>

There is a total of 8 pages, so I don't understant this output:

Page 1

Resource 1
Resource 2

Page 2

Resource 4
Resource 5
Resource 6

Page 3

Resource 7
Resource 8

So Resource 4 is missing, this is the same with different values.

Is there something wrog with the getPage snippet call, or do I need to set some custom properties for get resources as well?

Thank you for any replie.

Home is where the hard disk is:
http://sofasurfer.org

MODX Staff
10,725 Posts

opengeek Reply #2, 14 years, 5 months ago

I assume you meant Resource 3 is missing? Is this Resource in a Resource Group that might be protected from certain users?

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

10 Posts

sofasurfer Reply #3, 14 years, 5 months ago

Yes, correct number 4 is missing..

When I set pageOneLimit to 10 all 8 resources are shown, and no there are no custom resource groups set nor any other security setting.

Home is where the hard disk is:
http://sofasurfer.org

10 Posts

sofasurfer Reply #4, 14 years, 5 months ago

Just setup a complete fresh installation:
http://debug.sofasurfer.org

MODX Revolution 2.2.2-pl (traditional)
getPage 1.2.2 pl
getResources 1.4.2 pl

With the same results. Can provide manager login if this helps.

Home is where the hard disk is:
http://sofasurfer.org