Skip Navigation

[Resolved] Split: Fields with dropdowns for related posts do not show all available options – ordering asc/desc not working

This thread is resolved. Here is a description of the problem and solution.

Problem:
ordering asc/desc not working

Solution:
With New Many To Many relationship where the use_select2="never" attribute is not supported.

You can find proposed solution, in this case, with the following reply:
https://toolset.com/forums/topic/split-fields-with-dropdowns-for-related-posts-do-not-show-all-available-options-ordering-asc-desc-not-working/#post-1083806

Relevant Documentation:

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

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 10 replies, has 3 voices.

Last updated by tony 6 years, 5 months ago.

Assisted by: Minesh.

Author
Posts
#919243

Hi Minesh, many thanks for providing a solution. I have added this string to each field and it works. However, the available options (values) are not sorting alphabetically, even though the field paramaters are telling it to do so. See the attached screenshots. This is the line of code for this field:

<label>Related Governance gap</label>
[cred_field field='@governance-gap-example.parent' select_text='--- Select existing ---' class='form-control' output='bootstrap' order='title' use_select2="never" ordering='asc']
</div>

Do you happen to know what's going wrong? I have flushed all possible caches, tried ordering 'desc' and than 'asc' again, but nothing seems to help.

#919251

Minesh
Supporter

Languages: English (English )

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

Hello. Thank you for contacting the Toolset support.

Yes - I reproduce this issue and I'll escalate it to our Devs. Please hold on for further updates.

#919253

Thanks!

#919382

Minesh
Supporter

Languages: English (English )

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

You welcome.

#1078512

Minesh
Supporter

Languages: English (English )

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

Well - could you please share screenshot of the page Toolset => Relationships

#1079493

Minesh
Supporter

Languages: English (English )

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

Ok - after having a crosscheck with Devs the attribute use_select2="never" is not supported with newly created relationship with Types for good reason. It should be always rendered as select2.

Thank you. Please feel free to close this ticket.

#1083772
Original Field dropdown width - Add an example – Mind the Gap.png
Field dropdown toonarrow - Add an example – Mind the Gap.png
Change in Post Form for CPT Example ‹ Mind the Gap — WordPress.png

Hi Minesh, thanks for following up with the development team. I have just changed the attribute use_select2="never" into select2="never" within the Post Form for CPT Example, and the field now displays the available options in alphabetical order. However, the width of the dropdown is now extremely narrow, so I had to revert the change. See the attached screenshots. Could you please help me out?

#1083786
Toolset relationships.png

Please find attached the requested screenshot of Toolset > Relationships

#1083806

Minesh
Supporter

Languages: English (English )

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

Ok - the fact is that the feature is not supported even if you use select2="never" with screenshot I can still see it remain the select2 NOT the normal select dropdown.

I even confirm that you have new Many To Many relationship where the use_select2="never" attribute is not supported. I'm taking this as new feature request still and its still under assessment. Please note that there is no ETA on it.

Please feel free to close this ticket.

#1083883

Hi Minesh, yes, it would be great if you could treat this as a new feature request. I really hope a solution can be found soon - not just for me, but also for other users of Toolset. In my opinion this is not a feature request, but a bug that needs to be resolved. Anyway, I trust that it will be resolved and I will for now close this issue.

#1174514

For information - I also need a solution for this. I can get the dropdown to include all parents but the sort does not work.

The sort works if the select2="never" is removed but then the list is truncated and finding a record that is not displayed is not user friendly as it does not always work.

I agree with reneV-2 that this should really be treated as a bug.