Title: flowsheff's Replies | WordPress.org

---

# flowsheff

  [  ](https://wordpress.org/support/users/flowsheff/)

 *   [Profile](https://wordpress.org/support/users/flowsheff/)
 *   [Topics Started](https://wordpress.org/support/users/flowsheff/topics/)
 *   [Replies Created](https://wordpress.org/support/users/flowsheff/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/flowsheff/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/flowsheff/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/flowsheff/engagements/)
 *   [Favorites](https://wordpress.org/support/users/flowsheff/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce Stripe Payment Gateway] Very slow backend – 50 calls to the Stripe API](https://wordpress.org/support/topic/very-slow-backend-50-calls-to-the-stripe-api/)
 *  [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [1 year, 2 months ago](https://wordpress.org/support/topic/very-slow-backend-50-calls-to-the-stripe-api/#post-18470574)
 * [@zubair](https://wordpress.org/support/users/zubair/) is there an ETA on when
   this will be fixed? I can also confirm that ever since the latest update with
   this plugin, that its causing massive slowness in the admin area for virtually
   any admin function. It doesn’t affect the front end, just the back end. Looking
   at query monitor, it’s actually pretty bad…
 * ![](https://wordpress.org/fd999f93-87e2-4668-9142-4618a3efea07)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] 8.5.1 is a nightmare](https://wordpress.org/support/topic/8-5-1-is-a-nightmare/)
 *  [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/8-5-1-is-a-nightmare/#post-17352753)
 * [@lernerconsult](https://wordpress.org/support/users/lernerconsult/)
 * [@ajamm](https://wordpress.org/support/users/ajamm/) wouldn’t even be scratching
   the surface of what is wrong with the latest release, even if he did offer more
   information about his particular setup.
 * Countless websites have lost major revenue as a result of this release. Woo also
   fails to respond to support tickets in a timely manner in spite of the bloated,
   bug-laden release. As a paid woo customer myself, I think it’s fair to say that
   people are simply fed up with the lack of quality control. There’s absolutely
   nothing wrong with providing legit feedback to woo, when woo is in the wrong 
   here.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Major Critical Errors with Woo 8.5.1. Why the lack of response?](https://wordpress.org/support/topic/major-critical-errors-with-woo-8-5-1-why-the-lack-of-response/)
 *  Thread Starter [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/major-critical-errors-with-woo-8-5-1-why-the-lack-of-response/#post-17352721)
 *  (@ckadenge) The main point that woo continues to deflect, and the question on
   everyone’s mind is: why was 8.5.1 even released to begin with?
 * Look at all of the responses in the last 72 hours. It’s an absolute disaster 
   filled with endless bugs and bloat. What happened to quality control?
 * Does woo have plans to get rid of all of the code bloat anytime soon?
 * @
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Critical Error – Call to undefined fn wc_notice_count() – After plugin update](https://wordpress.org/support/topic/critical-error-call-to-undefined-fn-wc_notice_count-after-plugin-update/)
 *  [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/critical-error-call-to-undefined-fn-wc_notice_count-after-plugin-update/#post-17350155)
 * [@sandipmondal](https://wordpress.org/support/users/sandipmondal/) you’re making
   too much sense and asking too much 😉
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Insane BLOAT on latest update!](https://wordpress.org/support/topic/insane-bloat-on-latest-update/)
 *  [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/insane-bloat-on-latest-update/#post-17349452)
 * I also despise gutenberg ( I use the classic editor) and it just keeps getting
   worse and worse with this latest update. I noticed on the checkout page there
   are new “block” elements being forced whereas before they didn’t even exist.
 * Do you have any specific info on where you’re seeing the bloat and/or specific
   elements that were added? Are you seeing most of the bloat on the products page
   or also elsewhere?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Woo fails to communicate, so here’s my contribution..](https://wordpress.org/support/topic/woo-fails-to-communicate-so-heres-my-contribution/)
 *  Thread Starter [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/woo-fails-to-communicate-so-heres-my-contribution/#post-17348665)
 * [@hastibe](https://wordpress.org/support/users/hastibe/) I was able to produce
   the stripe issue and first report the error here: [https://wordpress.org/support/topic/major-fatal-error-and-conflict-w-8-5-1-and-stripe-gateway/](https://wordpress.org/support/topic/major-fatal-error-and-conflict-w-8-5-1-and-stripe-gateway/)
 * It was on a completely, empty site with nothing but woo and stripe activated 
   and the error was triggered anytime you attempted to edit users in the dashboard.
   You’d likely experience the same issue if you attempted to edit a user in the
   dashboard, though the fatal error may have also been triggered by other unknown
   actions as well.
 * Yes, 7.9.1 seemingly fixes this fatal error issue. but they didn’t even bother
   making an announcement about it. As we sit here now, countless people likely 
   don’t even realize a fix has ben released or that it;’s even related to woo’s
   own stripe plugin because obviously not everyone updates plugins as soon their
   released. Woo needs to take some accountability here and actually communicate
   with their users. Despite having a ticket open, I still have not heard back, 
   and yet this one error alone, clearly affects a huge number of users.
    -  This reply was modified 2 years, 6 months ago by [flowsheff](https://wordpress.org/support/users/flowsheff/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Woo fails to communicate, so here’s my contribution..](https://wordpress.org/support/topic/woo-fails-to-communicate-so-heres-my-contribution/)
 *  Thread Starter [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/woo-fails-to-communicate-so-heres-my-contribution/#post-17348515)
 * [@cliqueradar](https://wordpress.org/support/users/cliqueradar/),
 * As far as I know, there shouldn’t have been any database updates between 8.4 
   and 8.5, but it would be wise to double check that.
 * But yes, I am astounded at woo’s lack of support and communication. Nearly 900K
   active installs for the stripe gateway alone. It’s like they don’t want to publicly
   admit that the code they released, and their code alone, is the source of the
   issue. Not too shocking I guess.
    -  This reply was modified 2 years, 6 months ago by [flowsheff](https://wordpress.org/support/users/flowsheff/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Major Critical Errors with Woo 8.5.1. Why the lack of response?](https://wordpress.org/support/topic/major-critical-errors-with-woo-8-5-1-why-the-lack-of-response/)
 *  Thread Starter [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/major-critical-errors-with-woo-8-5-1-why-the-lack-of-response/#post-17348465)
 * Half of the fatal errors people are seeing have nothing to do with these security
   settings. They have to do with Woo’s own Stripe plugin. Updating that will fix
   half of these issues. Although I’m not doubting the other half of the issues 
   people are experiencing. 8.5+ is a mess.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Major, Fatal Error and Conflict w/ 8.5.1 and Stripe Gateway…](https://wordpress.org/support/topic/major-fatal-error-and-conflict-w-8-5-1-and-stripe-gateway/)
 *  Thread Starter [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/major-fatal-error-and-conflict-w-8-5-1-and-stripe-gateway/#post-17348448)
 * What is frustrating is that often when there is a support response (See [@carolm29](https://wordpress.org/support/users/carolm29/)’
   s response above) is that support doesn’t even address the issue at hand. My 
   first and opening post on this specific thread had NOTHING to do with 403 errors–
   it had to do with critical fatal errors being produced by Woo’s own Stripe plugin.
   It seems that Woo quietly updated this literally only 2 hours ago, and told no
   one about it and didn’t even bother making a blog post about it, even though 
   half of the critical errors that were being produced were indeed being caused
   by that issue.
 * So incredibly frustrating. Personally, I wouldn’t update to 8.5+ until they get
   all of the other bugs worked out. According to many others, they threw in a bunch
   of bloated stuff in this latest version. Eager to advance woo without paying 
   attention to quality control. Quality control seems to be the issue with most
   things today in society.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce PayPal Payments] Upgrading from PayPal Standard…Looking for Simple Answers](https://wordpress.org/support/topic/upgrading-from-paypal-standard-looking-for-simple-answers/)
 *  Thread Starter [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/upgrading-from-paypal-standard-looking-for-simple-answers/#post-17204578)
 * It sounds like the simpler answer would be: NO, PayPal Payments doesn’t process
   existing subscriptions. If you wish for older WooCommerce payments to continue
   processing using PayPal Standard, then you’ll need to leave PayPal Standard activated
   but remove it from the checkout process after you begin using PayPal Payments
 * Did I get that right?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce] Urgent! Recurring Subscription Payment Failures in Action Scheduler](https://wordpress.org/support/topic/urgent-timeouts-payment-failures-in-action-scheduler/)
 *  Thread Starter [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/urgent-timeouts-payment-failures-in-action-scheduler/#post-17192340)
 * Hi Roxy
 * My ticket is: 7281791.
 * There has finally been a response, and I have responded with additional info 
   as this urgent issue still exists.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce Stripe Payment Gateway] Urgent! Fully Updated and Still getting payment timeouts…Please advise…](https://wordpress.org/support/topic/urgent-fully-updated-and-still-getting-payment-timeouts-please-advise/)
 *  Thread Starter [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/urgent-fully-updated-and-still-getting-payment-timeouts-please-advise/#post-17190314)
 * We do indeed have a valid license. However, we’ve already opened a ticket nearly
   days ago from within our woo account when this first happened (now 36 hours ago)
   and still not a single response….So, do we open a new one?
    -  This reply was modified 2 years, 9 months ago by [flowsheff](https://wordpress.org/support/users/flowsheff/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WooCommerce Stripe Payment Gateway] WordPress 6.4 version and issues with this plugin](https://wordpress.org/support/topic/wordpress-6-4-version-and-issues-with-this-plugin/)
 *  [flowsheff](https://wordpress.org/support/users/flowsheff/)
 * (@flowsheff)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/wordpress-6-4-version-and-issues-with-this-plugin/#post-17189848)
 * This is still a BIG issue, as we have updated to the latest wordpress, stripe
   and woocommerce plugins. ALL of our recurring subscription payments are simply
   failing (both Stripe and Paypal standard) and in the logs they are as following:
   scheduled action 874898 (subscription payment) failed to finish processing after
   3600 seconds.
 * This is is literally a crisis and should be treated as the highest priority..
 * Please advise asap!
    -  This reply was modified 2 years, 9 months ago by [flowsheff](https://wordpress.org/support/users/flowsheff/).
    -  This reply was modified 2 years, 9 months ago by [flowsheff](https://wordpress.org/support/users/flowsheff/).

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