PluginUs.Net - Business Tools for WooCommerce and WordPress

[realize your idea - make your dreams come true]

Support Forum

You need to log-in to create request (topic) to the support

Filter for shortcode not working

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 please
If 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.

 

I'm trying to filter titles that contain something like"[sc name="product-code"][/sc]".  However, using the LIKE operator finds everything whether it has this term or not, and EXACT won't work because that wants the entire title to be the search term.

Does WOLF not have a CONTAIN operator that looks for the *exact* search term, but anywhere within the search field?

Hello

CONTAIN =  LIKE

In our case, the plugin splits the search text by spaces and searches for several words.  Try using a search query without spaces. For example: name="product-code"]

I'm afraid that only allows this to work if the section without spaces is unique.

If it's not unique, then it appears that WOLF is completely unable to filter for terms like this.

 

This is why I asked in a separate ticket whether WOLF supported RegEx searching, which would have been able to target this type of search term precisely.

Because of this, I'm afraid the need to implement a RegEx search is no longer a nice-to-have feature, but a required feature.

Hello

is completely unable to filter for terms like this. - It doesn't matter, it's just a string. And if you have the same parts of the string in all products, then searching for these parts will return all products.

Anyway, I added your suggestion to the developers, they should decide the priority and necessity of this feature.