• Resolved bobjgarrett

    (@bobjgarrett)


    I am getting the following error repeatedly.

    [06-Oct-2025 11:07:29 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the adventurous 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 /home/dufour/P4ML4XO9/htdocs/wp-includes/functions.php on line 6121

    The theme author is suggesting a clash with a plugin and QueryMonitor suggests

    Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the bbpress-notify-nospam 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. (This message was added in version 6.7.0.)

    1. _load_textdomain_just_in_time()

    Is this something that can be fixed?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author useStrict

    (@usestrict)

    Thanks for reporting this. Not sure why I can’t replicate this locally, but I did release an attempt at a fix with version 2.19.5. Please let me know if that fixes things for you.

    Cheers,
    Vinny

    Thread Starter bobjgarrett

    (@bobjgarrett)

    Yes, I can confirm the problem still exists with the latest update. Hope you can fix it.

    Plugin Author useStrict

    (@usestrict)

    Hi @bobjgarrett ,

    Please update to version 2.20 for the final fix.

    Cheers,
    Vinny

    Thread Starter bobjgarrett

    (@bobjgarrett)

    The problem still seems to be there with the new release.

    Plugin Author useStrict

    (@usestrict)

    Can you paste the error message, please?

    Note that your original message referenced ‘adventurous‘ domain – this is not mine. The warnings I fixed are regarding bbpress-notify-nospam domain.

    Thread Starter bobjgarrett

    (@bobjgarrett)

    Apologies, having run Query Monitor the error messages now seem to be coming from a different plugin.

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

You must be logged in to reply to this topic.