We are using one collection for 4 different resource groups.
If a usergroup is assigned all resource groups, the pagination works properly.
If a user that is restricted to one of the resource groups is logged in, the pagination will separate the resources into varying sets. The first pagination page could have 1 resource, the second page could be not showing any resources, the 3rd pagination page may show 5, the 4th may show no resources again, the 5th 5 resources...
I am assuming that it is creating the pagination based on all resources in the collection, and then MODX hides those resources not belonging to a user's assigned resource group after the pagination gets created. The result is that the user sees a pagination logic that makes no sense.
We are using one collection for 4 different resource groups.
If a usergroup is assigned all resource groups, the pagination works properly. If a user that is restricted to one of the resource groups is logged in, the pagination will separate the resources into varying sets. The first pagination page could have 1 resource, the second page could be not showing any resources, the 3rd pagination page may show 5, the 4th may show no resources again, the 5th 5 resources...
I am assuming that it is creating the pagination based on all resources in the collection, and then MODX hides those resources not belonging to a user's assigned resource group after the pagination gets created. The result is that the user sees a pagination logic that makes no sense.