Skip Navigation

[Resolved] Use relationship field for sorting order

This support ticket is created 2 years, 1 month 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.

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

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 2 replies, has 2 voices.

Last updated by marcB-6 2 years, 1 month ago.

Assisted by: Minesh.

Author
Posts
#2496729

Hi guys,

i have a question. I have two post types called articles and slides. In articles admin can setup a slider selecting 'slide' posts from a many to many relation. In the relation i created a relationship field called 'slide position'. It's a numeric field and i want to give admin control of the slide order using this number.

When i select 'slide position' field in the view for ordering it's resulting in an error (sorry no posts).
How to set it up correct?

Thanks!

#2497249

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

When you say:
In the relation i created a relationship field called 'slide position'. It's a numeric field and i want to give admin control of the slide order using this number.
==>
do you mean that the field 'slide position' is belongs to intermediary post type of many-to-many post relationship?

If yes, then you should have to set your view to query the intermediary post type and then display the parent/child fields accordingly as intermediary post type will have access to both parent and child posts of your many-to-many post relationship.

#2497541

Thanks Minesh, perfect support as always.
My issue is resolved now. Thank you!