When using offset and limit together in a ListPages module, the limit has to be increased by the amount of the offset to return desired results. This causes unnecessary pagination links to be displayed. If you examine the source of this sandbox page, you can see the issue.
I would like the offset to act as an index or starting point into the ListPages query and then return the next "limit" results. Currently, if I want to return 20 results with an offset of 40, I have to set the limit to 60. This causes the .pager element to appear when it's not needed. I should be able to set the limit to 20 in this example to get my desired results.
Could it be the question of positioning the parameters ( first limit and than offset or vice versa ) - which controls the sequence of usage?
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
Thinking about this more today, maybe a solution that would work that doesn't break existing ListPages modules and is simpler to implement would be to not display the .pager element if limit = perPage. That way you could keep your query the same and we could continue to use the same syntax, but have the unnecessary .pager element hidden when that condition is true.
Community Admin
We'll se what we can do.
Bartłomiej Bąkowski @ Wikidot Inc.
';.;' TeRq (Write PM)
Its fixed now.
use: perPage="20" limit="20" offset="40"
Thx for reporting.
Bartłomiej Bąkowski @ Wikidot Inc.
';.;' TeRq (Write PM)
That works really well, thank you.
Rob Elliott - Strathpeffer, Scotland - Wikidot first line support & community admin team.
Cool! Thanks
A - S I M P L E - P L A N by ARTiZEN a startingpoint for simple wikidot solutions.
Thanks TeRq! This works great.
Community Admin