Make WordPress Core

Opened 6 months ago

Closed 6 months ago

Last modified 6 months ago

#62493 closed defect (bug) (worksforme)

notices: _load_textdomain_just_in_time was called incorrectly

Reported by: pieterdw's profile pieterdw Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.7
Component: I18N Keywords:
Focuses: Cc:

Description (last modified by sabernhardt)

hi team

After the automatic update to 6.7, my website functionality always gets impacted. I have here below copied the error messages. The specific website is www.paard-en-bloem.be. I have updated to a back-up version of before 6.7 and everything works fine this way again. Automatic updates brought back the fault over and over. Automatic update should now be stopped until this issue is resolved.

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-seo-pack 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 
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the google-analytics-for-wordpress 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 
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the 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.
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the mollie-payments-for-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 
Warning: Cannot modify header information - headers already sent by (output started at /.../wp-includes/functions.php:6114) in /.../wp-admin/includes/misc.php on line 1438 
Warning: Cannot modify header information - headers already sent by (output started at /.../wp-includes/functions.php:6114) in /.../wp-includes/functions.php on line 7137 
Warning: Cannot modify header information - headers already sent by (output started at /.../wp-includes/functions.php:6114) in /.../wp-admin/admin-header.php on line 9

Change History (2)

#1 @swissspidy
6 months ago

  • Component changed from Site Health to I18N
  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Severity changed from critical to normal
  • Status changed from new to closed

Hi there and welcome to Trac!

Please note that these are not errors and not even warnings, just notices. The notice says a plugin is loading translations too early, which is now flagged in 6.7. So it’s not sonething in core itself. Developers can learn more about that at https://make.wordpress.org/core/2024/10/21/i18n-improvements-6-7/

Most plugins have already fixed their code, so try updating yours to the latest versions. For others, you can reach out to the individual plugin‘s support and point them to the above article (if they‘re not already aware)

#2 @sabernhardt
6 months ago

  • Description modified (diff)
  • Keywords needs-patch removed
  • Summary changed from Twentyseventeen theme - in Dutch - language adress to notices: _load_textdomain_just_in_time was called incorrectly
Note: See TracTickets for help on using tickets.