are you using WordPress version 6.7?
That version just broke the plugin including packages from plugins like woocommerce and the developer of loco is working on a fix. We are all waiting for an update.
Plugin Author
Tim W
(@timwhitlock)
Ensure you ALSO have the system translations installed. This is a known issue made worse by changes in WordPress that defer all translation loading, including those loaded explicitly as noted in the above post.
@jonasturnbull Yes, upgraded to WP 6.7 recently. Although issue occurred before the upgrade. We upgraded to 6.7 attempting to remedy the issue but wasn’t succesful.
Plugin Author
Tim W
(@timwhitlock)
Please try the latest dev version. If this doesn’t solve the problem, then please provide steps so I can reproduce your issue.
@timwhitlock No dice. You got a private channel please?
Plugin Author
Tim W
(@timwhitlock)
There is no private support. All issues need posting with details here. No passwords please.
You say your issue occurred before the upgrade. This means it may not be related to my plugin, but you’re welcome to submit a proper bug report here and I’ll investigate.
@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
Plugin Author
Tim W
(@timwhitlock)
Dev version tested and nothing change. Translations in custom folder not take effect.
Please provide an example source string and where in your WooCommerce site this is rendered wrongly.
Please also try the string debugger. Enable WP_DEBUG and it appears in the Loco Translate menu.
@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
Plugin Author
Tim W
(@timwhitlock)
Thanks.
Your first image is too small to read.
Your second (debug) image shows a different string to your original post, but it seems to be working. i.e. Loco Translate is finding the custom file and modifying the loading process accordingly.
If your site doesn’t also display “/Jour” then your issue may not be directly with my plugin. Note that major changes in WordPress 6.7 will affect any plugin involved in selecting languages or requesting translations.
@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…
Plugin Author
Tim W
(@timwhitlock)
Joining the dots, you have your answer:
1). You get _load_textdomain_just_in_time was called incorrectly.
and
2) “but work when move to system or author…”
—
This tells me numerous parts of your site are trying to access translations too early. Most likely before Loco Translate is running. Hence it actually do its job.
I note that ova-brw is one of the domains being requested too early. So I’d report this as a bug to the developer.
@timwhitlock Thank you !
Dev has published new update that fix it !
Plugin Author
Tim W
(@timwhitlock)
Glad to hear it. I’ve only just noticed that you aren’t the OP here. Hence my comment about your issue being different.
I’ll leave this open in case @wpshushu wishes to post more details.
