WooCommerce Paypal "Pay Later" settings not updating (3301)

[MeganAnne09]

Describe the Bug

I have been trying to update the settings in the Pay later tab for paypal with WooCommerce and it keeps reverting to the original settings, I don't want this banner allover my website in the category pages, I just want it at checkout, but even if I disable it, it won't save that I disabled the pay later feature.

To Reproduce

1. Go to "Plugins > WooCommerce Paypal > go to Pay later Tab'
2. Click on 'any of the settings off and hit save and it will not update even though it says it saved the settings.'
3. Scroll down to …'
4. See error it isn't giving an error it just won't save.

Screenshots

^Changes I want

^After I hit save changes

Expected Behavior

My changes actually get saved.

Actual Behavior

Nothing is saving

Environment

• WordPress Version 6.5.4
• WooCommerce Version 9.0.0
• Plugin Version 2.8.0
• Browser [e.g. Chrome, Safari] and Version CHROME
• Any other plugins installed Hostinger AI, Hostinger Easy Onboarding, Hostinger Tools, LiteSpeed Cache, Woo Product Add-ons, WooCommerce, WooCommerce Print Invoices/ Packing Lists, WooCommerce Shipping & Tax, WooCommerce Square, WooCommerce.com Update Manager

Additional Details

System status

<!--If applicable, paste the system status here. Please ensure you redact or remove any identifying information. -->

[ChrisPVille]

I can confirm I'm also seeing this in a pretty minimal WooCommerce install, plugin version 2.8.0. It seems suspiciously similar to #2243 #2319 and #2302 which I guess represents some sort of regression/incomplete fix from the 2.7.1 PR meant to address this

[InpsydeNiklas]

Hi folks, thanks for the issue report. The saving procedure for the Pay Later messaging configurator has been revised a few times already, but according to the reports, it may still be unreliable in certain instances, especially in setups with certain caching plugins. We apologize for the inconvenience and are investigating ways to improve the compatibility for a future update.
In the meantime, I recommend reaching out to our support team to be informed about the latest updates and so we can gather more details about affected systems. Thank you!

The originally intended workaround for potential messaging configurator-related issues has been to disable it with this snippet. However, this snippet is causing an error on the latest 2.8.0 update, but has been addressed with a small tweak in #2327 for the upcoming 2.8.1 update.

[david101design]

2.8.1 (+Litespeed cache) it is working with Chrome, but not Firefox.