WP 6.7; Function _load_textdomain_just_in_time was called incorrectly

  • This error is triggered and triggered and triggered:
    Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-pagenavi 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/30/d124584246/htdocs/wp/wp-includes/functions.php on line 6114

    Please, let me know, if you fixed it.

    Right now, to stop the debug messages from that I’m using:
    add_filter( ‘doing_it_wrong_trigger_error’, ‘__return_false’ );

    cheers

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

  • Hi, same issue here, with 6.7 WP und WP-PageNavi Version 2.94.2?:
    Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?wp-pagenavi?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?/html/wp-includes/functions.php?on line?6114

    greets

    Hi, facing the same issue with Version 2.94.2 on multiple sites:

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-pagenavi 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 /Users/*****/Sites/*****/web/wp/wp-includes/functions.php on line 6114

    It would be much appreciated if you could release a fix for this as soon as you possible.

    Thread Starter treibstoff

    (@treibstoff)

    thanx,
    you updated you plugin and it works now.
    and you did nothing else, as I did before to avoid the messages about textdomain:
    you cut out the function pagenavi_textdomain() ’cause you probably will never use translated strings.
    cheers

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.