Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
The error on the image showed a maintenance message before the error, the maintenance error is coming from WordPress, were you updating plugins or the theme by any chance? and is the error still there?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Remember to keep the debug.log enabled and check it from time to time.
The lines to enable it in the wp-config.php should NOT be at the end of the file, but more or less after any other "define". that is required for the file to actually log the content.
And if you have any auto update, it could be the reason why clients see that although it's unlikely, that sounds more like the server really just reached the max resources for the second and stopped working, the hosting usually have stats about this.
i was checking the debug log file, there are so many errors i see, please can you check that? i did give you FTP access. the debug log file is inside wp-content folder named "debug.log" and it seems it is related to wpml
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
I already checked those errors (I guess you mean the ones on the WPML > Support > Advanced Translation Editor), they are old ones and were related to things that I already checked you fixed and in fact the last time you had an issue was on the 17th. that log records the issues but doesn't allow you to delete them and will keep only 50 of them so make sure you always check that the errors have today's date given that a recurring issue will repeat everyday, at least once per day.
Your last error was on the 17th and that was because of a server upgrade we did.
------------------
If you mean the DEBUG.LOG file then there are many notices, yes, but they have nothing to do with WPML, they are a WordPress localization related issue coming from Complianz plugin, WooCommerce Cost of Goods, WMUDEV and many other plugins.
You can see the name in the actual notice since they look like this:
[24-Jul-2025 22:59:14 UTC] PHP Notice: _load_textdomain_just_in_time تمّ استدعائه بشكل غير صحيح. Translation loading for the
woocommerce-cost-of-goods
...
these are 99% of the content you get in the debug.log
There are indeed errors there, but again, they are not related to WPML. one of them is related to Elementor:
[24-Jul-2025 23:00:50 UTC] PHP Fatal error: Uncaught ValueError: Unknown format specifier "?" in /home/1308505.cloudwaysapps.com/dwdfyhvxnv/public_html/wp-content/plugins/elementor-pro/modules/mega-menu/widgets/mega-menu.php:2196
You should contact Elementor's Support and ask about it but these issues usually mean that you have a "bad" collation or charset in the database that doesn't handle special characters (like Arabic letters, or similar characters).
In fact, you also have another error:
[24-Jul-2025 23:01:27 UTC] WordPress database error Illegal mix of collations for operation 'UNION' for query
This error is actually talking about a mix of collations so it's likely the 2 errors are related and THIS could actually be why the users are seeing the errors you mentioned sometimes, they are not happening every time but they are happening and these errors do break the site for a moment. They are also making the site slower than usual and taking up resources so fixing them should make the site more stable and probably faster 🙂
There are also a few errors about WooCommerce either not finding some files (in this case you can reinstall WooCommerce) or not being able to access it (server permission issue which can be handled by your hosting)
You also have many other errors, and you can filter them by searching for "Error", those are the ones breaking your site and you have many but none of them are actually WPML related.
