Improve the how to upgrade your database page on wordpress.org

[Denis-de-Bernardy]

Or then, we need to seriously improve the codex page.

FWIW, I just got a customer on the phone, and, to the question "why haven't you upgraded for so long?" (she was on WP 2.7) the answer went something like:

I've clicked this link that tells me to backup. And I don't understand the slightest thing.

My guess is that up to a third of my customer-base is scared to death at the idea of upgrading because of that link to the codex page. And I wouldn't be surprised if it's the same for WP as a whole.

I've itched to mark this as blocker... since the security implications for WP are substantial.

[dd32]

Then the documentation needs to be rewritten in a way that all users will understand.

Alternativly, The upgrade screen could be reworded slightly, along the lines of

"Backing up your database or performing a Export to ensure that your data is safe is suggested to be done regularly, We'd like to invite you to ensure you a recent backup handy before upgrading. Please note, that a backup is usually required if you are not happy with the new version and wish to downgrade back to a previous version"

That last section about downgrading is key in my opinion, It gives users a reason to see why a backup/export is needed, its not the upgrade proceedure thats likely to damage data, its if they wish to go backwards. Which now we'll be supporting security releases for 2.8, Seems like a kick in the right direction.

[Denis-de-Bernardy]

Not sure... I've been using this less gentle approach over the past few months with great effect:

WordPress XXX is available! Please upgrade your site before it gets hacked.

I've recently added the following for php4 users:

Security Warning: Your server is configured with an outrageously outdated version of PHP. Please contact your host, and insist that they upgrade your server's software. Alternatively, consider switching to abetter host -- one that doesn\'t abandon its users on insecure servers.

[azaozz]

Perhaps instead of marking this ticket as blocker, better to update the codex page making it "less scary"?

[mrmist]

I've redrafted the Codex page for upgrading WordPress to make it (what I consider) a bit friendlier and less scary. Also, the attached patch references the page alongside the warning to back up databases.

[mrmist]

update core link to codex

[mrmist]

Setting a milestone & component for the change to update-core part of the ticket

[nacin]

(In [13898]) Add link to Updating WordPress codex page. props mrmist, fixes #11280.