No, it's a join of #__users and #__comprofiler to show the evidence and omit the columns that are irrelevant. I had to do the join to show all of these columns together.
Not sure what to suggest then. Sounds like something is altering the confirmation flow and making the user blocked. If you're doing any user stores (e.g. Field action) during confirmation process try turning on Reload User under Parameters of those auto actions.
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
Yes, I am as a matter of fact. Setting the cb_dateconfirmed is done with a field action onAfterUserConfirm. That's the only Field action, but that's not the only onAfterUserConfirm action. The others are all Code actions, and I just added one query action to set block=0 onAfterUserConfirm also (first, before any of the others). I've enabled Reload User on all of them. We'll see what happens over the next few days.
krileon
