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

Product Category and Product Tag Not Translating When Filters Applied

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 using the WOOF WooCommerce Products Filter on my website in conjunction with WPML.

I'm trying to translate the product category and product tag text into Spanish.

When I add translations in the 'Advanced' tab, the translations are visible on the left sidebar.

However, once I apply a product category or product tag filter, the text at the top of the page is not translated (see attached screenshot). Can you help me figure out how to translate this text?

Translations Added

Hello

Try  un  file  - \wp-content\plugins\woocommerce-products-filter\index.php change  this code - https://c2n.me/4c374kS.png

$options[$key] = WOOF_HELPER::wpml_translate(null, $this->settings["custom_tax_label"][$key]);

$options[$key] = WOOF_HELPER::wpml_translate($taxonomies[$key]);

Hi, I'm unable to open the PNG file. Malware Bytes shows there's a trojan virus on the site. Would you be able to embed it to this ticket instead?

Is there a way to apply the code update in a different manner (e.g. my child theme)? My concern is that each time I update the plugin, I'll need to manually overwrite the plugin's source code.

Trojan Virus

hello

My screenshot - https://share.pluginus.net/image/i20210518115945.png

 I'll need to manually overwrite the plugin's source code. - not. We will fix this in the next version.