• Hi!

    We are getting this error in the backend (not frontend) if this plugin is active:

    Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-gateway-stripe 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.

    Although this error message is already added in WordPress 6.7.

    Additionally there is huge performance problem. I have dozens of broken requests to https://api.stripe.com/v1/account (401 Unauthorized) because of invalid test API keys.

    Seems like the test API keys we’ve saved for you are no longer valid. If you recently updated them, use the Configure Connection button below to reconnect.

    The problem is, that there is no notice that informs me about this problem. I installed Query Monitor, saw all the broken request and needed to go to WooCommerce -> Settings -> Payments -> Stripe -> Settings – 5 clicks deep inside Woo to see the actual problem and how to fix it. Not very user-friendly.

    I know that reconnecting to Stripe will easily fix it, but this should be much easier to spot and/or should not produce these huge performance issues (we are talking about adding 6 seconds loading time to each page request in the backend!).

    Hopefully this can be fixed in a future release.

    Thanks in advance!

    All the best
    Torsten

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hi @zodiac1978,

    Thank you for bringing this to our attention and for the detailed explanation—it’s truly appreciated.

    Regarding the textdomain error, this is something we’ve been monitoring closely. It’s a known behavior that started after changes were introduced in the way translations is loaded since WordPress 6.7, just as you noted. While it’s understandably frustrating to see, the current workaround is to suppress the warning from appearing in the dashboard, as it doesn’t impact functionality.

    As for the second issue, what you’re seeing is more of a system notice from Stripe rather than a bug within the WooCommerce plugin. Reconnecting usually resolves it, and since Stripe manages your API credentials, they are best positioned to alert you when there’s a problem—hence why you’re seeing the notice in your Stripe account dashboard. All WooCommerce settings remain organized under WooCommerce > Settings > [Relevant Tab], including payment settings, to help you manage everything easily.

    Please let me know if there’s anything else you’d like help with—we’re here for you.

    Thread Starter Torsten Landsiedel

    (@zodiac1978)

    Hi @mosesmedh

    the current workaround is to suppress the warning from appearing in the dashboard

    Why not fix the underlying issue? I know how to suppress this warning, but without a snippet or link to a snippet you are not helping anyone here.

    what you’re seeing is more of a system notice from Stripe rather than a bug within the WooCommerce plugin

    I know that reconnecting will solve it. This is not my case here. This is about the huge performance decrease due to dozens of requests from within this plugin, adding 6 seconds to every page request in the admin area and the missing information about where to fix it. This should be a non-dismissible red error notice with a link to the area where we can fix this.

    hence why you’re seeing the notice in your Stripe account dashboard

    I am not talking about the Stripe account dashboard at all.

    All WooCommerce settings remain organized under WooCommerce > Settings > [Relevant Tab], including payment settings, to help you manage everything easily.

    I have no idea why you are telling me this unrelated information. I know where to find and to fix it, as I explained it above. But this is not obvious and I only found it, because I installed additional plugins. This should not produce this delay at all and if this is not preventable you should give the user all information to fix it immediately if the impact is so immense.

    Please let me know if there’s anything else you’d like help with—we’re here for you.

    This is such a bad end for a support reply. I need you to understand my issue and help to go forward with a solution. Telling me this is easily fixed and worked around without any comments about the actual problems and if they will get reported to the dev team is not helping at all.

    “we’re here for you” – no, at the moment it feels like my issues are completely dismissed and ignored.

    All the best
    Torsten

    Hi @zodiac1978,

    I completely understand your frustration, but it looks like there may have been some confusion between your actual needs and the request you initially made.

    My responses have been based on the specific questions you asked, which are listed below:

    We are getting this error in the backend (not frontend) if this plugin is active “Function _load_textdomain_just_in_time was called incorrectly”

    As mentioned earlier, this is a known situation that’s currently being monitored for improvements. It’s not considered a bug but rather a notice, and it doesn’t impact your site’s performance or functionality. The recommended approach for now is simply to hide the notice while the development team continues to assess it. Since it’s not a critical issue, an individual fix can’t be provided. For more details, please refer to this post: https://developer.woocommerce.com/2024/11/11/developer-advisory-translation-loading-changes-in-wordpress-6-7/

    Additionally there is huge performance problem. I have dozens of broken requests to https://api.stripe.com/v1/account (401 Unauthorized) because of invalid test API keys.

    Could you please clarify that part for me? Are you receiving a notice about invalid test API keys directly from your Stripe dashboard, or are you seeing the error elsewhere? I assumed you were referring to the Stripe dashboard based on the URL you provided.

    The problem is, that there is no notice that informs me about this problem. I installed Query Monitor, saw all the broken request and needed to go to WooCommerce -> Settings -> Payments -> Stripe -> Settings – 5 clicks deep inside Woo to see the actual problem and how to fix it. Not very user-friendly.

    You mentioned that reconnecting Stripe resolved the issue for you, which is great. Typically, with issues like this, Stripe will display a notice, and WooCommerce will also log it under WooCommerce > Status > Logs. Depending on how your site is set up and how you’ve configured error handling, the notice may either appear there or be stored in a separate log folder managed by another plugin you’re using.

    Could you please let me know if there’s anything I may have missed or any specific request I haven’t addressed yet? I want to make sure everything you need help with has been properly covered.

    @zodiac1978,

    To better understand your setup, please include your system status report by going to WooCommerce > Status > Get system report > Copy for support. Also, if there are any log entries related to Stripe or fatal errors, you can find them under WooCommerce > Status > Logs and share them as well using pastebin.com

    Thread Starter Torsten Landsiedel

    (@zodiac1978)

    Are you receiving a notice about invalid test API keys directly from your Stripe dashboard, or are you seeing the error elsewhere? I assumed you were referring to the Stripe dashboard based on the URL you provided.

    The error is showing at the place I mentioned in my first post:
    WooCommerce -> Settings -> Payments -> Stripe -> Settings

    View post on imgur.com

    I assumed you were referring to the Stripe dashboard based on the URL you provided.

    No, these URLs are from the broken requests I saw in Query Monitor, which I also mentioned in my first post. Which BTW sum up to 5-10 seconds as you can see in this screenshot:

    View post on imgur.com

    Which results in this massive delay showing up in Plugin Profiler for this plugin:

    View post on imgur.com

    Plugin Support Kay U a11n

    (@kingsleyinfo)

    Hi @zodiac1978

    The error is showing at the place I mentioned in my first post:
    WooCommerce -> Settings -> Payments -> Stripe -> Settings

    Thank you so much for taking the time to share such a detailed account of your experience with the Stripe plugin.

    We truly understand how important it is for critical notices to be clearly visible, especially when performance could be affected.

    Your feedback helps us see things from your perspective, and we truly value your input. We’re constantly striving to improve our products, and hearing directly from users like you is one of the most effective ways we can do that.

    If you’re comfortable, we’d be incredibly grateful if you could share your experience as a new issue on the Stripe GitHub repo.

    By posting your feedback there, you’ll ensure it reaches our development team directly, so they can prioritize it appropriately. Your voice can make a real difference-not just for you, but for the entire community.

    Textdomain error

    With respect to this error, please note that our developers are already working on this here
    Please expect this to be released with a later version of the plugin.

    You’re welcome to contact us again if you have any more questions. 🙂

    Plugin Support Feten L. a11n

    (@fetenlakhal)

    Hi there,

    It’s been a little while since we last heard from you, so I’ll mark this as resolved. Reach out anytime if you’d like to revisit this!

    Apart from this, if you’re happy with our plugin and the support you’ve received, we’d really appreciate a review: https://ww.wp.xz.cn/support/plugin/woocommerce-gateway-stripe/reviews/#new-post

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

The topic ‘Textdomain error and performance problem with invalid keys’ is closed to new replies.