Please describe the problem this pr fixes. How to replicate the bug and how to test the fix

When you order all the items, there's no problem, but when i try to put a different pagination order (like for example when i try o put another order, 5 or 10 for pagination, the 1st page is correct, but the other ones are not accurate, as they change the order without me knowing, like they go randomly)
This is a file that shows what I mean:

Sorry that shows nothing

Category list:

First page 5 items:

Second page:

Sorry but I still cannot see what is wrong

@t-arapi can you please create an animation that shows the issue? because screenshots are not so clear

1. Create 7 categories
2. Show content categories diplay all
3. Reorder all cats (remember the order)
4. Show content categories limit 5 (pagination has 2 pages)
5. Go to page 2 and order up the last item
6. Show content categories diplay all
7. Check up the order that you have now and if it is the same as the previous one

Does this help somehow?

I think I have replicated it - is this what you meant

Yes, more or less, although the category number 9 should be the sixth in the final order and not the fisrt.

Yes that's the bug?

On 4 Sep 2016 3:34 p.m., "t-arapi" notifications@github.com wrote:

Yes, more or less, although the category number 9 should be the sixth in
the final order and not the fisrt.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#11906 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8ZI0dPYlGTUJPNT5TYJgxbT-c7Mpks5qmtcFgaJpZM4J0Rlm
.

I have tested this item ✅ successfully on 508b3f4

I have tested this item ✅ successfully on d6b66a5

I have tested this item ✅ successfully on d6b66a5

RTC

This needs more testing, I am not 100% sure that the fix is ok and doesn't have side effects.

set to needs review since we have tested this

I have tested this item ✅ successfully on d6b66a5

yes , i have tested this successfully

Removed the milestone for now

@rdeutz have you done a review?

nudging @rdeutz

maybe @rdeutz is enough.

If this PR get no Response, it will be closed at 17th September 2017.

@franz-wohlkoenig this PR is waiting a review from a maintainer. It has been tested by several people as good but @rdeutz wanted to hold back on merging it so he could do further tests. It shouldnt be closed just because a maintainer hasnt approved/merged it

thanks for Info @brianteeman and thanks for approve @rdeutz

just go ahead with this, @mbabker can make the decision

Thanks