trouble between Loco Translate plugin and Woocommerce 9.2.3

Please don’t prod me for help.

Your question hasn’t been answered, because it’s highly specific to your WooCommerce setup, and you provided no steps to demonstrate that the issue is directly caused by my plugin.

If you submit a useful bug report, the bug will get fixed.

Hi,
I am very annoyed because this problem is based on 3 components:

• Woocommerce because this problem occurs in variable products,
• Loco Translate because this problem occurs when it is activated,
• And Jupiter Theme because this problem is mainly that the block editor is not displayed when the problem occurs.

But each of you 3 says “I assure you it’s not my component, go see the others”

However, the problem is there, and I think that if this problem only occurs when your plugin is activated, that is sufficient evidence that your plugin is involved, isn’t it ?!

So I think it’s definitely a crossover issue that probably involves a conflict between the 3.
So I would like to act as a mediator between the 3 of you and I will ask everyone, with my authorization and my credentials, to take a look at the test site and check for themselves.
If each of you looks and notices something that could be the cause, I’m sure you’ll learn something interesting about how your code interacts with other components. And I’m sure you will know how to optimize your code to avoid this type of situation.
Isn’t that a good idea?!

I can give you administrator credentials to the test site if you tell me how to send them to you privately and securely
This way you will see live what is happening and will be able to carry out tests.

None of the three parties here have a responsibility to log into your server and debug your site for you.

My plugin is thoroughly tested for its specific functions, but there are many ways you can go wrong, and many ways its functions can be overridden or prevented from working. There are also ways your own translations can break your website.

You’ve been invited to demonstrate a bug, and if you can do so, it will be fixed. Telling me you’re very annoyed is not a route to a solution.

I think that if this problem only occurs when your plugin is activated, that is sufficient evidence that your plugin is involved, isn’t it ?!

Involved, yes. But this is not evidence of the fault. Hence it is not an actionable bug report.

It could simply be that different translation files are being loaded, and something about those files is causing a change in behaviour that you don’t understand. There’s no point me guessing.

Hi,
Rather than discuss at length, since neither you nor I can really guess if it is a simple implication or a mistake, and that although I am annoyed is of no use, given that you are the person best placed here to test specifically, perhaps in just 2 or 3 minutes, would you be able to recognize what is causing this malfunction? Without even repairing it, simply by giving me some clues as to what is causing this, you would be doing a very good thing, if obviously your plugin was not the direct cause. At least we would get to the bottom of it.

Hi,
I have news for you, I’m sure you will be interested in this additional information.
Based on my investigation today, I was able to identify a cause of the problem.
Indeed, by reading the logs I realized that the start dates of this problem coincided with the change of server made in August, and at the same time the evolution of PHP from version 7.4.33 ( latest version where everything worked perfectly) to 8.3.12.
By downgrading to PHP version 7.4.33, the problem disappears. So it seems that the cause of the problem has been identified. I cannot keep version 7.4.33 active since it is deprecated.
The question now arises as follows:
How to identify which of the 3 components in question should upgrade its code to a recommended PHP version? Could you tell me if your plugin has been optimally tested for this latest PHP version?

Loco Translate is tested against 8.3, and I would recommend this version.

At a guess, based on this information, the issue is quite likely to be incorrect formatting in your custom translations. Read this FAQ and check your error logs as advised in the article.

I doubt there’s any compatibility issue between your PHP version and any of the code in WooCommerce or in my plugin. I can’t speak for your theme, or any of the other components of your web site.

For your information, I also get this error message: Détails de l’erreur

Une erreur de type E_ERROR a été causée dans la ligne 120 du fichier /var/www/vhosts/l-deco-bougies-naturelles.fr/httpdocs/wp-content/plugins/woocommerce/includes/admin/meta-boxes/views/html-product-data-variations.php. Message d’erreur : Uncaught ValueError: Unknown format specifier “a” in /var/www/vhosts/l-deco-bougies-naturelles.fr/httpdocs/wp-content/plugins/woocommerce/includes/admin/meta-boxes/views/html-product-data-variations.php:120
Stack trace: 0 /var/www/vhosts/l-deco-bougies-naturelles.fr/httpdocs/wp-content/plugins/woocommerce/includes/admin/meta-boxes/views/html-product-data-variations.php(120): sprintf() 1 /var/www/vhosts/l-deco-bougies-naturelles.fr/httpdocs/wp-content/plugins/woocommerce/includes/admin/meta-boxes/class-wc-meta-box-product-data.php(182): include(‘…’) 2 /var/www/vhosts/l-deco-bougies-naturelles.fr/httpdocs/wp-content/plugins/woocommerce/includes/admin/meta-boxes/views/html-product-data-panel.php(53): WC_Meta_Box_Product_Data::output_variations() 3 /var/www/vhosts/l-deco-bougies-naturelles.fr/httpdocs/wp-content/plugins/woocommerce/includes/admin/meta-boxes/class-wc-meta-box-product-data.php(33): include(‘…’) 4 /var/www/vhosts/l-deco-bougies-naturelles.fr/httpdocs/wp-admin/includes/template.php(1456): WC_Meta_Box_Product_Data::output() 5 /var/www/vhosts/l-deco-bougies-naturelles.fr/httpdocs/wp-admin/edit-form-advanced.php(723): do_meta_boxes() 6 /var/www/vhosts/l-deco-bougies-naturelles.fr/httpdocs/wp-admin/post.php(206): require(‘…’) 7 {main}
thrown

if we look at the error i provided, the clue is possibly here: Unknown format specifier “a” in. The error is saying that instead of %s it encountered %a (or maybe the s is missing and it’s something like % annually), which is not proper and gives the error.
Can you confirm me that it can possibly come from an incorrect formatting in my woocommerce translation ?
If i meet difficulties to find & correct that, is there an easy way to start from the beginning with your plugin for woocommerce translation ?
Is there a ready to go french translation for woocommerce that i can use directly?

I solved the issue by finding a missing ”s”next to % in the plural form of of %s items

Thanks for posting back. I’m going to mark as resolved.

Checking error logs should always be step 1 in diagnosing a fault.

As I alluded to earlier in the thread – “It could simply be that different translation files are being loaded, and something about those files is causing a change in behaviour that you don’t understand.”

Bad formatting is a common problem, which is why Loco Translate warns you when you open an affected file in the editor. I’m curious, did you not see a warning? Does the editor not flag this mistake? If not, I need to investigate why. Please post details in a new topic if this feature isn’t working for you.