Text Domain Loading Error

  • Resolved thunderfrog

    (@thunderfrog)


    1 week, 6 days ago

    Hello, we are getting the following error on our site, which is credited to this plugin – any chance for a fix and update?:

    Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-sendinblue-newsletter-subscription 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.

    1. _load_textdomain_just_in_time()
      wp-includes/l10n.php:1445
    2. get_translations_for_domain()
      wp-includes/l10n.php:1483
    3. translate()
      wp-includes/l10n.php:195
    4. __()
      wp-includes/l10n.php:307
    5. SendinblueWoocommerce\Managers\CartEventsManagers->checkout_label()
      wp-content/plugins/woocommerce-sendinblue-newsletter-subscription/src/managers/cart-events-manager.php:508
    6. SendinblueWoocommerce\Managers\CartEventsManagers->add_optin_wc_checkout_block()
      wp-content/plugins/woocommerce-sendinblue-newsletter-subscription/src/managers/cart-events-manager.php:576
    7. sendinblue_woocommerce_load()
      wp-content/plugins/woocommerce-sendinblue-newsletter-subscription/woocommerce-sendinblue.php:139
    8. do_action('plugins_loaded')
      wp-settings.php:622
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support shreyachawla

    (@shreyachawla)

    1 week, 4 days ago

    Hi,
    Thank you for reaching out and for sharing the detailed error log. We sincerely apologize for any inconvenience this may have caused.

    The error you are encountering:

    “Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-sendinblue-newsletter-subscription domain was triggered too early.”

    is related to a known compatibility issue introduced in WordPress 6.7, which enforced stricter rules around when translation files can be loaded. In this case, our plugin’s CartEventsManager was calling a translatable string (__()) during the plugins_loaded hook, which now runs before WordPress’s translation system is fully initialized.

    Here is what we recommend in the meantime:

    1. Update the plugin to the latest available version from the WordPress plugin repository, as this issue may already be addressed in a recent release.
    2. If the error persists after updating, you can safely suppress the notice as it is non-critical and should not affect your site’s functionality. It is a PHP notice, not a fatal error.
    3. If you are experiencing any functional issues beyond this notice (e.g., broken opt-in checkbox at checkout), please let us know and we will escalate accordingly.

    We appreciate your patience and for helping us improve the plugin experience. Please do not hesitate to reach out if you have any further questions.

    Best regards,

    Thread Starter thunderfrog

    (@thunderfrog)

    1 week, 4 days ago

    Hello, the plugin is currently at the latest version, 4.0.54. And that error/notice is still occurring. It does in fact interfere when running other plugin updates.

    Plugin Support shreyachawla

    (@shreyachawla)

    1 week, 3 days ago

    Hi,

    Thank you for confirming and for your continued patience with this.

    We understand that you are on the latest version (4.0.54) and the notice is still appearing. We also take note that it is causing interference when running other plugin updates, which means this goes beyond a cosmetic notice and warrants a proper fix.

    Here are a few options that may help reduce the impact:

    1. Temporarily disable the opt-in checkbox feature in the plugin settings if it is not critical to your current workflow, as this may prevent the early loading from being triggered.
    2. Run plugin updates individually rather than in bulk, as a workaround while the fix is being implemented.


      We sincerely apologize for the inconvenience and appreciate your patience.
      Best regards,
Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.