This thread is resolved. Here is a description of the problem and solution.
Problem:
After updating the WPML Multilingual CMS plugin to version 4.8.3, the WordPress admin page stops functioning, although the frontend still works. Reverting to version 4.7.4 resolves the issue.
Solution:
The issue does not stem from WordPress itself but likely from other plugins that may not be compatible with the new WPML version. Here are the steps we recommend:
1. Update all other plugins to their latest versions, especially those mentioned in the error logs.
2. If the issue persists, switch to a default WordPress theme like TwentyTwenty-Four and deactivate all plugins except for WPML and WooCommerce.
3. Reactivate other plugins one by one to identify the one causing the conflict.
4. If a specific plugin is identified as the cause, contact the plugin author for further support.
5. Ensure to back up your site fully before making these changes, especially if it is a live site. Consider performing these steps in a staging environment.
If these steps do not resolve the issue or if the solution seems outdated, please visit our known issues page and check for any related updates. If necessary, do not hesitate to open a new support ticket with us.
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: Not WPML issue
This topic contains 3 replies, has 0 voices.
Last updated by Itamar 5 months, 1 week ago.
Assisted by: Itamar.
| Author | Posts |
|---|---|
| October 20, 2025 at 12:30 pm | |
 danijelH |
Background of the issue: Symptoms: Questions: |
| October 22, 2025 at 6:33 pm #17509841 | |
 Itamar WPML Supporter since 02/2016 Languages: Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+03:00) |
Hi, I've made two separate attempts to take a copy of your site. My first attempt was with the All-in-One migration plugin. Although I applied filters, the created package was 33GB, and I couldn't work with it. The second attempt was with the Duplicator Pro plugin. I could generate a much smaller package by applying filters. However, when I installed it on my local server, I received a fatal error. Today, we released a new version of WPML, along with a new version of WPML Multilingual & Multicurrency for WooCommerce. Please see the attached screenshot. Please take a backup of your site and update our plugins. Then please check if the problem persists. Before doing that, please enable WordPress debug.log. In this way, we will be able to "catch" PHP errors if they occur after the update. To enable it, open your wp-config.php file and look for
define('WP_DEBUG', false);
Change it to:
define('WP_DEBUG', true);
// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);
// Disable display of errors and warnings
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
After this, update our plugins. If the problem occurs again, errors will be saved to a debug.log log file inside the /wp-content/ directory. Then please share the errors with us. Please only share the error you encountered during your test to keep the log concise and avoid unrelated errors. |
| October 26, 2025 at 11:05 am #17519316 | |
|
danijelH |
I tried but its the same arror. Debug is: [26-Oct-2025 11:03:23 UTC] PHP Deprecated: Creation of dynamic property PS_Checkout_Terms_Conditions_Popup::$ps_wp_fields is deprecated in /home/ehomesi/public_html/wp-content/plugins/woocommerce-ps/classes/class-ps-checkout-terms-conditions-popup.php on line 59 hide-login-page 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 meta-box 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/ehomesi/public_html/wp-includes/functions.php on line 6121 hide-login-page 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wbcr_factory_pages_473 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wbcr_factory_templates_126 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/ehomesi/public_html/wp-includes/functions.php on line 6121 checkout-upsell-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 /home/ehomesi/public_html/wp-includes/functions.php on line 6121 hide-login-page 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 meta-box 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/ehomesi/public_html/wp-includes/functions.php on line 6121 hide-login-page 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wbcr_factory_pages_473 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wbcr_factory_templates_126 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/ehomesi/public_html/wp-includes/functions.php on line 6121 checkout-upsell-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 /home/ehomesi/public_html/wp-includes/functions.php on line 6121 hide-login-page 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 checkout-upsell-woocommerce pokrenuto je prerano. To je obično pokazatelj da se neki kôd u dodatku ili temi prerano pokreće. Prijevodi bi se trebali učitati nakon akcije init ili kasnije. Vidite Ispravljanje grešaka u WordPressu za više informacija. (Ova poruka je dodana u inačici 6.7.0.) in /home/ehomesi/public_html/wp-includes/functions.php on line 6121 hide-login-page 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 woo-feed 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/ehomesi/public_html/wp-includes/functions.php on line 6121 hide-login-page 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 checkout-upsell-woocommerce pokrenuto je prerano. To je obično pokazatelj da se neki kôd u dodatku ili temi prerano pokreće. Prijevodi bi se trebali učitati nakon akcije init ili kasnije. Vidite Ispravljanje grešaka u WordPressu za više informacija. (Ova poruka je dodana u inačici 6.7.0.) in /home/ehomesi/public_html/wp-includes/functions.php on line 6121 hide-login-page 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 wpbm 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/ehomesi/public_html/wp-includes/functions.php on line 6121 checkout-upsell-woocommerce se je sprožilo prezgodaj. To je običajno znak, da se neka koda v vtičniku ali temi izvaja prezgodaj. Prevodi bi se morali naložiti ob dejanju init ali kasneje. Za več podrobnosti si oglejte razhroščevanje v WordPressu. (To sporočilo je bilo dodano v izdaji 6.7.0.) in /home/ehomesi/public_html/wp-includes/functions.php on line 6121 |
| October 28, 2025 at 2:08 pm #17526450 | |
|
Itamar WPML Supporter since 02/2016 Languages: Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+03:00) |
Hi, Thanks for sharing these errors with us. None of these errors point to WPML or any of its add-ons being the culprit of this problem. However, they do point to many other plugins you are using. One of the errors that repeats itself many times is: PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. WPML does not cause it. We explain about this error here: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/. The solution for this should be to update those mentioned plugins to their latest versions. If the authors of those plugins have not corrected the _load_textdomain_just_in_time error in their file, you should contact them regarding this error. Furthermore, there are two other errors I see: 'Creation of dynamic property PS_Checkout_Terms_Conditions_Popup::$ps_wp_fields is deprecated', and 'PHP Deprecated: Creation of dynamic property CJAPI_TrackingSettingsPage::$integrations_installed is deprecated'. Those errors are also related to other plugins; you should update them. If you want to proceed with finding the culprit plugin and determining whether the collision is with WPML, please follow the steps below. If possible, get your site into a minimum environment, switching to a default WordPress theme like TwentyTwenty-Four and having no plugins activated except WPML. First, you must check if the problem persists when just the theme is switched to TwentyTwenty-Four (for example). If it persists, deactivate all plugins except WPML and its add-ons and WooCommerce without any extensions. Then, please check if the problem persists. If it does not continue, start by activating the plugins individually and checking when the issue comes back, then report to me which plugin was the culprit. |
