We are working on what I believe is a tangle of sorts between LoginToboggan and CiviCRM.

I have opened a forum posting with CiviCRM here:
http://forum.civicrm.org/index.php/topic,18350.0.html

Originally we were getting an "access denied" at one point during the CiviCRM site join / contribute process. We changed one LoginToboggan setting and were able to get rid of the "access denied". (We disabled LoginToboggan's "Immediate login" as we are also using LoginToboggan's "Set password" capabilities.)

Unfortunately we do not receive the email with URL to verify email addy now.

Is there some sort of verbose logging we could enable in LoginToboggan to see when it thinks it is sending the email, see return codes, etc...???

BTW: I came across this thread...

hide core's "Require e-mail verification when a visitor creates an account"
http://drupal.org/node/409338

so just to verify, we have the box in LoginToboggan checked for "Set password" and the check box at /admin/user/settings unchecked. That IS the way it is suppose to be, correct?

Comments

hunmonk’s picture

hunmonk commented
Status: Active » Fixed

the LT checkbox and core checkbox are manipulating the same setting. if you have "Set password" checked, then LT's custom validation code should be running.

#409338: disable core 'Require e-mail verification when a visitor creates an account' setting is a feature request that is being addressed in 7.x -- it will not be addressed in 6.x.

nope, no verbose logging. install devel module and toss some dsm()'s in the code...

mdlueck’s picture

mdlueck commented
Status: Fixed » Active

the LT checkbox and core checkbox are manipulating the same setting.

For us, the LT "Set password" checkbox IS checked and at the same time the Drupal core "Require e-mail verification when a visitor creates an account" checkbox IS NOT checked.

What we are seeing seems therefor inconsistent with what you are saying. Please elaborate. Thank you!

hunmonk’s picture

hunmonk commented
Status: Active » Fixed

What we are seeing seems therefor inconsistent with what you are saying

it's not inconsistent. i said they manipulate the same setting, i didn't say they displayed them the same... ;)

the two checkboxes display the same setting, but from a different perspective. from core's perspective unchecking "Require e-mail verification" means the user can set their own password -- i find that expression convoluted and not very helpful when looked at from LT's perspective. therefore the "Set password" checkbox merely expresses the same setting in a more sensible context given what LT is trying to do. the description for the setting mentions this.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.