This explores flows from the update notice. This site was running 4.3 RC3 and the beta tester plugin when vizreced, so the update-core.php screen shows beta track ui.
The codex pages linked to from the update notice and upgrade-core.php are not at all compelling. They’re the opposite of that. 🙂 You don’t see anything compelling until you reach the About page after doing the upgrade.
update-core.php really needs the shiny updates treatment. Upgrading to the next release is a flow that should be polished and compelling.
This entire process needs better localization.
#gallery-35 {
margin: auto;
}
#gallery-35 .gallery-item {
float: left;
margin-top: 10px;
text-align: center;
width: 33%;
}
#gallery-35 img {
border: 2px solid #cfcfcf;
}
#gallery-35 .gallery-caption {
margin-left: 0;
}
/* see gallery_shortcode() in wp-includes/media.php */
-
- Click Version 4.3 in the update notice.
-
- This is not a compelling page. 4.3 shipped without this page being updated. It had wrong dates and no link to the release announcement. Scroll down.
-
- Yuck. Linking to the release announcement would be better than this. Dismiss this tab, go back to the update notice, and click Please update now.
-
- Please update now leads here. This page doesn’t compel an upgrade either. This UI is placeholder ui that is long overdue for the shiny updates treatment. As part of that, we should add at least a link to the release announcement. i18n must be considered. Perhaps api.wordpress.org could return a localized link. Click Backup your database and files.
-
- Another uncompelling codex page. Dismiss this tab, go back to update-core.php, and click updating WordPress.
-
- Another uncompelling codex page. Dismiss this tab, go back to update-core.php, and click Update Now.
-
- This screen appears briefly before being redirected.
-
- Our about page is good, but you don’t see it until after you upgrade. Scroll down to take it in a check the version in the footer.
-
- Done.