4 ms·
One of the nice things about major releases of Wordpress is that it will auto patch minor releases. I believe this is a reasonable approach for most open source
by arkitaip 12y ago
One of the nice things about major releases of Wordpress is that it will auto patch minor releases. I believe this is a reasonable approach for most open source CMS even if it might break some functionality. You can also fairly easily add auto update for plugins and themes by modifying wp-config.php [1].
I suggest that themes/plugins with 100% compatibility ratings should be auto patched too. Auto patching themes can be problematic because updates override changes you've made to the theme files. So my other suggestion would be to automatically create a child theme for every installed theme so that devs can easily update the parent theme and keep changes made to it.
[1] http://codex.wordpress.org/Configuring_Automatic_Background_Updates http://codex.wordpress.org/Configuring_Automatic_Background_...
- ams6110 12y agoYes, better to have your site temporarily broken by an update than hacked and all data stolen. At least in many cases.
- nkuttler 12y agoOf course, giving your php webapp the permission to rewrite it's core files is a brilliant and secure idea!
- ams6110 12y agoMost operating systems do it. It's not an intractable problem.
- hahainternet 12y agoSaid operating systems typically require you to use an account that is inaccessible to almost all automated processes. This would not be the case, the two are not analogous.
- Retric 12y agoSigned binary's can get you most of the way there. It's still a trade-off and for most users waiting to apply a security patch is a larger danger.
- dubcanada 12y agoI really don't think this is such a bad idea, I would actually like to see this. In my hosting environment I have a single location for all my drupal websites core files, and I just update that.