Hi @andraganescu
Thanks for asking! To be honest, it just wasn’t a feature I expected, wanted or even saw the need for. Usually you can accommodate for changes in how things are don, but this one was very drastic in regards to the changes it introduced. Breaking changes.
I’m aware of the choices vs options discussion and how WordPress tends to go for choices. Not that I’m a huge fan of that, but it makes sense and I understand it.
It really isn’t a thing about how I would have wanted to know about that change in advance. But the plugin we’re commenting on here *clearly* shows that this could have been an option to phase ot in. When updated to this version site owners should be asked if they want to try it out now or later (again, it’s a filter… that could and should have been very feasible), with the possibility to switch back.
WordPress was pushing for more automatic updates. This is great and in my experience nothing major ever broke in years – I’m talking core and almost all plugins and themes that come from the repo. Now that we have auto updates almost globally, an update that changes integral parts of WordPress needs to be more carefully rolled out. It can be rolled out whenever but it should be switched on manually. Even if it will be the default at some point in the future (which it should clearly state, of course) and the option will be gone, then. It just can’t be dropped on people at potentially very inconvenient times. Especially, again, if it could very well be just an option.
What I don’t understand is that you seemingly refer to the existence of this plugin. Which would be something you only search for if you already have the problem and scramble how to solve it.
And again, not opposed to changes, not opposed to automatic updates – but I’d appreciate the WordPress team being more considerate of the user base and phase in drastic changes instead of just dropping them.
