Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
user.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
6 May 2009 at 19:25 UTC
Updated:
24 Jul 2013 at 09:01 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tstoecklerAnything that cleans that page up...
Nice work, works great.
Comment #2
catchtagging. Screenshots look good, didn't look at patch yet.
Comment #3
yoroy commentedLooking good but a 'before' page would still be helpful.
Oooh, look there it is: http://img.skitch.com/20090507-nnm1at43ure82iw4ifd8dys7my.jpg
Comment #4
dries commentedI'm delegating this patch to catch. I will commit it when catch thinks it is ready. (@catch, if you don't want to champion this patch, let us know please.)
Comment #5
mcrittenden commentedSemi-related: #432962: Add option to disable password strength checking
Comment #6
catchAll looks good except signatures is now lumped in with user account cancellation. I think we should try to keep it grouped with user pictures if possible (not sure what the fieldset for that should be called though). I kept thinking the checkbox was a setting related to the radios, which of course it isn't.
Comment #7
xanoThe 'problem' with user pictures is that enabling them also enables a bunch of other elements, making things kind of messy if they're not in a dedicated fieldset.
Comment #8
yoroy commentedAgree with catch. Extra mess when enabling user pics is not an argument, it's actually pretty nice these only show up after choosing to enable them. So yes, group signatures with user pictures, put it above user pictures and all the extra form fields (screenshot of those) for user pics will not break anything. Then rename the cancellation fieldset to "account cancellation".
Comment #9
xanoI don't like the idea of putting only a single form element in a fieldset without a real good reason. Also, can't we convert the four radios used for account cancellation into something simpler? With the current options radios are the best solution, but what if we rephrase or split the options?
Status -> Needs thought.
Comment #10
yoroy commentedThen group cancellation with signup options, makes sense to group the options for 'in' and 'out', no?
Comment #11
xanoMakes sense. I'll post a follow-up this evening :)
Comment #12
xanoI tried using vertical tabs for the e-mail fieldsets, just to see how it looked. I must say it's quite an improvement, although we do need a title for the tabs to indicate it's about the e-mail settings.

