izotop

Same issue here !

@carolm29 any news about a fix ?

After every woocommerce updates, We need to edit free shipping amount to change 70,00 to 70 to avoid bug on checkout page =/

Thank you @acsnaterse to start this thread !

Same issue for us… After woocommerce update free shipping rule not works randomly. We need to edit amount and change 70,00 to 70 to fix it…

This is a known issue on github… How to fix this permanently ?

@timwhitlock Thank you !

Dev has published new update that fix it !

@timwhitlock
Console :

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?ova-brw?domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the?init?action or later. Please see?Debugging in WordPress?for more information. (This message was added in version 6.7.0.) in?/wp-includes/functions.php?on line?6114

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?woocommerce?domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the?init?action or later. Please see?Debugging in WordPress?for more information. (This message was added in version 6.7.0.) in?/wp-includes/functions.php?on line?6114

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?wp-security-audit-log?domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the?init?action or later. Please see?Debugging in WordPress?for more information. (This message was added in version 6.7.0.) in?/wp-includes/functions.php?on line?6114

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?wpvivid-backuprestore?domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the?init?action or later. Please see?Debugging in WordPress?for more information. (This message was added in version 6.7.0.) in?/wp-includes/functions.php?on line?6114

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?complianz-gdpr?domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the?init?action or later. Please see?Debugging in WordPress?for more information. (This message was added in version 6.7.0.) in?/wp-includes/functions.php?on line?6114

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?dynamic-content-for-elementor?domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the?init?action or later. Please see?Debugging in WordPress?for more information. (This message was added in version 6.7.0.) in?/wp-includes/functions.php?on line?6114

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?woolentor-pro?domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the?init?action or later. Please see?Debugging in WordPress?for more information. (This message was added in version 6.7.0.) in?/wp-includes/functions.php?on line?6114

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?rocket?domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the?init?action or later. Please see?Debugging in WordPress?for more information. (This message was added in version 6.7.0.) in?/wp-includes/functions.php?on line?6114

Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?wordpress-seo?domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the?init?action or later. Please see?Debugging in WordPress?for more information. (This message was added in version 6.7.0.) in?/wp-includes/functions.php?on line?6114

Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:6114) in?/includes/misc.php?on line?1438

Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:6114) in?/wp-includes/functions.php?on line?7137

Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:6114) in?/wp-admin/admin-header.php?on line?9

Got : “à partir de 105,00?€ HT?/ Day ” instead of “à partir de 105,00?€ HT?/ Jour”

All translations not work when using custom but work when move to system or author…

@timwhitlock

Please find : debug console with alerts & debugger from loco (available 2 days)

https://i.ibb.co/tC9S337/issue.jpg
https://i.ibb.co/xg45GTB/debug.jpg

@timwhitlock

Since 6.7 wordpress update I had to move the translations from the custom folder to system or author for them to take effect.

I have selected my translation to move it from system to custom and not working since 6.7.

Dev version tested and nothing change. Translations in custom folder not take effect.

Cache and CSS empty ; no changes. When rollback to system or author, works well

Hi,

Issue fixed after moving translations from custom to system… Not the best way to save translations, but it was necessary to get the website back properly.

Hope you can publish new update quickly =)

• This reply was modified 4 months ago by izotop.

Woocommerce needed