Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Mohammed Jamsheed KM

    (@jamsheedkm)

    Hi All,

    Please check the issue with only the WooCommerce plugin installed. From WooCommerce version 9.4.0-rc.2 onward, this issue is reportedly fixed.

    Additionally, the warning/error you’re encountering might be caused by some of your other WooCommerce-related plugins. These plugins could be using the same text domain woocommerce in their code. If they are calling the WooCommerce text domain too early—like directly in the constructor function or during the plugins_loaded hook—this can trigger the warning.

    To resolve this:

    1. Disable all WooCommerce-related plugins except WooCommerce itself and translate a WooCommerce page
    2. Test if the issue still occurs.
    3. If it’s resolved, enable other plugins one by one to identify the problematic one.

    If the issue persists with just WooCommerce and the translation plugin, update WooCommerce to the latest stable version as the problem might already be patched.

    Let me know if you need more clarification or steps!

    Thread Starter Mohammed Jamsheed KM

    (@jamsheedkm)

    Hi there,

    I tested the issue with WooCommerce version 9.4.0-beta.2 and WordPress 6.7-beta3-59237, but the error is still occurring:

    PHP 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 /Applications/MAMP/htdocs/support/wp-includes/functions.php on line 6099

    The issue appears specifically on translated WooCommerce pages, but it does not occur when using the default English language.

    I have already reported this in the WooCommerce GitHub issues, and we hope it will be addressed in the 9.4.0 release.


    Thanks for your support!

    Thread Starter Mohammed Jamsheed KM

    (@jamsheedkm)

    Hey,

    Thanks for testing the issue. I believe you can reproduce it by visiting a translated WooCommerce page. The issue likely occurs because the load_plugin_textdomain function is being called too early, before the plugin is fully loaded.

    I recommend using the init hook instead of the plugins_loaded hook for loading text domains. This aligns with WordPress 6.7 requirements, which specify that text domains should only be loaded on init or later.

    You can refer to this line in the WordPress core: WordPress GitHub – l10n.php

    At this stage, I don’t think it’s necessary to provide a screenshot, as the issue is likely related to the loading sequence of the text domain. If you’re still unable to reproduce the issue following this suggestion, I’ll be happy to share a screenshot as needed.

    Thank you!

    Thread Starter Mohammed Jamsheed KM

    (@jamsheedkm)

    Hi Zubair Zahid,

    After further testing, I’m unfortunately encountering the error again, but this time it seems to be happening specifically when I visit a translated WooCommerce page.

    I’m still using WooCommerce 9.4.0-beta.2 and WordPress 6.7-beta2-59195, but the issue seems tied to the translation aspect of WooCommerce. Could you please advise if there have been any related updates or if you need additional details to help diagnose the issue?

    Thank you for your continued support!

    Thread Starter Mohammed Jamsheed KM

    (@jamsheedkm)

    Hi?Zubair Zahid,

    I’m currently not experiencing the error anymore. I’m using WooCommerce 9.4.0-beta.2 and WordPress 6.7-beta2-59195, and everything seems to be working fine now. It appears that the issue has been resolved with these updates.

    Thank you for checking in!

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