Title: Critical bug in v1.3 that intervenes in EACH request in admin panel
Last modified: October 26, 2025

---

# Critical bug in v1.3 that intervenes in EACH request in admin panel

 *  [daiohansed](https://wordpress.org/support/users/daiohansed/)
 * (@daiohansed)
 * [5 months, 2 weeks ago](https://wordpress.org/support/topic/critical-bug-in-v1-3-that-intervenes-in-each-request-in-admin-panel/)
 * We noticed that random plugins stopped saving changes to their settings — no 
   error, the page just normally reloads after submitting the form yet no changes
   are applied. Then we noticed that even certain basic actions, such as deleting
   or updating plugins, stopped working — the XHR request to admin-ajax.php returned
   400 Bad Request with “0” in response.
 * After deactivating plugins one by one, we’ve pinpointed the issue to your plugin.
   Then we’ve found out the exact piece of code that causes it: [https://share.cleanshot.com/6PxwyysfRm1nZxKtq2KL](https://share.cleanshot.com/6PxwyysfRm1nZxKtq2KL).
   In v1.3, you started calling plugin_options() on ‘init’ instead of ‘after_setup_theme’.
   And inside one of the CSF::_createSection_(), that method calls $this->getPaymentOptions()
   on line 114. This is the method that breaks everything.
 * We didn’t dig further, so the only possible explanation we have is from AI:
 * > $this->getPaymentOptions() invokes WC()->payment_gateways->payment_gateways(),
   > forcing early initialization of all WooCommerce payment gateway classes in 
   > an AJAX context.
   > Gateway initialization can trigger side effects: loading files,
   > registering hooks, emitting notices or accidental output (echo). Any unexpected
   > output before the AJAX handler finishes corrupts the expected response format.
   > When the AJAX response is polluted or interrupted, WordPress falls back to 
   > returning 0 or a 400 Bad Request.
 * P.S. no, we’re not able to provide you with a sandbox website to experience it
   yourselves. But I hope that’s enough.

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

 *  Plugin Support [mathdaniel](https://wordpress.org/support/users/mathdaniel/)
 * (@mathdaniel)
 * [5 months, 2 weeks ago](https://wordpress.org/support/topic/critical-bug-in-v1-3-that-intervenes-in-each-request-in-admin-panel/#post-18697119)
 * Hello [@daiohansed](https://wordpress.org/support/users/daiohansed/),
 * I hope you’re well.
 * Thanks for reporting what you’re experiencing.
 * We have already forwarded this to the team for review within the sprint cycle
   used to address the needs of all users.
 * To isolate the root cause, please test on a clean staging site (Storefront + 
   WooCommerce + our plugin) and share the exact steps you took, date/time and timezone
   of the attempt, the WooCommerce System Status Report, and error logs (WooCommerce
   → Status → Logs and wp‑debug.log if applicable). With that evidence we will be
   able to reproduce the issue and proceed accurately.
 * We’re standing by.
 * Best regards, peace!
 *  Thread Starter [daiohansed](https://wordpress.org/support/users/daiohansed/)
 * (@daiohansed)
 * [5 months, 2 weeks ago](https://wordpress.org/support/topic/critical-bug-in-v1-3-that-intervenes-in-each-request-in-admin-panel/#post-18697745)
 * We’ve already switched to an alternative plugin, so unfortunately won’t be be
   able to investigate further.
 *  Plugin Support [mathdaniel](https://wordpress.org/support/users/mathdaniel/)
 * (@mathdaniel)
 * [5 months, 2 weeks ago](https://wordpress.org/support/topic/critical-bug-in-v1-3-that-intervenes-in-each-request-in-admin-panel/#post-18698479)
 * Hello [@daiohansed](https://wordpress.org/support/users/daiohansed/),
 * Thank you for letting us know.
 * It was a pleasure to help; our goal is always to assist users in achieving the
   most accurate results possible through clear isolation and testing.
 * If you decide to use the plugin again in the future, we’ll be happy to assist
   you once more.
 * Best regards,
   Peace!
    -  This reply was modified 5 months, 2 weeks ago by [mathdaniel](https://wordpress.org/support/users/mathdaniel/).
 *  Plugin Support [mathdaniel](https://wordpress.org/support/users/mathdaniel/)
 * (@mathdaniel)
 * [1 month, 3 weeks ago](https://wordpress.org/support/topic/critical-bug-in-v1-3-that-intervenes-in-each-request-in-admin-panel/#post-18828498)
 * Hello [@daiohansed](https://wordpress.org/support/users/daiohansed/),
 * I hope you’re doing well.
 * I’m reaching out to let you know that Version 2.0 is now available. This update
   includes a fix for custom status email handling when multiple statuses are enabled.
   It also resolves a related issue where settings might fail to save in specific
   cases.
 * Please update to Version 2.0 and try again.
 * Best regards, peace!

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

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcritical-bug-in-v1-3-that-intervenes-in-each-request-in-admin-panel%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/bp-custom-order-status-for-woocommerce/assets/icon-256x256.
   gif?rev=3056274)
 * [Custom Order Status Manager for WooCommerce](https://wordpress.org/plugins/bp-custom-order-status-for-woocommerce/)
 * [Support Threads](https://wordpress.org/support/plugin/bp-custom-order-status-for-woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/bp-custom-order-status-for-woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bp-custom-order-status-for-woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bp-custom-order-status-for-woocommerce/reviews/)

## Tags

 * [400 Bad Request](https://wordpress.org/support/topic-tag/400-bad-request/)
 * [status](https://wordpress.org/support/topic-tag/status/)

 * 4 replies
 * 2 participants
 * Last reply from: [mathdaniel](https://wordpress.org/support/users/mathdaniel/)
 * Last activity: [1 month, 3 weeks ago](https://wordpress.org/support/topic/critical-bug-in-v1-3-that-intervenes-in-each-request-in-admin-panel/#post-18828498)
 * Status: not resolved