https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29291 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #1 from David Cook <dcook@prosentient.com.au> --- I think this might be outdated. I've noticed the OPAC_REG_VERIFY email in message_queue -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29291 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- There cannot be any password in the message thankfully. Maybe the misunderstanding is that it's not linked to the patron yet via borrowernumber and thus not showing on the notices tab. The patron doesn't have a borrowernumber until they click the verification link. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29291 --- Comment #5 from David Cook <dcook@prosentient.com.au> --- (In reply to Christopher Brannon from comment #4)

I don't think I am being understood here. I am not talking about the template of OPAC_REG_VERIFY. That is all well and good. What I am not seeing is a copy of the email sent to the patron in notices.pl. It would be great if we could see what was sent out here, and when it was sent. It would also be great if we could resend it, if they missed their window of time to respond.

You're misunderstanding Katrin's comment. The email doesn't appear in notices.pl because it's not linked to the patron by borrowernumber, since the patron and its borrowernumber doesn't exist until after they verify the registration. You could see the information via a SQL report, but it's true there's no way of resending it, although the window to respond out of the box is 14 days. If they haven't signed up in that time, I think it's reasonable to have them try to self-register again. I don't really see this one changing, but I suppose it's possible someone could sponsor an enhancement that provides a UI for an administrator to see all emails in the message_queue and lets them resend whatever they want. But I think that would different to "Self Registration e-mail verification is not stored in notices". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29291 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #7 from Christopher Brannon <cbrannon@cdalibrary.org> --- Okay, I think I understand now. Until they verify, the account isn't created? So, forgive me for not walking through the process. Are they asked to create a login before they provide all the information and email address? If not, where is all their information stored until the email address is validated? I'm just trying to understand which comes first, email validation, or the storage of their self registration information. And maybe this needs to morph into a different subject/title, but what if an email address is changed or added later, either by staff or patron. It seems that right now the only validation happening is at registration, but no other time. It seems that we need to work towards adding this notification to notices.pl, if not for this specific instance, but for the possibility of validating addresses at some other point. I know. I am putting the cart before the horse here. But back to my question. Is there no patron info stored before the validation email goes out? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29291 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #9 from Christopher Brannon <cbrannon@cdalibrary.org> --- Well, you keep closing it, and I would like to keep it open for discussion, but I'm not given that option when you close it. I think this is something we should work on. I don't think this notification has to slip through the cracks in the process. It seems to me, if this information is kept in borrower_modifications, we could find some way of tying the email to this information. Regardless of whether the email serves a functional purpose in notices.pl, it serves us to keep a record of communications. Having this piece slip through the cracks because the account can't be created until they respond is not enough of a reason to not keep record of it where staff can see it. I know, it isn't crucial, but it would be more thorough to put this in the notices.pl after the account is validated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29291 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Self Registration e-mail |Link self registration |verification is not stored |verification email to |in notices |patron account after | |verification --- Comment #10 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I changed the bug description. I think at the moment we don't have good enough information to reliably link. Maybe keeping the letter_id in borrower_modifications could be a way. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29291 --- Comment #12 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Christopher Brannon from comment #11)

Thank you for hearing me out on this, and putting up with my noise. Just trying to make the most sense out of all of this.

I think I could have done a bit better here. Glad we came to a solution. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.