• Resolved zaidibinhusin

    (@zaidibinhusin)


    I have update my WordPress version from 6.7.0 to 6.7.1. After successfully upgrade, my page display with this error:

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the 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.) in /home/cikgutay/public_html/wp-includes/functions.php on line 6114

    Now I revert back to previous version and the error message disappear. Kindly advise on how to fix this error so that I can update my WordPress to the latest version 6.7.1.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Hi @zaidibinhusin,

    Thank you for reaching out.

    I can confirm the issue was fixed here, and it will be available in our next WooCommerce release.

    Thank you for your patience and understanding.

    @ckadenge will this be in the next minor or major release? I am waiting for this update before attempting an update of wordpress. Any idea if it will be this week or next week?

    Hi

    We are unable to provide a specific timeline for whether the update will be included in the next minor or major release. Our development team is working diligently to roll out updates as soon as possible.

    We recommend keeping your WordPress and WooCommerce installations up-to-date for optimal performance and security. We highly recommend updating your WooCommerce and WordPress versions in a staging site for testing before moving the updates to your live website.

    I hope this clarifies your concerns.

    Thread Starter zaidibinhusin

    (@zaidibinhusin)

    Hi @ckadenge just want to follow up whether this issue already release to production? I just try to update the WordPress but the issue still persist. Kindly advise.

    Hi @zaidibinhusin,

    Thanks for reaching out.

    This issue seems related to a known problem currently under investigation by our developers: GitHub Issue #52646. From what we’ve observed, this seems to occur when the primary site language is set to something other than English. Could you confirm if your site language is set to something other than English?

    At the moment, we don’t have an active workaround. However, you could temporarily disable WP Debug mode and share your findings directly in the GitHub issue linked above. Your input could help our developers resolve this more quickly.

    Thank you for your understanding, and we appreciate your patience while we work on this!

    Thread Starter zaidibinhusin

    (@zaidibinhusin)

    Hi @jonayedhosen

    Thank you for your updates. As per checking my WordPress primary language is set as English (United States).

    I have done some troubleshooting where I install fresh installation of WordPress version 6.7.1 and after that install WooCommerce plugin, the issue is not happen. From this, I assume that upgrading process from version 6.6.2 or 6.7.0 to 6.7.1 may cause the issue.

    Hi @zaidibinhusin

    Thanks for doing some troubleshooting on your end, we appreciate you for sharing your findings. Just to confirm, when you did a fresh install of WordPress version 6.7.1, the issue didn’t happen? Does this mean the error is now resolved with this approach?

    Looking forward to your response.

    Thread Starter zaidibinhusin

    (@zaidibinhusin)

    Hi @reynierc

    Yes, the issue resolved with this approach. Actually I have 2 plugins getting the same issue in my WordPress 6.70 and both plugin issue didnt happen again. If I want to proceed with this approach, I need to migrate all the production data together with customize module that I develop in my current production environment and this is very challenging. Due to that I will wait the fixes release.

    Hi @zaidibinhusin ,

    Thanks for the update! It seems some old error logs are still appearing on your site, which might be due to caching. To address this, let’s try the following troubleshooting steps by navigating to WooCommerce > Status > Tools:

    • Clear WooCommerce transients
    • Clear expired transients
    • Clear template cache
    • Reset capabilities
    • Clear customer sessions
    • Regenerate product lookup tables
    • Regenerate the product attributes lookup table

    In addition, ensure you clear all caching at every level—browser, site, and server. This guide provides helpful instructions: How to Clear Your Cache in WordPress.

    Please give these steps a try and let us know if they resolve the issue.

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

The topic ‘Getting error after update WordPress 6.7.1’ is closed to new replies.