Skip Navigation

[Resolved] select_text is not working in dropdown search view

This support ticket is created 6 years, 3 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 2 replies, has 2 voices.

Last updated by yvonneJ 6 years, 3 months ago.

Assisted by: Minesh.

Author
Posts
#1136001

On the website people can select members (coaches) by choosing name, skills etc. Also by province.
I see the dropdown with all the provinces, but i want to start with 'Select provice' as first option.

Because when people only want to filter by skill they HAVE to choose a province. I do'nt want that. If they dont select a province he have to show the members (coaches) from all provinces.

I use this in my view with the select_text:

<div class="form-group">
	<label>[wpml-string context="wpv-views"]Provincie[/wpml-string]</label>
	[wpv-control-postmeta field="wpcf-provincie" url_param="wpv-wpcf-provincie" select_text='Kies een provincie']</div>

Link to a page where the issue can be seen: hidden link

#1136014

Minesh
Supporter

Languages: English (English )

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

Hello. Thank you for contacting the Toolset support.

Well - the correct attribute to use is default_label

Could you please try to use the following code and try to resolve your issue:

<div class="form-group">
    <label>[wpml-string context="wpv-views"]Provincie[/wpml-string]</label>
    [wpv-control-postmeta field="wpcf-provincie" url_param="wpv-wpcf-provincie" default_label='Kies een provincie']</div>

#1136039

My issue is resolved now. Thank you!