WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 4 years ago

#11280 closed enhancement (fixed)

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

Reported by: Denis-de-Bernardy Owned by: dd32
Milestone: 3.0 Priority: normal
Severity: major Version: 2.9
Component: Upgrade/Install Keywords: has-patch
Focuses: Cc:

Description

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.

Attachments (1)

update-core.patch (767 bytes) - added by mrmist 4 years ago.
update core link to codex

Download all attachments as: .zip

Change History (10)

comment:1 dd325 years ago

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.

comment:2 Denis-de-Bernardy5 years ago

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.

comment:3 demetris5 years ago

  • Cc dkikizas@… added

comment:4 azaozz5 years ago

  • Milestone changed from 2.9 to Future Release

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

comment:5 Denis-de-Bernardy5 years ago

  • Component changed from Security to WordPress.org
  • Milestone changed from Future Release to Unassigned
  • Summary changed from remove the suggestion to backup the database... to Improve the how to upgrade your database page on wordpress.org

comment:6 mrmist4 years ago

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.

mrmist4 years ago

update core link to codex

comment:7 mrmist4 years ago

  • Keywords has-patch added

comment:8 mrmist4 years ago

  • Component changed from WordPress.org to Upgrade/Install
  • Milestone changed from Unassigned to 3.0
  • Owner changed from ryan to dd32

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

comment:9 nacin4 years ago

  • Resolution set to fixed
  • Status changed from new to closed

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

Note: See TracTickets for help on using tickets.