|
westcoastnaturalshows
|
December 30, 2024 at 12:12 pm
Currently receiving these 2 error messages at the top of my website, I found a similar post from November but did not see any posted fixes yet so hoping you guys can help! These appear as soon as the plugin is activated, and disappear if I disable it temporarily.
At the top of my site I get the following 2 errors:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-graphql 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 /var/www/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the event_espresso 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 /var/www/wp-includes/functions.php on line 6114
Warning: foreach() argument must be of type array|object, string given in /var/www/wp-content/plugins/event-espresso-core-reg/core/services/notifications/PersistentAdminNoticeManager.php on line 122
|
|
stateconadmin
|
January 3, 2025 at 7:51 am
I am having the same issue.
|
|
Tony
|
January 3, 2025 at 4:29 pm
Hi there,
The reason those warnings/notices are being thrown is that WordPress changed when they allow for translations to be run in version 6.7, it’s caused a whole bunch of issues with translations across WordPress themes/plugins and they reverted part of those changes in 6.7.1 but left those notices in.
We (EE) need to push an update out to prevent those notices from throwing (we already have a ticket with changes in the pipeline).
However, the fact that they are displaying on your live site means your server is set to display errors, which isn’t great. You don’t want to display errors/warnings/notices directly on the site itself but rather log them and review them in the logs. Outputting them to the page like this causes issues like what you are currently running into (the cause of your current problems is the notices being output).
Yes, we need to fix this, and the notices are there for a reason, but you don’t want your production (live) site outputting those like this.
Do you have file access to the site?
If so look in your wp-config.php file for something like:
define( ‘WP_DEBUG’, true );
Set that to be false:
define( ‘WP_DEBUG’, false );
Or if your host allows you to set WP_DEBUG within your control panel, do so there. That will prevent them being output to the page, do you still run into issues then?
|
