Plugin throws fatal errors, unusable

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was experiencing fatal errors that prevented access to both the front-end and back-end of their site, and they were unable to view or create support tickets due to these errors.
Solution:
We addressed the issue by patching the missing database tables and deactivating then reactivating all plugins. This resolved the error messages and restored backend functionality. We also scanned the theme for strings, ensuring that they appeared in the string translation table, indicating that the string translation is functioning correctly. We recommend the client to verify the changes from their end and report any discrepancies.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check if you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket here.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Exception

This topic contains 19 replies, has 0 voices.

Last updated by Lauren 2 months, 2 weeks ago.

Assisted by: Lauren.

Author	Posts
January 21, 2026 at 3:26 pm #17751092
Lauren	I found that there was a missing table icl_string_batches, so I'm adding that now to see if it resolves the fatal error. I also found the following error in the debug log, and this typically shows when there is a conflict with another plugin/theme. Do you happen to have a staging site where we can deactivate all non WPML plugins to see if this error goes away? PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpml-string-translation 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 /home/u257530350/domains/beersyachtconsulting.eu/public_html/wp-includes/functions.php on line 6131 If not, I can create a staging site and get a copy of your site to test that, however I realize time is of the essense so if you already have a test site, that could speed things along.
January 21, 2026 at 3:32 pm #17751164
martijnv-52	This website isn't live, so just do what needs to be done. I thought that would be clear considering it's about half done and there's an "under maintenance" active 😉
January 21, 2026 at 4:05 pm #17751373
Lauren	THanks for allowing me to test with that. I patched the missing tables, deactivated/reactivated all plugins, removed the messages and as of now, I'm not seeing the messages return and I'm not seeing errors on the backend anymore. Can you test from your end and let me know if you find anything that I may have missed? I also scanned the theme for Strings and the strings appear in the string translation table, so it appears to be working as expected.
January 21, 2026 at 4:12 pm #17751442
martijnv-52	Thank you. It's been a long day for me (literally, working 7 to 5 currently) so I'm done for today. I will test tomorrow 🤞🏼 If there are still issues, I hope someone closer to my time-zone can help, cos more than half my day will be over before you have to start work. Thanks for all your help so far.
January 21, 2026 at 4:46 pm #17751497
Lauren	I can understand that! Just let us know if you run into any issues, and I'll assign this to a client in your time zone in case you need assistance sooner. But, hopefully everything is now resolved. Have a great rest of your day!