Maximum execution time exceeded

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

Problem:
The client is experiencing a 'Maximum execution time exceeded' error when accessing their website with WPML enabled. Additionally, there are notices about the function

_load_textdomain_just_in_time

being called incorrectly, which is related to early translation loading in WordPress.
Solution:
1. For the maximum execution time issue, we recommend following the steps outlined in this documentation: https://wpml.org/forums/topic/maximum-execution-time-of-180-seconds-exceeded/.
2. Update WordPress, WooCommerce, and all WPML plugins to their latest versions. Instructions for updating can be found here: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/.
3. If the issue persists, especially with the

_load_textdomain_just_in_time

error, consider deactivating all other plugins and switching the theme to isolate the issue. This should ideally be done in a staging environment.
4. Contact the support team for the WooCommerce Wholesale Prices plugin if the error reoccurs when this plugin is enabled.
5. If problems continue, consult with your hosting provider to review server logs and possibly increase memory limits or execution times.

If these steps do not resolve your issues or if the information provided here becomes outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket at https://wpml.org/forums/forum/english-support/.

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 8 replies, has 2 voices.

Last updated by Mihai Apetrei 1 month, 1 week ago.

Assisted by: Mihai Apetrei.

Author	Posts
November 20, 2024 at 9:07 am #16423203
kevinB-74	Background of the issue: I am trying to access my website, but I encounter an error. The issue does not occur when I disable WPML. The problem can be seen at: hidden link Symptoms: Maximum execution time exceeded error when accessing the website. Questions: Why does the maximum execution time error occur when WPML is enabled? How can I resolve the maximum execution time exceeded error?
November 20, 2024 at 9:08 am #16423223
kevinB-74	I get this kind of error in log : [20-Nov-2024 08:23:06 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /*/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 2642 [20-Nov-2024 08:23:54 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in //wp-includes/class-wp-hook.php on line 324 [20-Nov-2024 08:23:55 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in //wp-content/plugins/sitepress-multilingual-cms/classes/request-handling/class-wpml-language-resolution.php on line 64 ------------------- [20-Nov-2024 08:30:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the schema-and-structured-data-for-wp 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 [20-Nov-2024 08:30:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the temporary-login-without-password 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 [20-Nov-2024 08:30:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woo-product-feed-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 [20-Nov-2024 08:30:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-wholesale-prices 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 [20-Nov-2024 08:30:54 UTC] PHP 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 [20-Nov-2024 08:30:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging 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 [20-Nov-2024 08:30:54 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check 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 [20-Nov-2024 08:30:54 UTC] PHP 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 [20-Nov-2024 08:30:55 UTC] PHP Notice: La fonction _load_textdomain_just_in_time a été appelée de façon incorrecte. Le chargement de la traduction pour le domaine astra a été déclenché trop tôt. Cela indique généralement que du code dans l’extension ou le thème s’exécute trop tôt. Les traductions doivent être chargées au moment de l’action init ou plus tard. Veuillez lire Débogage dans WordPress (en) pour plus d’informations. (Ce message a été ajouté à la version 6.7.0.) in //wp-includes/functions.php on line 6114 [20-Nov-2024 08:30:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the schema-and-structured-data-for-wp 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 [20-Nov-2024 08:30:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the temporary-login-without-password 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 [20-Nov-2024 08:30:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woo-product-feed-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 [20-Nov-2024 08:30:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-wholesale-prices 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 [20-Nov-2024 08:30:56 UTC] PHP 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 [20-Nov-2024 08:30:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging 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 [20-Nov-2024 08:30:56 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check 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 [20-Nov-2024 08:30:56 UTC] PHP 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 [20-Nov-2024 08:30:57 UTC] PHP Notice: La fonction _load_textdomain_just_in_time a été appelée de façon incorrecte. Le chargement de la traduction pour le domaine astra a été déclenché trop tôt. Cela indique généralement que du code dans l’extension ou le thème s’exécute trop tôt. Les traductions doivent être chargées au moment de l’action init ou plus tard. Veuillez lire Débogage dans WordPress (en) pour plus d’informations. (Ce message a été ajouté à la version 6.7.0.) in /**/wp-includes/functions.php on line 6114
November 20, 2024 at 11:27 pm #16426776
Mihai Apetrei Supporter Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00)	Hi there. Regarding the maximum execution time, please follow my colleague's steps here and see if that will help you resolve the issue: https://wpml.org/forums/topic/maximum-execution-time-of-180-seconds-exceeded/ Also, I can see a notice (La fonction _load_textdomain_just_in_time), which is related to a recent WordPress update (not WPML), and we have a yellow block at the top of this page regarding that: WordPress 6.7 has introduced a new issue that impacts translations; please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ So, I recommend first creating a full website backup and then updating WordPress, WooCommerce, and all the WPML plugins to the latest versions (you can go to Plugins > Add new > Commercial > click the "check for updates" button > and update the WPML plugins to the latest version). Please let me know how things go and if these steps helped you resolve the issue. I will be waiting for your reply. Mihai Apetrei
November 22, 2024 at 8:38 am #16432310
kevinB-74	Hi, Regarding _load_textdomain_just_in_time I still have the issue event after upgrading my version.
November 22, 2024 at 8:41 am #16432328
kevinB-74	Regarding "PHP Fatal error: Allowed memory size exhausted" it is hard to diagnose because it doesn't happen all the time... I don't know how to reproduce. But it happen 3-4 times a day
November 25, 2024 at 5:05 pm #16441391
Mihai Apetrei Supporter Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00)	Hi there, and thank you for the update. Regarding the "_load_textdomain_just_in_time" error, please take a look at the workaround section here: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ Make sure that WooCommerce and WordPress are also on the latest versions. There's also a chance another plugin is causing that error because since WordPress 6.7 was launched, there have been issues with many plugins in the market. You could try to create a full website backup and then leave just WPML active (also change the main theme to a different one) and see if the issue is still happening. It would be best to do this on a staging/testing environment, if possible. Regarding the other error, I understand. It's common for this to happen randomly because the memory runs out only occasionally when the server limits are reached. I recommend contacting hosting support and asking them to take a deeper look at the logs. Then, have them increase the memory or limits that are being reached, causing that error.
November 26, 2024 at 8:24 am #16443081
kevinB-74	Hi, Regarding PHP issue we already worked on it with hoster: we set max execution time to 300 and we still got issues. We increased PHP memory limit also and same issue...
November 26, 2024 at 8:43 am #16443322
kevinB-74	Regarding "_load_textdomain_just_in_time" warning. I switched theme and disabled all plugins. No error. But if I enaable "WooCommerce Wholesale Prices" the error come back. How to solbe it? Regards,
November 29, 2024 at 12:33 am #16457249
Mihai Apetrei Supporter Languages: English (English ) Timezone: Europe/Bucharest (GMT+02:00)	Hi there. It seems that that plugin (WooCommerce Wholesale Prices) created the loadtext issue. I recommend that you contact the support team because they probably already have a quick fix that they can share with you. Regarding the max execution time, there's a change that value needs to be increased even more. Still, there's also a chance that this issue could be caused by other active plugins (especially if we have many active plugins that are pretty resourceful - as plugins created for WooCommerce usually are). Please let me know how things go.