• Resolved neowebmaster

    (@neowebmaster)


    I can’t find any solutions to this issue:

    PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woo-cart-abandonment-recovery 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 /opt/bitnami/wordpress/wp-includes/functions.php on line 6121

    Running WordPress 6.8.1 and Woo 9.9.4

    Causes the debug log to create errors continuously.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter neowebmaster

    (@neowebmaster)

    Updated to Version: 1.3.3 and still have the same issue.

    Plugin Support Aamir

    (@aamiribsf)

    Hello @neowebmaster,

    Thank you for reaching out and reporting this issue.

    The issue that you reported appears to be related to this.

    Notice: Function _load_textdomain_just_in_time was called incorrectly

    was introduced in WordPress 6.7.0. With this update, WordPress expects all translation files to be loaded at or after the init action, and not before.

    We want to reassure you that:

    • This is a non-fatal notice, meaning it does not affect the functionality of your site.
    • Your checkout should continue working as expected.
    • The notice is appearing due to a change introduced by WordPress, and our development team is already reviewing the code to ensure full compatibility with these new standards.

    Incase you are seeing some notices related to this on your site, If you’d prefer to hide such notices on your live site, you can do so by updating your wp-config.php file like this:define( ‘WP_DEBUG’, true ); define( ‘WP_DEBUG_DISPLAY’, false );

    This keeps the notices logged for internal use without displaying them on your site’s frontend or admin area.

    Hope ths helps.

    Best regards,

    Hey, I’m still seeing this after updating to 1.3.3. Would you be open to a pull request if I can track down the bug?

    Thread Starter neowebmaster

    (@neowebmaster)

    I am also still having this issue with these updated settings:

    WordPress 6.8.2
    WooCommerce 10.0.2
    WooCommerce Cart Abandonment Recovery 1.3.3

    Just to follow up. I’m still seeing this after upgrading to 2.0.0. I don’t think it would be too hard to track down if you would be open to a PR. Just let me know.

    Plugin Support Herman Asrori (BSF)

    (@bsfherman)

    Hi guys,

    This has been fixed in the update we just released. Please update the plugin and you will no longer see the notice.

    Kind regards,
    Herman 😊

    Wahoo! Thank you so much for taking care of this. It’s much appreciated. 🙂

    Thread Starter neowebmaster

    (@neowebmaster)

    I can confirm that this is fixed. Thank you for your help on this!

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

You must be logged in to reply to this topic.