shaunek
Forum Replies Created
-
Wow, what a quick response, thank you very much. I got the most recent version and attempted to activate, and I still got a very similar error in the WordPress Admin UI. See screenshots here: https://imgur.com/a/wGyfoRk
But I did get a different error message in my php error log…
[27-Aug-2025 22:16:02 UTC] [WeeConnectPay] [CRITICAL] CRITICAL WARNING: WeeConnectPay is running in 'development' environment instead of 'production'. Non-production use of this plugin will NOT WORK because Clover does not expose our app in non-production environments. Authentication will fail. REQUIRED ACTION: (1) Uninstall the WeeConnectPay plugin completely, (2) Set your WordPress environment to 'production', (3) Reinstall the plugin. This happens because your WP_ENVIRONMENT constant is set to non-production. Non-production authentication is only available to internal WeeConnectPay developers. If you don't understand why WeeConnectPay is not resolving to production environment, please contact [email protected] for assistance.Thankfully that had a good error message that helped me understand that I needed to change the WP_ENVIRONMENT_TYPE constant that was defined in my wp-config.php file from ‘local’ to ‘production’ to get this to work.
So in the end I was able to install the plugin on my localhost. I had more to do but thanks for helping me figure out the issue. I will say that the message that was provided in the error log would have been nice if it could have been displayed on the screen. Not all WordPress users know how to rummage through the appropriate log files.
All the best, cheers!
Forum: Plugins
In reply to: [Clover Payments for WooCommerce] Payment Form Not Working On Firefox BrowserThis is still an issue. I have been working with another vendor’s plugin which uses the same Clover tokenization/iframe APIs. Just thought I would comment a few things I have found out about this since I started my investigation about a month ago:
- The issue is restricted to a subset of Firefox users. Here are the things I am sure about:
- Firefox on macOS with the M-series chips are impacted
- Firefox on macOS with older Intel-series chips are NOT impacted
- Firefox on Windows is NOT impacted
- Firefox on Linux is mixed. One guy could not replicate the problem on his Linux setup (I didn’t get his Linux config details unfortunately), but I installed Ubuntu on two new vms and replicated the problem easily. One vm was the arm64 version of Ubuntu running on my M1 mac, and the other was a x86_64 version of Ubuntu running in a vm on Google Cloud.
- Other browsers besides Firefox are not experiencing the issue (Edge, Chrome, Safari, etc).
- As the OP said, when you open Web Console (ie dev tools) and you have the Network tab’s “disable cache” checked this fixes the problem and it isn’t possible to replicate the issue. That being said when “disable cache” is unchecked have been able to replicate the issue occasionally – it is flakey and intermittent though.
- If you turn on “Troubleshoot mode” (menu -> Help -> Troubleshoot mode -> click Restart -> when it is restarting click Open in the popup) the issue goes away and it is not possible to replicate the problem. It works 100% consistently, like in other browsers. If you turn off Troubleshoot mode it will again revert to not working properly
- Deep Technical Mumbo Jumbo: I did a somewhat deep investigation to understand what was happening and found out that the way it is supposed to work is that for each field (cc#, exp#, exp date, etc) it is supposed to create a separate iframe – and that iframe loads an HTML document at a URL similar to this: https://checkout.clover.com/widget.html?baseOrigin=https%3A%2F%2Fcheckout.clover.com&element=CARD_NUMBER&origin=https%3A%2F%2Fwww.yoursite.com&apiKey=XXXXXXXXXXXXXXXX&styles=%7B%22body%22%3A%7B%22fontSize%22%3A%221em%22%7D%2C%22input%22%3A%7B%22fontSize%22%3A%221em%22%7D%7D&domainHost=https%3A%2F%2Fwww.yoursite.com&locale=en … but for some reason this iframe’s html doc doesn’t load properly into Firefox. I have inspected the network traffic with mitmproxy and I can confirm that the widget.html document is a legit document, nothing funny about it, but Firefox doesn’t render it properly… and then the JS and CSS files that widget.html are supposed to include to make all this functionality work just don’t get requested by Firefox at all.
- It is relatively clear to me that this “Clover Payments for WooCommerce” plugin is not “at fault” since I am experiencing this exact same problem in another plugin by another developer (Clover Gateway for WooCommerce which is in the WooCommerce Marketplace). Instead the problem is either with Firefox itself (as in some sort of browser bug) OR it is a problem with the backend Clover e-Commerce APIs (https://docs.clover.com/dev/docs/clover-ecommerce-homepage).
I would recommend that anybody with complaints for this issue please reach out to Clover at [email protected] to make it known to the team that maintains this plugin (they apparently don’t monitor this forum), and also email [email protected] to make your issue known. The support guy from my other plugin said he had previously been in contact with clover about 9-10 months ago about this issue but nothing was figured out and it got forgotten, and this past month I was able to get ahold of someone at Clover named Jacob via [email protected], but so far they are very slow to make any efforts to confirm the issue even though I have provided lots of detail to them… so the more people complain about this the better chance that it will get looked at.
Forum: Plugins
In reply to: [Clover Payments for WooCommerce] Clover now conflicting with WoocommerceHoping you get your issue resolved. I’m not with Clover and not related to this plugin at all, but I installed this plugin today (for a random reason I don’t need to explain the details) and I ran across your multiple unanswered posts here on the support forum and wanted to mention that they seem to prefer to be contacted by email at [email protected] instead of here.
Also, I just thought I would say that I don’t know much about this plugin but my company uses a competing plugin which is listed in the Woocommerce Marketplace store called Clover Gateway for WooCommerce. It is written by a third party developer, Kestrel, and I have reviewed the internals of this plugin and used it for a couple years now, it is a high quality plugin and I’ve been in touch with their support and they provide very good technical support.
Best of luck
The answers in this thread are quite helpful. Thanks to rodulfl for asking and for the excellent answers. Preeesh!
Forum: Plugins
In reply to: [Index WP MySQL For Speed] Can it deactivate?This question and answer was helpful, thanks.
Forum: Plugins
In reply to: [WP Hardening (discontinued)] PHP Warnings when using WP-CLII’m curious if you figured out the best way to patch this plugin to avoid this problem?
@valwa Thanks for the reply, but I guess I wasn’t clear in my original post. Some plugins do a really good job of cleaning up after themselves by deleting all their config data, cached files, etc, but most just leave all their data behind. What I was actually wanting to know is if there is a way to fully clean up all the data that this plugin has generated, including but not limited to entries in the options table (or other tables), image files, etc. Maybe deleting the plugin the the normal way or via wp-cli will do all the data clean up itself, but I didn’t see any documentation about that. And I also grep’ed for the function “register_uninstall_hook” and I didn’t see it referenced, so I’m guessing this plugin doesn’t actually do anything when it is uninstalled. My apologies for not explicitly asking those details before.
Hi there, thanks for the response. For the record I also could not replicate the problem on a different environment! I had 3 environments I tried it on besides production environment, all very similar. I even used Cloudways’ built in staging functionality which creates a copy of your prod site and copies it exactly to a staging site (db + code + assets) and the staging site worked just fine. Ugh, was very frustrating. The thing that fixed our issue was disabling this plugin.
We went ahead and permanently uninstalled this plugin and installed a competing plugin, https://ww.wp.xz.cn/plugins/woocommerce-pdf-invoices-packing-slips/, which has the similar functionality, and we are happy with it.
Thanks again for looking into it
Thanks @bitpay, I ended up creating a github issue and I think I’ll create a PR in the next week or so. Thanks for the help and encouragement.
Sweet! I see you already merged the PR, how great. I’ll look forward to the plugin update.
@bitpay What is the best way to suggest a minor improvement/change to the plugin? We did have to make one other change to the plugin code because of a business need, it is a pretty small change, but it might be considered a feature change. Should I share our code customization + rational via Github PR or should I open a Github Issue to open a discussion or some other option? I could do a PR but I don’t want to be presumptuous if you aren’t interested in feature requests. It is a pretty minor thing – basically we really don’t want the Woo order status to go directly to “processing” right when the invoice goes to “paid”.
Thanks for your explanation
Okay thanks for the reply, we’ll try that out.
Forum: Plugins
In reply to: [WooCommerce] wc_customer_bought_product() slows down page massivelyThanks @cutu234 for posting the link to the open github issue, I first found this report which lead me there which was helpful.
Forum: Plugins
In reply to: [WP Hardening (discontinued)] PHP Warnings after upgrading to PHP 8.2I believe I have partially figured out what is going on, the /modules/hooks.php file has this code at the top:
require_once(ABSPATH."/wp-includes/pluggable.php");
require_once(ABSPATH."/wp-load.php");When I comment those lines out the warnings I’m complaining about go away.
Does anybody know why the plugin needs to require these two files here? It seems like it works without these lines.
Forum: Plugins
In reply to: [Invisible reCaptcha for WordPress] PHP Notices on PHP 8.2The more I poke around the more it is obvious the original developer isn’t actively involved.
I found that @digitalchild posted a patch in a gist here https://ww.wp.xz.cn/support/topic/php8-support-16/, in case anybody is planning to stick with this plugin.
- The issue is restricted to a subset of Firefox users. Here are the things I am sure about: