pingram
Forum Replies Created
-
Thank you for the kind feedback @doublezed2, much appreciated.
I am reporting that the issue still persists, along with an example and a fix.
Others are surely to continue reporting this, most esp. if anyone attempts to translate those functions that are still being called too early which is the underlying reason we are still seeing the notice when debugging is enabled. The purpose for debugging is to solve problems, and this “notice” is giving us a heads up that there is something amiss. Disabling debugging does not correct the underlying translations problem.
I appreciate your continued dialog in this matter. Have a great one!
Thanks for the quick response Moses but again I must respectfully disagree regarding this being a known issue caused by changes to how WordPress handles translation loading.
The change in core 6.7 did not change how translations themselves were handled only that a notice is now written to the debug log to inform the plugin or theme development team that their plugin or theme is “doing it wrong” in the sense that translations are being attempted on string values before translating has become available.
This is an effort to “do it right” and I hope that is ok. Here’s a quick attempt to shed some light on what might still be the issue…
With a quick search for translation functions,__(), we first come across:
https://github.com/Automattic/woocommerce-payments/blob/f6dd0c6f5691ab31fc7c583b664c01904c108c0d/woocommerce-payments.php#L312Which is a class function
wcpay_get_jetpack_idc_custom_content()that has translation functions__()within it yet if we search for the hook that calls this class function we find it onL93within another class function onL85calledwcpay_jetpack_init()of which is called onL156using theplugins_loadedhook which is too early as explained here: https://make.ww.wp.xz.cn/core/2024/10/21/i18n-improvements-6-7/I did not do a thorough review of all
__()translation functions but I hope this helps identify how we are still seeing this notice in our log files.I also understand that this is not “front end” affecting provided debugging is not turned on for a high traffic site that could lead to disk quota issues but for developers this is a frustrating thing to have to sift through when debugging is necessary, esp. when many plugins are still not patched.
I appreciate your desire to work with the community and better your plugin, thanks for hearing my thoughts.
I disagree but I’d love to help resolve this. It appears to be the same issue reported for many plugins. Perhaps there are still some __() functions that are being loaded too early?
This is running the current
woocommerce-paymentsversion 9.3.0, loaded on a fresh instance with WP defaults:
[16-May-2025 21:08:14 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for thewoocommerce-paymentsdomain 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 theinitaction or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /…/wp-includes/functions.php on line 6121This is a support community and it is perfectly acceptable for people to contribute in finding a solution to the same problem. Please reconsider, the intent is to work together to resolve an issue that is not isolated but effects a broad spectrum of users, if not every active installation. Thanks for your consideration.
https://ww.wp.xz.cn/support/guidelines/
https://make.ww.wp.xz.cn/handbook/community-code-of-conduct/Thanks for the quick response. Does that mean that this wp repo version is no longer being maintained and will not be patched for this?
Hi @pavithrasivasamy thank you for the kind response and for patching this.
Here on the WordPress repo it says 2.6.9 is the latest version.
Is V3 the paid version?
We are seeing the repeated notice for
woo-discount-rulesnotwoo-discount-rules-pro, please advise when this patch can be available to this repo version of which we are experiencing this notice thank you.Hi Zubair,
Yes we have updated from 9.4.1 to 9.5.0 which became available to us on 5/13/25 but likely patched in your development work months ago, we just didn’t have an actual update offered to us from the repo until after opening this ticket.
Thank you for making this patch along w/ many others now published, I have confirmed since updating to 9.5.0 last night that the notice is no longer occurring for this plugin.
I am marking this as resolved, again, thank you very much for all of your efforts, cheers!
Hi Sven,
You rock. Thanks for the update and patching this. Please close this ticket as resolved. Thank you kindly.
Yes 3.3.1
I had only verified the error was dated today and that the plugin showed it was current before opening this ticket. Another admin had updated pods about an hour before I started opening tickets. I can confirm (among the many other plugins still not patched), that pods is no longer reporting this notice.Please close this ticket and thank you for the quick response making these corrections.
Forum: Plugins
In reply to: [oik bwtrace] Function name conflict, too genericI changed the function name and updated all references to ‘ep’ adding a prefix ‘bw_ep’ and all was good.
Yes it appears the problem has resurfaced a few times being removed then re-patched. Please verify you are running v2.5.3 as of today.
The fix applied in version 2.4.1 was reverted with the code refactor in 2.4.3-rc1 and when inspecting the code it appears it was rolled back and then later patched in 2.5.0-rc2 but then removed again the next release in 2.5.1. See – https://github.com/woocommerce/woocommerce-paypal-payments/issues/1947
patched – 2.5.0.rc-2 – /modules/ppcp-wc-subscriptions/src/WcSubscriptionsModule.php (see lines 88-90)
patch rolled back – 2.5.1 – /modules/ppcp-wc-subscriptions/src/WcSubscriptionsModule.php (see line 85)
patched 3rd time – 2.5.2.rc-1 – /modules/ppcp-wc-subscriptions/src/WcSubscriptionsModule.php (see lines 88-90)
Hope this helps.
Forum: Plugins
In reply to: [WPIDE - File Manager & Code Editor] ZIP extremely slow and odd behaviorOpened a ticket on wpide.com website. Will update here if I hear back.
Thanks Joost & team!
Greatly appreciate all your efforts on this.Hi Joost,
Disabling PayPal Advanced Card Processing did not resolve the issue.
I’ve gone ahead an opened a ticket w/ your service desk, including the system status log and 4 order notes screenshots as follows:
- New Subscription Order via WooPayments = PayPal error
- New Subscription Order via PayPal = no error
- Existing Subscription Order via Stripe = no error
- Non-Subscription Order via WooPayments = no error
Thanks again for you help with this!
Thank you Joost. One thing remains, the error is indeed of this plugin as a result of a method (ppcp_get_paypal_order) within a class being called which should not be called when PayPal is not the payment method being used.
Stripe has been disabled yet the error continues.
Not an educated guess but we saw PayPal Advanced Card Processing enabled, which is explained as for the ability to process credit cards using PayPal which seems unnecessary if WooPayments is handling credit card processing.
We have now disabled PayPal Advanced Card Processing and will monitor the issue, if it continues, we will follow your instructions and open a ticket w/ your service desk.p.s. A screenshot of the order notes was provided in my previous post, the first url is the larger full size image. Sorry, I fail to understand how people post actual images in these wp.org threads, it’s not very intuitive.
Oh my, I spoke too soon. As you can see, I flipped the circumstance in my previous response from my original, where it is the INITIAL subscription order and NOT renewals that fail with this error.
The error being:
Error during status transition. PayPal order ID not found in meta.This is not a PayPal order so there should be no seeking of a PayPal order ID in the product meta when other payment method is used, most esp. successfully. Hopefully this screen shot will help. Let me know if you need anything from me. Thanks Joost.
[url=https://postimg.cc/fV2gXf2T][img]https://i.postimg.cc/fV2gXf2T/Screen-Shot-2023-10-30-at-8-06-50-AM.png[/img][/url]