Closed (won't fix)
Project:
LoginToboggan
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Feb 2011 at 14:37 UTC
Updated:
17 Aug 2011 at 18:23 UTC
If you set "Force registration form" in Janrain Engage (formerly RPX)'s settings and also require users to set password on registration form by using LoginToboggan's setting "Set password", you will get a "You must enter a password" validation error when trying to save the registration form. You usually need users to set a password on the traditional route, so the setting "Set password" needs to be set. But when trying to register by using external providers via Janrain Engage (formerly RPX) module, you don't have to set a password and the fields for password are not, indeed, there, but the validation comes up and displays that error message.
I've developed a patch that's bypassing validation for Janrain Engage registration form. I hope that's useful for those having the same problem as I did.
| Comment | File | Size | Author |
|---|---|---|---|
| logintoboggan.module.patch | 627 bytes | tibip |
Comments
Comment #1
hunmonk commentedi don't commit commit module-specific patches to LT.
also, LT merely leverages core's "Require e-mail verification when a visitor creates an account" setting, so this isn't strictly an LT-specific issue.
this problem would need to be solved in a more generic way in order to make it into the module.
Comment #2
greg.harveyI think the only sensible way to achieve this would be to have some sort of bypass variable that can be set in LT admin.
But this feels like a feature request, not a bug report.
If you provide a patch that does this using a system variable set on the admin form, instead of reading the form ID for a specific module, that would be a generic approach and hunmonk can review. =)
Comment #3
steveparks commentedIt seems there wasn't enough demand for this generic functionality to generate a patch, and the original poster has managed to solve their specific problem so probably doesn't have interest in working on a generic new feature. Therefore I'm closing this feature request for now.
Please feel free to reopen with a patch attached ;)
Thanks
Steve
Comment #4
rafamd commentedWon't reopen because I don't have a patch, but I'm +1 for this as we want to use Janrain Engage with LoginToboggan.
Here's a related issue over Janrain Engage queue: #1176728: Integration with LoginTobbogan
Comment #5
nathancollins44 commentedYes!
We need Janrain Engage to work with Login Toboggan.
I am using D7 and the Janrain Engage (formerly RPX)7.x-2.1
I have created a new issue for D7 version of this RPX module
#1251370: We need Janrain Engage to work with Login Toboggan
"Janrain Engage Integration With Login Toboggan"
Lets get this show on the road !!!
Comment #6
greg.harveyMarked #1251370: We need Janrain Engage to work with Login Toboggan as a duplicate of this issue. As stated above, feel free to add a patch for this and set the issue to 'needs review'. Otherwise, it will be a long while coming, as the maintainers don't really have time for this right now.
Comment #7
rafamd commentedYes, we don't need separate issues for 6.x and 7.x, in fact, we are also using 7.x.
I guess we should follow the approach mentioned in #2.
Comment #8
hunmonk commentedfolks, i've thought this over, and am not going to commit a patch for this issue. LT works with the standard login form, therefore modules that do something non-standard should be responsible for making the necessary adjustments to it.
so it should either be handled at #1176728: Integration with LoginTobbogan, or written as a separate compatibility module.