I updated my WordPress plugin

  • Resolved theboydemola

    (@theboydemola)


    1 week ago

    i updated my wordpress on my website and it started showing this on the site – Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?woocommerce-paypal-payments?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/exhxcgyp/public_html/wp-includes/functions.php?on line?6114

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

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

    (@ckadenge)

    Hi there,

    This is a known issue that was earlier reported, but a fix has already been deployed here, and it will be available in our next release.

    Thank you for your patience and understanding.

    I grabbed the dev version so I could at least have payments until the official release, but the plugin is still broken. It’s showing a blank page in the Woocommerce payment settings and nothing is coming up on the front end. This is the busy time of year so any help would be greatly appreciated!

    thanks

    Chris

    Plugin Support Jonayed Hosen (woo-hc)

    (@jonayedhosen)

    Hi @coffeemugger ,

    Thank you for reaching out about this issue. To align with the best practices of the support forum, I recommend creating a new thread for your concern. Each site has a unique setup, and a dedicated thread will help us investigate your issue more accurately. You can start a new topic here: WooCommerce Stripe Support Forum.

    Additionally, I suggest waiting for the official release of the next version to see if the issue persists. It’s possible that something is missing or not functioning correctly in the development version you’re using. Since this isn’t an official release fix yet, it would be best to wait for the next update and recheck the issue afterward.

    I hope this helps!

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