Closed (outdated)
Project:
Inline Registration
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Jan 2008 at 20:56 UTC
Updated:
14 Aug 2021 at 03:19 UTC
Jump to comment: Most recent
Comments
Comment #1
gulliverrr commentedQuite an old post but I have the same problem (in Drupal 6 now) or I havent googled enough.
Do you have a solution to this exact scenario (publish ONLY when email is validated)
Thanks
Comment #2
pieterdcI have this problem too, but it was to be expected as this is a documented issue both in the README.txt file and on the project (description) page.
I guess inline_registration_submit() should check if the 'user_email_verification' variable is set to TRUE.
If so: unpublish the node that was just created or even better: set the node to 'not published' before it gets created - if possible.
Secondly: the user account confirmation link -> path 'user/reset/%/%/%', which calls user_pass_reset, which should be intercepted somewhere to publish the - previously mentioned - node.
Any suggestions, feedback, patch?
Comment #3
mrtoner commentedA bit of feedback: I'm looking to use this with Case Tracker to allow anonymous users to open support tickets, so I want the ticket to be published even if the user hasn't validated.
Comment #4
mrtoner commentedA bit more feedback, although, given Matt's recent inattention to the module, changes may not be forthcoming soon:
It seems I can't use Inline Registration at the moment, for the very reason that it doesn't respect the user_email_verification setting. Actually, more accurately, it doesn't play with LoginToboggan, which I'm using to assign new users to a non-authenticated role until they validate their email address.
New users who register via an Inlne Registration form are assigned the authenticated user role instead, and now can do anything on my site a normal authenticated user can do -- without validating their address. (Of course, all the other options of LoginToboggan are ignored, too.)
I wonder if Rules/Triggers/Actions could be setup to mitigate this issue?
Anyway, +1 for dealing with the known issue and cooperation with LoginToboggan.
Comment #5
geek-merlinsub
Comment #6
elamanIssue is very old. Closing it.