WordPress 6.8. Update Issues

  • Resolved Mario

    (@marioblum)


    1 year, 1 month ago

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf 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 /homepages/17/d254961246/htdocs/2023/wp-includes/functions.php on line 6121

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordfence 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 /homepages/17/d254961246/htdocs/2023/wp-includes/functions.php on line 6121

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/17/d254961246/htdocs/2023/wp-includes/functions.php:6121) in /homepages/17/d254961246/htdocs/2023/wp-includes/pluggable.php on line 1450

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/17/d254961246/htdocs/2023/wp-includes/functions.php:6121) in /homepages/17/d254961246/htdocs/2023/wp-includes/pluggable.php on line 1453

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Mario

    (@marioblum)

    1 year, 1 month ago

    And this after removing Wordfence Plugin:

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf 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 /homepages/17/d254961246/htdocs/2023/wp-includes/functions.php on line 6121

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/17/d254961246/htdocs/2023/wp-includes/functions.php:6121) in /homepages/17/d254961246/htdocs/2023/wp-includes/pluggable.php on line 1450

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/17/d254961246/htdocs/2023/wp-includes/functions.php:6121) in /homepages/17/d254961246/htdocs/2023/wp-includes/pluggable.php on line 1453

    Moderator threadi

    (@threadi)

    1 year, 1 month ago

    These PHP notices (not errors) appear because some of your plugins are not compatible with changes in WordPress 6.7.x. To solve this you can:

    • Install all pending updates. The theme and plugin developers may have already provided a fix.
    • Disable the output of PHP notices. This either happens because your WordPress is running in debug mode OR your hosting is outputting PHP errors. The support of your hoster might help here.
    • Or downgrade to WordPress 6.6.2 and then wait some time until you go back to 6.8.x until the plugin developers have caught up.
    • Or simply wait until the plugin developers make changes in this regard.

    See also the information from the core developers about the upcoming changes for plugin developers from a few months ago: https://make.ww.wp.xz.cn/core/2024/10/21/i18n-improvements-6-7/

    throwaway111

    (@throwaway111)

    1 year, 1 month ago

    I, too, am getting scads of the “Function _load_textdomain_just_in_time was called incorrectly.” messages. This is on my dev site and I intentionally have error reporting turned on to check for issues.

    The thing is, I know a bunch of these are using the init hook or later because I went through all the plugins and reported this issue to developers after the notice was first introduced in WP 6.7. One of the plugins triggering this message is one I wrote myself, and it uses the init hook. It’s a textbook implementation of plugin_load_textdomain(). There does seem to be a deeper issue that appeared with the WP 6.8 update.

    Moderator threadi

    (@threadi)

    1 year, 1 month ago

    @throwaway111: I would recommend that you open a separate topic for this in accordance with the forum rules and show your specific example with your plugin there so that it can be checked separately and you can be helped: https://ww.wp.xz.cn/support/forum/how-to-and-troubleshooting/#new-topic-0

    throwaway111

    (@throwaway111)

    1 year, 1 month ago

    Thanks, I wasn’t requesting help here. I was affirming Mario’s experience as something that maybe should not be dismissed out of hand. I am also running ACF (Pro) and Wordfence. If Mario has recent versions installed, I don’t think he should be encountering textdomain errors.

    I noticed this morning that a ticket related to this issue was submitted on Trac maybe three weeks ago, and it was similarly categorized as a plugin issue and closed.

    Thread Starter Mario

    (@marioblum)

    1 year, 1 month ago

    Thanks @throwaway111 and @threadi. After updating the ACF plugin, the textdomain errors are gone

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘WordPress 6.8. Update Issues’ is closed to new replies.