Cannot Save Settings Error in 7.9.3

  • Resolved CK MacLeod

    (@ck-macleod)


    1 year ago

    We have been experiencing an error similar to the one discussed (exhaustively) here: https://www.ads-software.com/support/topic/urgent-error-saving-settings-not-working/page/2/ The rather odd workaround mentioned there (Customizing the Google/Apple buttons) did not help.

    What DID solve the problem was rolling back the Gateway to 7.9.1 from 7.9.3.

    We initially encountered the problem when trying to enable test mode. On the same settings page, the error highlighted a Bank Statement issue that was not correctable even after we visited our Stripe account and tried to update or re-save. The error message onscreen was “The customer bank statement is invalid. Please make sure it:
    – Has between 5 and 22 characters” I also see from the changelog that the descriptor statement was the focus of a recent update (7.9.2).

    This behavior occurs with all plugins other than WooCommerce and the Stripe Payment Gateway de-activated, a WordPress annual theme in place (TwentyTwentyOne), and the latest available updates of WooCommerce and the Gateway

    DevTools Console shows a Failed to load resource: the server responded with a status of 400 () and the identified link is [siteurl]/wp-json/wc/v3/wc_stripe/settings?_locale=user This looks highly indicative. Both this error and the specific bank statement error go away with 7.9.1 in place of 7.9.3.

    We were also initially unable to de-activate the Gateway plugin itself – an issue that I believe others have reported in different contexts. We were able to force de-activation from from file management, and then to delete the plugin, before manually uploading the old version we had on disk.

    • This topic was modified 1 year ago by CK MacLeod.
    • This topic was modified 1 year ago by CK MacLeod.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @ck-macleod,

    We have been experiencing an error similar to the one discussed (exhaustively) here: https://www.ads-software.com/support/topic/urgent-error-saving-settings-not-working/page/2/ The rather odd workaround mentioned there (Customizing the Google/Apple buttons) did not help.

    We are aware of this issue. While this issue isn’t common, our development team is actively working on a fix for it: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/2921

    The customer bank statement is invalid. Please make sure it:
    – Has between 5 and 22 characters” I also see from the changelog that the descriptor statement was the focus of a recent update (7.9.2).

    The 5 to 22 characters requirement is a policy from Stripe, not from WooCommerce Stripe Payment Gateway. Please ensure that the statement descriptor in your Stripe account settings meets this requirement.

    If this is not required, you could remove this information too. The WooCommerce Stripe Payment Gateway plugin should work without this too.

    We were also initially unable to de-activate the Gateway plugin itself – an issue that I believe others have reported in different contexts. We were able to force de-activation from from file management, and then to delete the plugin, before manually uploading the old version we had on disk.

    This is unusual and indicates something else is happening. Can you enable WP Debug and also debug in Stripe setting and share the log found in WooCommerce → Status → Logs and inside the error log file generated on your server?

    You can do this on a staging site without interacting on your live site: https://woo.com/posts/what-is-staging-site-wordpress-how-to-set-one-up/

    In the meantime, you can run a conflict test to help you identify the cause of the issue. More info: https://woo.com/document/how-to-test-for-conflicts/

    Looking forward to resolving this issue for you.

    tbone07734

    (@tbone07734)

    @shameemreza FYI having exact same issue. Error message shows even when loading the page and simply pressing “save”. No way around. Please post fix, as this is blocking us from implementing much needed features to our site.

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @tbone07734,

    Did you try the workaround shared here? Didn’t it work?

    Additionally, please can you share a copy of the following:

    • System Status Report: Navigate to WooCommerce → Status. Select Get System Report and then Download for Support.
    • Fatal Error log: Share a copy of any fatal error log found under WooCommerce → Status → Logs.

    You could copy and paste your reply or share it via Mozilla Community Pastebin and share the link here.

    Looking forward to hearing from you!

    I have the same problem with version 8.0.0, and I’ve reported in https://www.ads-software.com/support/topic/cannot-save-stripe-keys-on-a-site-with-http-only/.

    anastas10s

    (@anastas10s)

    Thank you, @strategio. For creating a GitHub issue, also.

    @ck-macleod @tbone07734 :

    To clarify, are you still seeing this, after updating to 8.0.0?

    Sorry @anastas10s, I misunderstood your last comment, my bad.

    Thread Starter CK MacLeod

    (@ck-macleod)

    The update worked in our staging environment – but not in our live environment. When trying to save settings we still get the “Error Saving Settings,” and the aforementioned 400 error in DevTools Console: [siteurl]/wp-json/wc/v3/wc_stripe/settings?_locale=user

    Plugin Support omarfpg a11n

    (@omarfpg)

    Hi @ck-macleod,

    The update worked in our staging environment – but not in our live environment. When trying to save settings we still get the “Error Saving Settings,” and the aforementioned 400 error in DevTools Console: [siteurl]/wp-json/wc/v3/wc_stripe/settings?_locale=user

    Have you tried this workaround after updating to 8.0.0 which was released just yesterday?

    Additionally, could you please send us a System Status Report from your live site to learn more about your environment? You can find it via WooCommerce > Status > Get system report > Copy for support. (feel free to redact your site URL for privacy as you’ve been doing).

    Additionally, Fatal error logs?(if any) under WooCommerce > Status > Logs.
    You could copy and paste your reply here or paste it via?https://gist.github.com/?and send the link here.

    Once we have more information, we’ll be able to assist you further.

    anastas10s

    (@anastas10s)

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Cannot Save Settings Error in 7.9.3’ is closed to new replies.