Issue after update wordpress

  • silvia1611

    (@silvia1611)


    2 weeks ago

    I’ve this problem since I updated to wordpress 6.7:

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-services 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 /app/wp-includes/functions.php on line 6114

    I’ve seen in the forum that you recommend hiding these warnings, but this solution doesn’t fix the problem; it just hides it. Are you planning to release a new version that actually fixes this?

    Thanks.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Jonayed (woo-hc)

    (@jonayedhosen)

    2 weeks ago

    Hi @silvia1611 ,

    Thanks for reaching out

    The Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-services domain was triggered too early – it’s a common warning notice and it’s more of a heads-up from WordPress about how it now loads translations.

    It’s not harmful for your site, but it is something the WordPress team is still keeping tabs on. You can check more about it here: https://developer.woocommerce.com/2024/11/11/developer-advisory-translation-loading-changes-in-wordpress-6-7/

    As a workaround, If you’d rather not see that message showing up, you can disable it by adding WP_DEBUG_DISPLAY set to false in your wp-config.php. That way, the notice stays behind the scenes while everything continues to work just fine. In that case, you may add the following line lines to the end of your wp-config.php file:

    define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

    I hope this helps!

    Mehraz Morshed

    (@mehrazmorshed)

    1 week, 4 days ago

    Same here!

    Plugin Support Moses M. (woo-hc)

    (@mosesmedh)

    1 week, 3 days ago

    Hi @mehrazmorshed,

    I understand you’re facing a similar issue, but it would be best if you could start a new topic. That way, we can focus on your specific case and get a clearer understanding of the problem.

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