thewebmonk

Hello Victor,
thank you for your reply.

I tried checking with WPML, and this is the answer by its AI chatbot, I will try to apply the fix in the weekend when I have time but for now I thought I would share it with you, if useful:

**

There is a known tracked bug between the Filter Everything plugin and WPML that closely matches what you’re describing — filter terms not working correctly on the frontend in translated languages. Before applying the workaround, I need to confirm one detail about your setup.

1. Go to Plugins -> Installed Plugins and check whether Advanced Custom Fields (ACF) is active on your site.
2. Also check: is the GENERE taxonomy a standard WordPress / WooCommerce product attribute or custom taxonomy, or is it a field you created using ACF?

–

I don’t use ACF, and GENERE is a product attribute

–

Since GENERE is a standard WooCommerce product attribute (not an ACF field), the relevant workaround is a tracked WPML bug with the Filter Everything plugin affecting filter term display in translated languages. Let’s apply the fix.

Before starting, take a full site backup.

1. Go to Appearance -> Theme File Editor and select functions.php from your Astra Child theme (make sure the child theme file is selected, not the parent).
2. Paste the following code at the very bottom of the file:

// WPML Workaround for compsupp-7581  
add_filter('wpc_terms_before_display', 'wpml_compsupp7581_filter_wpc_filter_terms', 10, 4);

function wpml_compsupp7581_filter_wpc_filter_terms($terms, $filter, $set, $urlManager) {  
  if ( class_exists('Sitepress') ) {  
    foreach ($terms as &$term) {  
      $label = $term->name;  
      $textdomain = 'WordPress';  
      $string_name = 'WPC Filter Label: '.substr($label, 0, 40);  
      if ( apply_filters('wpml_default_language', NULL) == apply_filters('wpml_current_language', NULL)) {  
        do_action('wpml_register_single_string', $textdomain, $string_name, $label);  
      }  
      $term->name = apply_filters('wpml_translate_single_string', $label, $textdomain, $string_name);  
    }  
  }  
  return $terms;  
}  

1. Click Update File to save.
2. Visit your English shop page (the original-language version) — this registers the filter label strings with WPML.

After visiting the English page, go to WPML -> String Translation, search forWPC Filter Labelunder the WordPress textdomain, and confirm that the GENERE / Genre term strings appear there ready for translation.

Hello, thank you, here it is: https://privatebin.syde.com/?c834103e8bc30924#DVabbUH5RShKicwy89dmrgYkAMvc9ea4YuFsij1MBwCy

AS INSTRUCTED I WILL OPEN A NEW THREAD

Hello Frank,

I have another problem, after hitting “publish the changes” on CookieYes, I tested the checkout process (luckily) and found out that the Paypal buttons were not showing! I tried both on mobile and desktop.

I have deactivated the CookieYes plugin, and the buttons reappered. I use WooCommerce PayPal Payments.

As Script I had put wp-content/plugins/woocommerce/ – I notice that in your instructions you had included a / at the beginning of the script, could that be the issue?

I see that the other Woocommerce cookies that were previously set, have the following pattern: plugins/woocommerce. Here they are:

woocommerce_items_in_cart
session
Script URL pattern: plugins/woocommerce

wp_woocommerce_session_*
2 days
Script URL pattern: plugins/woocommerce

The only exception is this:
woocommerce_cart_hash
session
Script URL pattern: Not available

Just for information, if useful, I also use LiteSpeed Cache plugin.

Thank you!

• This reply was modified 3 weeks, 2 days ago by thewebmonk.

I apologise, thank you for your tips

Thank you so much ! I will contact the Server.

Meanwhile, here is the requetested info:

Status Log https://pastebin.com/ptJ5CwC2

There are no recent Fatal Error logs, there is one from 6 February (when for some reason Woocommerce Multilingual got deactivated) https://pastebin.com/haudLh9B

Thanks again!

Hello Zubair,

the hosting company helped me fix the problem, looks like it was a malicious attack from some bots that had my website offline. But the event coincided with the time at which WooCommerce Multilingual for some reason was deactivated and created those errors in the logs. Not sure what caused it, if the malicious attack could deactivate the plugin.

Thank you

Raffaella

The Hosting Company was able to make me log into WordPress again, here is some more information from the WooCommerce Logs (fatal-errors-2025-02-06)

https://pastebin.com/NYdR0VXA

Thank you