Please update both WPML (4.5.12) and String Translation (3.2.3).
If you have access to your WP back end, you can update from the custom WPML installer page found under the commercial tab of the Add New plugins page (screenshot). You may need to click the Check for Updates button for your site to contact WPML and identify the latest available versions.
You can also reach this page from the list of plugins: under any of the WPML plugins click the registered link, and that will take you to the custom installer page.
If you cannot access the site because of the fatal error, you may need to use FTP to change the String Translation plugin folder name, which will deactivate it (see hidden link). You can then delete it from the plugins page and reinstall it (with the latest version).
For the clients commenting on this thread, the error occurs with String Translation 3.2.2, not with the latest version 3.2.3.
Please ensure that you update to String Translation 3.2.3 (and WPML 4.5.12).
As noted in my initial reply at the top, you may need to click the Check for Updates button on the custom installer page to make sure the installer sees the latest versions.
I had the same problem. It would be great to get an update before that. Logging into a website with a fatal error/or the client telling about the fatal error is not good practise. Especially if it's known beforehand that this error can be caused. I would really appreciate it you're more proactive about informing about such those issues.
We published a blog post and sent a newsletter last week encouraging users not to update to WordPress 6.1 until they had updated WPML and ST, hopefully you have not opted-out of receiving the newsletters. (If you need to re-subscribe, please email hello@wpml.org.)
Unfortunately WordPress did not handle this release very well, continuing to make breaking changes as late as last Friday, before releasing on a public holiday across Europe yesterday.
We are sorry for the disruption.
And, for anyone still commenting that they cannot see the 3.2.3 update of String Translation, please read again my first reply and know that you may need to click the Check for Updates button. (You can, of course, obtain the latest version to install manually from your account downloads page.)
This problem has broken all of our sites today. We are currently using WPML plugins in 3 sites, and there is no notification to update plugins to newer version.
Our sites are updated automatically to latest WordPress version and we did not see your notices not to update to WordPress 6.1.
If you can check and send us detailed instructions to fix the problem caused by WPML plugins please
The topic ‘[Closed] Fatal error: Uncaught Error: Call to undefined method WP_Textdomain_Registry’ is closed to new replies.