Jason

This issue most certainly impacted orders as our WAF blocked IPs for causing excessive 400 errors simply for browsing the site.

Many hosts would have the same.

Can you highlight what specific changes have been made to your release process to pick up errors such as this?

Cheers,

Jason

Hi Ben,

Can you please let us know what steps have been put in place to prevent poor quality software from costing your merchants sales in the future?

Thanks,

Jason

This is affecting us too!

How can we escalate this with the core security team?

I am seeing the same problem here. Would love a fix, Facebook!

BTW: https://www.facebook.net is not a valid domain.

• This reply was modified 1 year, 7 months ago by Jason.

Thanks for letting me know. I guess WC Core should be the ones fixing this.

These responses are very weak.

I have raised a feature request at https://woocommerce.com/feature-request/fraud-prevention-against-thousands-of-posts-to-wc-ajaxcheckout/#

I already have fraud prevention turned on.

I don’t understand why you think it’s okay to use a third party plugin to solve problems with your own. Your customers are asking you to solve this issue in your plugin. Can you please listen to our request and add this to your development backlog as a high priority?

Jason

1. 6.0.3, 7.4, 4.4.3.2
2. It has been happening for a while.
3. It is breaking listing processes as they are killed due to OOM.
4. They occur randomly but are quite annoying.
5. Not specifically, but as mentioned updating eBay listings with WP Lister seems to cause WSAL to use exorbitant amounts of memory. This plugin deals with large XML payloads due to the eBay integration.
   
   Cheers, Jason

Sorry your logic makes no sense.

I had 25,000 payment attempts against a single order from a single IP. This has nothing to do with high volume sites.

Your customers and Braintree themselves would appreciate a proper solution to this very real issue.

Jason

Why does this plugin allow infinite payment attempts with no rate limiting at all?

3DS is not a solution, and this plugin shouldn’t require another plugin to avoid security and performance issues.

Cheers,

Jason

Hey @robert681

1) Can you confirm if any of the events with IDs 5010 up to 5024 are enabled or disabled?

All disabled.

2) The error message you posted is incomplete. There should be more info with the logs. Can you share them all? If they include sensitive data please send them over email at [email protected] and make reference to this thread.

That is the full error. The rest is information from the web server such as IP address, date and time which you do not need.

3) Do you know if it is something specific that is triggering this error?

As per the log entry it is occuring on a post edit, specifically editing a WooCommerce Product.

4) What version of WordPress and PHP are you running please?

5.9.3 (WC 6.5.1) and PHP 7.4.

Cheers,
Jason

Hey Maarten,

I want to clarify something (again). Nowhere did I say you “should do all the work for free”. In fact, I said “I fully understand the need to earn”. But you must be reasonable.

I referenced a 3 year old ticket raised by someone else in my first post, showing at least one other customer has run into this issue. More probably are, but don’t have the technical knowledge to know. Your reason that you “have no time” or “your site has some configuration making our plugin slower” does not really explain why you couldn’t point me to that line of the plugin so I can customise it.

I updated my review to reflect the quality of the conversation we had in this thread. If you don’t like the review, maybe have a think about how your response made your customer feel.

It’s disappointing that you feel the best course of action in response to a single negative review is to no longer offer the software, but that’s your call. I’d happily contribute a pull request with a more reasonable default, or reconsider my review if you accept my feedback.

Cheers,
Jason

Hey Maarten,

I want to be clear here, I am not lacking respect. You released a plugin that queries the two biggest tables in any WooCommerce install (posts & postmeta) once a minute. When I took the time to suggest one way to fix this issue, you tried to upsell to the paid version. I don’t think that is appropriate.

I fully understand the need to earn, however holding people random is not a great way to do it. To keep a good reputation for this software you have released it needs to stay maintained, secure & performant. My feedback has a value and takes time to provide too.

My last support interaction with you was great – I took the time to point out an issue, and you came back with a fix when it was convenient for you. I am not asking for free development work, but at least think about how users could help themselves if you do not have the time to fix the issues in your free version.

Thanks,
Jason

Once upon a time open source software was about sharing knowledge, not trying to sell fremium.

For those playing along at home, go to line 68 in admin/class-mabel-rpnlite-admin.php and change the transient timeout to whatever you want. I went with set_transient( $cachekey, $products, 600);

Cheers,
Jason