Taxonomy select number, include higher

Trevor

#238408

You could set this as range control, manually set the max (not auto detect) and set that to a number higher than any maximum you are likely to have, then use CSS to hide that control. The user gets only to set the min number, but the query sent is actually a range. Does that make sense?

Anonymous

#238434

Hi Trevor,

thanks for your help. No, it doesn’t make sense to me at all, sorry :-). Can you please elaborate?

Thanks!
Boris

Trevor

#238439

Can you send me a screenshot of the field setup in the form UI design?

You will need to upload the image to an external file sharing site, like dropbox, and share the link(s) with me.

Anonymous

#238459

Hi Trevor,
you mean a screenshot of the frontend? Here it is. I’ve marked the part I’m talking about, which is now a multiselect.

Trevor

#238461

Sorry, no, in the back end, in the form design. It is a Post Meta, not a taxonomy, yes? I ask, because the numbers have a preceding ‘0’?

Anonymous

#238473

Ah, sorry! Here is the back-end screenshot:

It’s a taxonomy, not a post meta. I’ve put the leading zeros there on purpose, because otherwise when selecting the proper number in the accommodation in the backend would not be in the proper order.

Anonymous

#238491

I’ve added a filter for postmeta, using the maximum occupancy field used in the post type (ranges from 4 to 12 guests). However, it doesn’t work. No matter what I select, the results do not change.

You can see how I set it up here:

Trevor

#238495

This reply has been marked as private.

Anonymous

#238503

This reply has been marked as private.

Anonymous

#238550

This reply has been marked as private.

[Author]

Posts