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.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 12:00 – 16:00 | 10:00 – 14:00 | 10:00 – 14:00 | 9:00 – 13:00 | 9:00 – 13:00 | - |
- | 17:00 – 21:00 | 15:00 – 19:00 | 15:00 – 19:00 | 14:00 – 18:00 | 14:00 – 18:00 | - |
Supporter timezone: Europe/Bucharest (GMT+02:00)
Tagged: Exception
This topic contains 7 replies, has 2 voices.
Last updated by kevinB-74 14 hours, 51 minutes ago.
Assisted by: Mihai Apetrei.
Author | Posts |
---|---|
November 20, 2024 at 9:07 am #16423203 | |
kevinB-74 |
Background of the issue: Symptoms: Questions: |
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: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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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: 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:
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: 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, |
November 26, 2024 at 8:43 am #16443322 | |
kevinB-74 |
Regarding "_load_textdomain_just_in_time" warning. I switched theme and disabled all plugins. Regards, |