No Radio Button Option for Custom Meta?
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from flyte on January 18, 2021, 22:41Why is there no radio button option for meta? And why if you have a meta filed do you need to enter each value individually for Checkboxes and Select?
Thanks.
Why is there no radio button option for meta? And why if you have a meta filed do you need to enter each value individually for Checkboxes and Select?
Thanks.
Quote from Pablo Borysenco on January 19, 2021, 13:41Hello
Why is there no radio button option for meta? - because it doesn't make sense. In checkbox mode, only one checkbox is used for one meta key
why if you have a meta filed do you need to enter each value individually - because the meta field is a free text field - the user can enter any values, even serialized data
Hello
Why is there no radio button option for meta? - because it doesn't make sense. In checkbox mode, only one checkbox is used for one meta key
why if you have a meta filed do you need to enter each value individually - because the meta field is a free text field - the user can enter any values, even serialized data
Quote from flyte on January 19, 2021, 15:15Thank you for the answers and they do make sense.
My issue was that I had product attributes that I could originally display as radio buttons that I moved to custom meta for various reasons. I then realized that there was no radio button option for meta filters and that meta filters won't auto populate the key values of my meta fields as individual choices. This means additional work to build the filter and the filter needs updating if an additional key is added to my meta field.
I can work with checkboxes but life would be easier if meta had all the same options as attributes including the ability to toggle counts etc. I do appreciate that attributes are essentially taxonomies and that does make them different to custom meta fields.
Thanks
Thank you for the answers and they do make sense.
My issue was that I had product attributes that I could originally display as radio buttons that I moved to custom meta for various reasons. I then realized that there was no radio button option for meta filters and that meta filters won't auto populate the key values of my meta fields as individual choices. This means additional work to build the filter and the filter needs updating if an additional key is added to my meta field.
I can work with checkboxes but life would be easier if meta had all the same options as attributes including the ability to toggle counts etc. I do appreciate that attributes are essentially taxonomies and that does make them different to custom meta fields.
Thanks
Quote from flyte on January 19, 2021, 22:02Ok I have set my meta values to filter with a select menu and only one of them is working. See private data.
Ok I have set my meta values to filter with a select menu and only one of them is working. See private data.
Quote from Pablo Borysenco on January 20, 2021, 12:47Hello
Drop me wp-admin access( https://c2n.me/43SC6rb.png ->https://c2n.me/42BAoj4.png ) I will check it
Hello
Drop me wp-admin access( https://c2n.me/43SC6rb.png ->https://c2n.me/42BAoj4.png ) I will check it
Quote from flyte on January 20, 2021, 15:37Done. Can you also clarify that for checkbox use, each meta key for any meta field requires it's own checkbox?
Thank you.
Done. Can you also clarify that for checkbox use, each meta key for any meta field requires it's own checkbox?
Thank you.
Quote from Pablo Borysenco on January 21, 2021, 12:14Hello
It looks like you're not using the keys correctly. My short video showing how I set up one of the filters - https://c2n.me/4aDG5ZD
each meta key for any meta field requires it's own checkbox? - Only one checkbox for only one meta key
Hello
It looks like you're not using the keys correctly. My short video showing how I set up one of the filters - https://c2n.me/4aDG5ZD
each meta key for any meta field requires it's own checkbox? - Only one checkbox for only one meta key
Quote from flyte on January 21, 2021, 19:04Hi, thanks for the video I see what you are doing there but I think you are using the attribute fields which I am not going to use moving forward. Using woo comm attributes for them makes importing and exporting way more complex than it needs to be for that data
I think the issue is that the two fields that are currently giving me trouble, Filter Needle Size and Filter Hook Size are checkbox fields in ACF so they are returning an Array. The two fields are 'filter_hook_size' and 'filter_needle_size' these are specifically for filtering. These can span several values which is why they are checkboxes and not select in ACF.
New test product without attributes and with debug info in private data
Hi, thanks for the video I see what you are doing there but I think you are using the attribute fields which I am not going to use moving forward. Using woo comm attributes for them makes importing and exporting way more complex than it needs to be for that data
I think the issue is that the two fields that are currently giving me trouble, Filter Needle Size and Filter Hook Size are checkbox fields in ACF so they are returning an Array. The two fields are 'filter_hook_size' and 'filter_needle_size' these are specifically for filtering. These can span several values which is why they are checkboxes and not select in ACF.
New test product without attributes and with debug info in private data
Quote from Pablo Borysenco on January 22, 2021, 12:54Hello
I think you are using the attribute fields - I am 100% sure that these are meta fields. Taxonomy is not stored in custom fields
My test - https://c2n.me/4aEFA7N.jpg
The two fields are 'filter_hook_size' and 'filter_needle_size' t - where did you get these keys? Products have no such meta fields
Hello
I think you are using the attribute fields - I am 100% sure that these are meta fields. Taxonomy is not stored in custom fields
My test - https://c2n.me/4aEFA7N.jpg
The two fields are 'filter_hook_size' and 'filter_needle_size' t - where did you get these keys? Products have no such meta fields
Quote from flyte on January 22, 2021, 21:16No I'm not using the attributes although I haven't deleted them yet. I switch to Advanced Custom Fields as this data is easier to deal with for us and it's the kind of data that is not going to affect product price.
I have done some testing and it looks like checkbox and multi-select fields in ACF can't be used with your plugin. It seems to only work with text input and select values where a single input is used. If the keys are returned as an array it doesn't work. Is there a way around this?
No I'm not using the attributes although I haven't deleted them yet. I switch to Advanced Custom Fields as this data is easier to deal with for us and it's the kind of data that is not going to affect product price.
I have done some testing and it looks like checkbox and multi-select fields in ACF can't be used with your plugin. It seems to only work with text input and select values where a single input is used. If the keys are returned as an array it doesn't work. Is there a way around this?
Quote from Pablo Borysenco on January 25, 2021, 14:22Hello
Unfortunately this won't work with serialized data(an array).
Hello
Unfortunately this won't work with serialized data(an array).