@allbutone Thank you. We are checking this and keep you updated here.
@allbutone thanks for reporting it here. @renehermi thank you.
A combination of two issues has caused the main issue:
One in wp staging, the other in the “Admin and Site Enhancements” plugin
We accidentally loaded an HTML input element into every wp-admin page instead of plugins.php. It’s part of our optional feedback form when someone deactivates wp staging. It has no function on any other page, but when saving its settings, the other plugin checks for input with the submit type.
As it does not select the input type by ID, it falsely detects our input element and can not save its settings.
We will remove our redundant code with the next next release. Still, the Admin and Site Enhancements plugin can make its code more robust against such conflicts by giving its submit button an ID and listening to that ID instead of all input elements on a page.
@renehermi good catch. I’ll be making changes in the next release of ASE as well. It should now listen to the submit button’s ID, which is specific to ASE. Thanks!