• Resolved murrayelliot2

    (@murrayelliot2)


    Been using WordPress 6.4.5 for some time, but when I upgrade to 6.7.1 on my Dev site I’m getting an error – same error with Hestia 3.2.2 and 3.2.6

    All pages display the following:
    Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?hestia?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?/var/www/clients/client3/web28/web/wp-includes/functions.php?on line?6114

    Anyone else experiencing, or solved this issue?

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Yes, I just did and it brought down my staging site

    I’ve turned off the offending plugin (smart coupons) and the problem has gone away though I’ve a feeling that’s not the issue exactly

    here’s the error:

    PHP Notice Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wt-smart-coupons-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.)

    Any questions let me know

    UPDATE: Fixed

    needed to reinstall the plugin, so it must have been out of date or bad internal state

    I’ve turned off automatic updates to the WP core

    Hi,

    Thank you for the update! We are working on an update that should fix all issues related to the latest WP release.

    Kind regards,

    Rodica

    simonsayspt

    (@simonsayspt)

    Hi
    i am also getting a Critical Error after 6.7.1 update of wordpress..

    “Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the hestia domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early”

    Any updates near..?
    Thank you.
    ??

    rodicaelena

    (@rodicaelena)

    Hi there,

    This should be fixed in the latest update of Hestia 3.2.7.

    If you are still experiencing this issue, it may also be a good idea to disable debugging on your site https://docs.themeisle.com/article/819-how-to-turn-on-off-debugging-in-wordpress as it’s not a good idea to have it on, on a live site. Your hosting provider should be able to help with that.

    Kind regards,

    Rodica

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