Sort order of results with pagination - out of order

This support ticket is created 6 years, 2 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	-
-	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	14:00 – 18:00	13:00 – 18:00	-

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: Paginated lists, Views, Views plugin

This topic contains 1 reply, has 2 voices.

Last updated by Shane 6 years, 2 months ago.

Assisted by: Shane.

Author

Posts

September 17, 2018 at 2:41 pm #1109485

HarryT902

Hi toolset,

I have a custom post type setup as a parent. I have a second type setup as a repeating child. I have a view set to show the repeating posts of the parent. The view is set to show 10 items at a time. It's set with AJAX pagination and manual page transition. Upon first page load, the posts are being displayed in the correct ascending order. The view's sort order is set to order by a single custom field in ascending order.

The problem: When paginating back and forth between pages, the order gets out of whack. It becomes random, and it's not adhering to the initial order when the view loaded in.

September 17, 2018 at 7:29 pm #1109660

Shane

Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Harry,

Thank you for contacting our support forum.

This could possibly be an issue with a plugin conflict and as such I would recommend that you temporarily disable all the non-toolset plugins and try again.

Once you have done this please let me know if the issue still remains.

Thanks,
Shane