Translation loading triggered too early

[grahamh]

GM all. I’m getting this message – annoyingly on the public site, not just in the dashboard.  There’s a similar one for wpforms-lite. Any ideas how to fix it?

<b>Notice</b>: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the weaver-xtreme 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 <b>/var/www/vhosts/stanfordpc.org.uk/httpdocs/wp-includes/functions.php</b> on line <b>6114</b>

Note to self: turn off WP automatic updates.

Graham

[scrambler]

@weaver would have to comment

[User]

@grahamh

A couple of suggestions that may help improve the front-end appearance while the issue is resolved.

1. The “WP Rollback” plugin will allow you to roll back plugins etc. to older working versions until you have a solution to the root cause of the problem.

2. Turn the debug display off.

// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Regards.

[grahamh]

Thanks, but (1) the messages suggest it’s WP itself that needs rolling back. It looks as if the problem was there for a while but has only been revealed by WP 6.7.  And (2) that code hasn’t got rid of the messages.

I set WP_DEBUG false.  Got rid of the messages but still it would be good to get a proper fix.

[Weaver]

This reply has been accepted as the best answer.

I think that this issue  is unlikely to be caused by the WeaverXtreme theme.

My dev site runs WP 6.7. I switched to non-English language support to force translations to be loaded. I get no error messages.

We aren’t getting other reports for our users.

So, this may be one of your plugins, or a host site issue.

I would suggest the following procedure:

Disable your plugins, then re-enable one at a time to see when the error message comes back.

You would probably need to re-enable WP_DEBUG.

You can disable all plugins, or disable one or a few at a time.

 

[User]

@grahamh

Just been checking WP forums and seems like WP6.7 has kinda caused chaos among plugins.

Based on what I’ve read, I think a bit of checking of plugins will still be required after the Weaver-Xtreme update.

Good to see your site looking back to normal though!

Regarding your comment about turning off updates, I don’t think that can be done on the core WP…

I certainly do that on my main site for the theme and pkugins, so I can do all updates when I am there to monitor it all, and during a quite time for readers, just in case bad things happen.

Regards.

[User]

@grahamh

Just been checking WP forums and seems like WP6.7 has kinda caused chaos among plugins.

Based on what I’ve read, I think a bit of checking of plugins will still be required after the Weaver-Xtreme update.

Good to see your site looking back to normal though!

Regarding your comment about turning off updates, I don’t think that can be done on the core WP…

I certainly do that on my main site for the theme and pkugins, so I can do all updates when I am there to monitor it all, and during a quite time for readers, just in case bad things happen.

But the collective wisdom is to keep sites up to date for security reasons.

Regards.

[grahamh]

Thanks for checking @weaver. I’ll take a look at wpforms.

.. that was indeed the culprit. Apologies for the bandwidth and thanks to @user

[Author]

Posts