10 ms·
The recommended procedure for "automatic" upgrades, as described on that page, is to back up your entire database and disable all plugins beforehand.
by idlewords 17y ago
The recommended procedure for "automatic" upgrades, as described on that page, is to back up your entire database and disable all plugins beforehand.
- lucumo 17y agoNot as bad as phpBB's "automatic" upgrade, which gives you a tar-ball of changed files which you're supposed to unpack...
- reedlaw 17y agoExactly. I give WP a lot of credit since it's the only web application I know of that can be upgraded from its own interface without the need to ever login to a shell or manually FTP files to the server.
- jasonneal 17y agoThat's what I love about WP. Joomla 1.6 (about to go into Beta) also has this feature as a built in component (which is also installable to Joomla 1.5. When I read the article right at the first paragraph I was appalled. Quote: "...devote half your life to learning and understanding WordPress administration..." Really? Half your life to learn how to click ONE link? I don't get it, has the author here never even upgraded Wordpress?
- amalcon 17y agoCall me crazy if you like, but I'd never use a webapp that has that feature. It just opens you up to more potential security problems. For example, it appears to operate over in-the-clear HTTP. Poisoning someone's DNS cache and then somehow triggering an "upgrade" = changing their software to whatever I want. Also, "Note that your files all need to be owned by the user under which your Apache server executes, or you will receive a dialog box asking for "connection information," and you will find that no matter what you enter, it won't work." That's a security no-no if I've ever seen one.
- reedlaw 17y agoThat should take, at most, a few additional clicks, since plugins can be disabled en masse and databases can be backed up with another plugin (or done automatically at the server).