|
stateconadmin
|
January 3, 2025 at 10:56 am
I have a similar issue to the following support forum posts.
https://eventespresso.com/topic/translation-loading-for-the-event_espresso-domain-was-triggered-too-early-2/
https://eventespresso.com/topic/translation-loading-for-the-event_espresso-domain-was-triggered-too-early/
I am unable to register anyone new. Can you help me understand the issue and if there is an update to these tickets with a solution?
|
|
stateconadmin
|
January 3, 2025 at 11:04 am
On the web site home page I have the following errors at the top. Page does load
https://coloradoaa.org/convention/
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 /home2/coloraj1/public_html/convention/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 /home2/coloraj1/public_html/convention/wp-includes/functions.php on line 6114
Warning: session_start(): Session cannot be started after headers have already been sent in /home2/coloraj1/public_html/convention/wp-content/plugins/event-espresso-core-reg/core/services/session/SessionStartHandler.php on line 65
|
|
stateconadmin
|
January 3, 2025 at 11:06 am
Going to the registration page which is of course the first real use of the event espresso plugin. I get
On the web site home page I have the following errors at the top. Page does load (Currently there are not errors as the event espresso plugin is disabled)
https://coloradoaa.org/convention/?p=2237
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 /home2/coloraj1/public_html/convention/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 /home2/coloraj1/public_html/convention/wp-includes/functions.php on line 6114
Warning: session_start(): Session cannot be started after headers have already been sent in /home2/coloraj1/public_html/convention/wp-content/plugins/event-espresso-core-reg/core/services/session/SessionStartHandler.php on line 65
|
|
stateconadmin
|
January 3, 2025 at 11:08 am
When the plugin is enabled the page
https://coloradoaa.org/convention/?p=2237
Does not load correctly and I can not register anyone.
Also the when enabled I am unable to access the admin page.
https://coloradoaa.org/convention/wp-admin
Could really use any help you can give as I am completely down.
|
|
Tony
|
January 3, 2025 at 3:15 pm
Hi there,
There’s 2 issues here.
The reason those warnings/notices are being thrown is that WordPress changed when they allow for translations to be run in version 6.7, its 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, whih 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?
|
|
stateconadmin
|
January 3, 2025 at 3:40 pm
Ok I will give this a try, thank you.
|
|
Tony
|
January 3, 2025 at 3:42 pm
You’re most welcome.
If you get stuck or your unsure just post a screenshot of what you have in a private reply and I’ll take a look.
|
|
stateconadmin
|
January 3, 2025 at 4:00 pm
Your suggestion worked like a charm, thank you so much for this timely repsonse.
On the statement.
You don’t want to display errors/warnings/notices directly on the site itself but rather log them and review them in the logs.
How do a setup these errors to go to a log and where are they located.
Again Thank you
|
|
Tony
|
January 3, 2025 at 4:28 pm
You’re most welcome.
So generally your host will already have set up the server to log PHP errors within a error_log (or similar) file, somewhere outside of the ‘regular’ directories.
It could be within the root directory of your site, or they may store them separately and have a section for your to view them.
Who are you hosting with?
|
