I’m able to duplicate the issue. There are two possibilities:
1. Something changed in core regarding how to disable the Widgets block editor, and I need to update the plugin accordingly, or…
2. A recent change I made to the plugin is the cause.
I believe #2 is more likely, and I’m pretty sure I know what it is. There’s a bit of a chicken-and-egg situation here, as I’ve added hooks to the plugin to allow developers to extend its functionality. I had to encapsulate the code that applies all of the No Nonsense settings into a hook, and I had to move that hook to run a bit later than it used to.
My guess is that this change has caused the code to disable the Widgets block editor to run too late, so it’s having no effect.
I’ll investigate both possibilities and if there’s a simple solution, I should have a fix available later today.
Ah… good news… my first guess at a possible fix seems to work, and it’s a very simple fix. (Just a matter of changing the priority on the after_setup_theme hook.)
As long as I’m at it I’m going to do a bit more testing just to verify that all of the other settings are still working properly, and then I’ll roll out an update.
Thank you very much! I didn’t think it was just me. 🙂
Ha.. nope! I’m just about ready to roll this change out. As I was testing the other features, I realized that the “Disable site search” option was not removing the core Search block from the Block Editor. I’ve just wrapped up my testing on fixing that as well and I’m going to roll out both of these changes in the update. It will be version 2.4.1 and should be available within the next few minutes.
Thank you VERY much! The update did the trick.
