This is a feature jjeff and I wrote for a site we're building that we thought could be useful to the community. Screenshots attached.
The idea is to add an option to LT to present a single page to logged-out users that can both register them AND log them in, using nice JS buttons so that you don't need to re-load the page in between, instead of relying on tabs which (as the UMN usability study saw) people have a hard time seeing.
A side-effect of this patch is you need the "I forgot my password" link on the login form itself (where, arguably, it makes more sense anyway), so a new option's been added for that as well.
Patch comin' right up.
Comment | File | Size | Author |
---|---|---|---|
#15 | logintoboggan-264332-15.patch | 10.15 KB | fearlsgroove |
#14 | logintoboggan-264332-14-updated.patch | 14.7 KB | AaronBauman |
#10 | logintoboggan-264332-10.patch | 11.04 KB | jjeff |
#9 | logintoboggan-264332-9.patch | 11.04 KB | jjeff |
#7 | logintoboggan.patch | 8.94 KB | KarenS |
Comments
Comment #1
webchickPatch.
Comment #2
webchickOops. How about one *without* all the stuff from #264300: Use checkboxes rather than "Enabled"/"Disabled" radios :D
Comment #3
litwol CreditAttribution: litwol commentedI created the patch from within the module folder.
webchick: this includes all the changes we've discussed on irc.
Comment #4
Fayna CreditAttribution: Fayna commentedI patched the module and enabled this unified page as well as the password link but am still unsure how to access it. Should it be at ../user? All that shows up is the "I forgot my password" link on the login form.
Comment #5
hunmonk CreditAttribution: hunmonk commented#login-message
instead of.toboggan-unified #login-message
? the id tag already specifies element, so i'm not understanding why it's useful to prepend a class.// TODO: Somehow add a class of "default" to whichever form is the default.
should be handled before this is committed.if (Drupal.jsEnabled) {
, and the new format isDrupal.behaviors.myBehavior = function (context) {
Comment #6
EvanDonovan CreditAttribution: EvanDonovan commentedHas any more work been done in this area? I think a unified login/register page would really streamline things for users....
Comment #7
KarenS CreditAttribution: KarenS commentedI brought this patch up to date against the 6.1 branch (couldn't figure out what the 6.2 branch was for). This would still be a nice enhancement.
Comment #8
RobbM CreditAttribution: RobbM commentedGreat patch. But for 6.x-1.7, it seems that any occurrences of
#toboggan-unified
need to be replaced with.toboggan-unified
(inunified.js
). Sorry, I'm not able to update the patch.Comment #9
jjeff CreditAttribution: jjeff commentedHere's an updated patch with a few improvements such as clearing the menu cache when the unified login setting is changed and fixing the JS file with the changes in #8.
We've been using this functionality on Lullabot sites for some time now. I really hope that it will make its way into LoginToboggan. If not, perhaps we will have to split this off into a separate module. That would be a shame.
-Jeff
Comment #10
jjeff CreditAttribution: jjeff commentedMinor text changes to change "I forgot my password" to "Request new password"
Comment #11
hunmonk CreditAttribution: hunmonk commentedthanks for the updates. i'm not accepting new features for 6.x anymore, but my plan is to get this into 7.x before its first official release.
Comment #12
hunmonk CreditAttribution: hunmonk commentedtook the patch from #10, ported it to 7.x, futzed for a few hours to work out all the kinks, and committed it to 7.x-1.x-dev.
the one major change from the earlier patch is that i ripped out the option for the request password link, and just rolled the display of the link into the unified login setting. that option alone left the 'Request new password' tab on the page, and added another link to get to the same place -- didn't feel like good UI to me. i think the tab alone is enough if the unified login page is not being used.
thanks to everyone for keeping up the work on this patch. it took awhile, but it finally got in -- the major new feature of the 7.x branch... :)
Comment #14
AaronBaumanPatch in #10 didn't apply cleanly for me -- here's an updated patch against 6.x-1.8.
I understand that this will not get in to 6.x, but thought for the majority of Drupal users who are still using 6.x it still might be useful.
Comment #15
fearlsgroove CreditAttribution: fearlsgroove commentedRe-rolled for 1.9
Comment #16
Lionsharz CreditAttribution: Lionsharz commentedHi
Is there a way to display this unified form in a block?
Comment #17
AaronBauman#15 works against 6.x-1.10 with fuzz.