Fix all buttons in update manager workflow to use "Sentence case" labels
dww - October 15, 2009 - 22:20
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | update.module |
| Category: | bug report |
| Priority: | minor |
| Assigned: | dww |
| Status: | closed |
| Issue tags: | Quick fix, Update manager, Usability |
Description
There are a few spots in the new update manager workflow that use "Do Stuff" buttons instead of "Do stuff".
#1
Tagging for UX folks...
#2
Note, I just discovered #609772: authorize.php connection settings form broken (doesn't degrade, can't extend, pointless fieldset). That's basically unrelated to this patch, but I wanted to point it out for anyone testing this. I mention it here since the process of changing "Process Updates" (which was the wrong button label to be using inside authorize.php, anyway) to "Authorize" also made me want to change a few of the form element ids, etc. You might think that's what broke #609772, but no, that's broken right now in HEAD, regardless of this patch.
#3
Can you provide before/after screens?
#4
I can't believe I just spent 5 minutes providing screenshots for this patch. This is trivial button label fixing. This hardly requires in-depth UI effort. If you want to spend energy on that, please focus on something more relevant like #602490: Fix help text and action links to find the update manager pages or #602496: Clean up the update manager project selector page when updating your site. Thanks.
#5
dww, for what it's worth, it IS helpful to provide screenshots. People like myself are able to drop in completely out of context, and understand exactly what's going on without reading the entire issue que, or installing patches to figure out how you've improved something.
#7
@dww After reviewing the screenshots, I think we should not go down the path of using "Authorize" although it might sound accurate. It is a scary word, it is what you expect when you make 20 bank transfers not when you update your site, it might be a slight shift in perception but its is very critical for the confidence of users in the next step they will encounter after this.
Since this will almost always encounter in a flow, I think it is more fitting to call it "Continue" - which is also conform to the Drupal standard. Where we carefully choose to Continue, even when it might not be the most accurate work -for example in the installer.
Pretty much RTBC, from the rest.
#8
Right, Bojhan and I hashed this out in IRC and I suggested "Continue" there as the alternative. Either way is fine with me. So, here it is with "Continue"...
Note, I tried changing the underlying form elements and JS stuff to match "continue" instead of "process" again, but it all came crashing down. This JS code is quite fragile. :( That's going to have to be cleaned up at #609772: authorize.php connection settings form broken (doesn't degrade, can't extend, pointless fieldset), not here. So, this is now a trivial patch.
Based on Bojhan's UI review, and the trivial nature of the current patch, this is now RTBC.
#9
#10
Fixed a few minor code-style issues in the comments being touched by this patch, instead of including those fixes over at #605344: Docs and code style fixes for update manager since then the patches would conflict.
#11
Looks good. Committed to HEAD.
#12
Automatically closed -- issue fixed for 2 weeks with no activity.