Custom Coding needed

Anonymous

#26896

Hello,

I would like to pay to get a feature added now to the plugin.

I would need in Search Form UI, when you add a Post Meta, to be able that the value “Like” the custom value instead of “=”.

For example if custom value is “Core i3 3500” for meta key “processor”, i could add a Post meta key “processor” value “LIKE” “Core i3” So i get posts with “Core i3 3500” as result.

Would you do that kind of job?

Anonymous

#26897

Hi Adrien,

From your description, unless I’m misunderstanding what you want, it doesn’t sound like you need any custom coding.

When you add a Post Meta field to your Search Form UI, you are choosing the KEY (in this case, ‘processor’), not the VALUE. The form UI will then show all the possible VALUES that they could search for, and a search will return all matches, including partial matches.

What you might do is ensure that your taxonomy for ‘processor’ is a hierarchical one, and have a parent taxonomy that is “Core i3”, with child taxonomies under that parent that are for the specific i3 processor, in this case “Core i3 3500”. Then select any type of field (although personally I think a check box would work best), and then check if you want child terms shown (or not, depending on how many you have) and be sure to check to return child results in parent searches (Include Children in Parents?) – that way if someone checks the choice “Core i3” under “Processor”, they will get all results that have Core i3 parent taxonomy checked, including all those with child taxonomies checked.

Anonymous

#26899

“Processor” is a meta_key. How to check that it is a hierarchical taxonomy?

Also, there might be hundreds of Core i3 processor, so would i need to add the new processor each time in a parent processor taxonomy?

Ross Moderator

#27195

Hi Adrien

It sounds like you are getting terms confused.

Post meta and taxonomies are two different concepts – post meta is not hierarchical, if you want to use a hierarchical taxonomy, you must use a taxonomy field – which is not related to a post meta field.

That being said, I think I do follow what you want anyway, based on previous communications.

Just to note, I am building an option to sync post meta – so that the post meta field will automatically populate, so you don’t need to edit the search form each time you add a new processor type.

In regards to the other option, I’m absolutely swamped with support from the new S&F 2.0 so I am unable to take on any more custom work for the next couple of months.

Thanks

[Author]

Posts