Problem with v2.6.12

Confirm. After upgrading to version 2.6.12, all my translations disappeared. Moreover, all plugins that were translated using Loco began to be displayed only in English!

@pixelsing The only change in 2.6.12 is a fix that loads custom translation files when the installed system file is absent. Do you have any such custom translation files? This is the only change in behaviour I can explain.

@ronbi13 Please start your own topic for your own issue. There’s nothing here to suggest you have the actual same problem, and it’s impossible for me to track issues this way.

I’ve got WordPress 6.6.2 and PHP 7.4 running and am trying to reproduce this error. I can’t find any Ajax services failing. e.g. plugin search. How can I see this happening? Do I need a particular combination of translation files to be installed?

I don’t know what to say. It’s just a fact…
The website is in production and sells tickets for shows so I can’t “play” with it and let the bug.

If necessary, I’ll do a duplication for you but I’ve no time for that next week.

Seen on admin of another website WP 6.7, Loco 2.6.12 :

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cpt-tables 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 /var/www/clients/client0/web109/web/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-dark-mode 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 /var/www/clients/client0/web109/web/wp-includes/functions.php on line 6114

Maybe it can helps

Regarding those notices. They’re not from my plugin. See FAQ: https://localise.biz/wordpress/plugin/faqs/early-domain-loading

They may be related though.

As for how this relates to my plugin version bump – I don’t know. I’m dealing with regressions now that I have identified, but none that would directly produce the side effects you’re seeing, unless the difference is actually the translations themselves that get loaded.

btw – It’s essential to have a test environment if you run a business. Having a live website that you upgrade without testing first is a huge risk.

Hello, same problem with version 2.6.12, version 2.6.13 did not solve anything. I had to go back to 2.6.11. I specify that I have version 6.7 of WordPress.

@kromaweb Please try the dev version. A bug has been identified in 2.6.12 and 2.6.13 where an exception is not caught for unresolved relative paths.