Comment #13
catchThat looks good, but yeah it needs a title.
Comment #14
xanoThere is currently no way to set a title for vertical tabs. We could either improve vertical tabs with a title or use a markup element instead. Either way, the title would be a piece of HTML not linked to the tabs in the way legends are linked to fieldsets and labels to inputs. Semantically (from a FAPI point of view) it might be best to add titles to vertical tabs first and then finish this issue.
Comment #15
gábor hojtsyGood looking changes. Since catch marked #460296: Clean up user settings form duplicate of this one, I am hereby requesting to roll in the Anonymous username setting to this new page. This patch makes the page look much better then my patch did, with a lot more changes obviously.
Comment #16
gábor hojtsyAlso, while I like "Who can register accounts?", I don't like how it shows up with the colon. Drupal usually does not use this question / answer format anyway.
Comment #17
dries commentedLooks good visually. Just tagging to help me keep track of this.
I think this is good use of the vertical tabs (unlike some of the other patches that I've seen) -- like catch et al, I do think it needs a title. Maybe just put it in a fieldset?
I also noticed that some options end with a point, whereas others don't.
Comment #18
xanoPutting the tabs in a fieldset makes the page messier than with the current patch. I suggest just adding some sort of a label, either by making vertical tabs accept a #title or by using #markup right before the tabs so it shows as a title. Moving the Anonymous setting is indeed a very good idea. I'll take that into account for the follow-up.
Comment #19
xanoComment #20
dries commentedI'd consider renaming 'Enable signatures' to 'Enable signatures for authenticated users'.
Similarly, I'd rename 'Enable pictures' to 'Enable pictures for authenticated users'.
The '?:' in 'Who can register accounts?:' is a bit odd but I'm not sure how to solve that elegantly.
Comment #21
xanoI forgot the question mark. I'm unsure how we can improve that too. Anonymous users can't personalise their accounts, so I guess it's pretty obvious that user pictures and signatures are for authenticated users only.
Comment #22
gábor hojtsyXano: I think that since you grouped the anonymous username with the authenticated personalization options, it looks more like we support personalization for anonymous (which we do support to some degree via anonymous contact details in comment module, but not here).
Comment #23
dries commentedI had exactly the same worry as Gabor in #22.
Comment #24
xanoSeparate fieldset for settings for anonymous users then?
Comment #25
gábor hojtsyXano: well, I suggested grouping it with the registration setting in my original issue. That seemed logical, since it showed a logical progress from anonymous user to user registration. You already have registration grouped with cancellation. I think it would make sense to put the initial anonymous username there too. That is important for how non-authenticated user posts look before they register and after their account is cancelled (in some cases).
Comment #26
catchPutting it right up top above registration works for me too - anonymous - registration - cancellation, nice easy progression.
Comment #27
xanoThere might be other options for anonymous users added by contrib. From this point of view a separate fieldset at the top of the page is best IMO.
Comment #28
akahn commentedI have been told that coding standards say to use U.S. English spelling, so 'personalisation' needs to be changed to 'personalization'.
Comment #29
xanoThe anonymous user name has moved to a separate fieldset at the top of the page. "personalisation" has been changed to "personalization".
Comment #30
catchThat still leaves the "Who can register accounts?:" issue - which is a very old issue I don't think we should try to fix here. I'd lean towards putting the patch in with that bug exposed, and then try to finally get it fixed before release.
#67211: Show colon after form title only when there is no other punctuation
Xano - could you post another screenshot?
Comment #31
Bojhan commentedCan I see more screenshots of the vertical tabs?
Comment #32
catchI read through the patch and I think this looks fine. Pretty sure the vertical tabs haven't changed since the last screenshot, so RTBC.
Comment #33
dries commented@Bojhan: why do you need more screenshots? A couple of screenshots are included above.
Comment #34
sirkitree commentedPatch works as intended. Very big improvements IMHO! Attached is a full page screenshot and here's a few more screenshots of the vertical tabs:
Comment #35
Bojhan commentedPassword recovery should be last, you have two groups Welcome and Acount - password recovery looks a bit placed in between these. However shouldn't hold this patch up, I asked for screenshots of Vertical tabs because in the origin patch of this ui pattern I saw some trouble (visually) with slim titles combined with long content area - in this patch it looks fine though.
Comment #36
sirkitree commentedHere's a patch with the vertical tab change mentioned above: password recovery weight I set to 100 which throws it to the bottom of the list. Looks good /methinks

Comment #37
xano#weight => 100 might be a bit overkill. What about just setting it to 1?
Comment #38
Bojhan commentedDon't know if 100 is the good approach, not any objections from me.
Comment #39
dries commentedI think we should move 'User settings' from 'Users' to 'Site configuration'. We can do that in another patch.
I think we should remove the trailing dot from most options -- we don't add dots to other options in core, except maybe when they are truly sentences.
Instead of 100, let's use 10.
Comment #40
sirkitree commentedComment #41
webchickA few more things.
I am pretty sure this patch has nothing to do with taxonomy.test. ;)
Please leave the comma at the end here, per coding standards.
No dots. Dries already said that.
exists. Period, not colon.
Comment #42
naheemsays commentedHaving a look at this patch - I like the changes, however I personally (and I know - just one voice that is not offering code...) do not like the idea of having a fieldset for anonymous users with just one option in there - could it also be merged with "Registration and cancellation" as was proposed by Gabor in #460296: Clean up user settings form?
I also liked how there was a description for the user pictures and the signatures next to their check boxes.
Comment #43
naheemsays commentedcross posted.
Comment #44
xano@nbz: It's a separate fieldset to allow other modules to add options for anonymous users here.
Comment #45
sirkitree commentedOk, here's a reroll against HEAD.
- keeps the ',' at the end of the #title change
- removes the periods from t() options
- period, not colon in comment
- weight of password recovery set to 10
Comment #46
webchickNow that's sexy.
Committed to HEAD. Thanks for all the hard work, folks!
Comment #48
dave reidPlease also see followup with #645738: UX: Vertical-tabify the rest of the admin/config/people/accounts page.
Comment #49
xano