Bug 18988 - OPAC password not going by autoemailprimaryaddress preference
Summary: OPAC password not going by autoemailprimaryaddress preference
Status: In Discussion
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: 16.05
Hardware: All Linux
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-27 07:37 UTC by Kumar
Modified: 2018-02-12 18:07 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kumar 2017-07-27 07:37:23 UTC
The way OPAC password recovery is working with koha 16.05 as understood by me is below: 

1. We need to enter userid(Loginid)
2. Enter email - any email associated with the patron in the borrower table 
3. Verifying email associated with userid(Loginid) in all email fields of that patron
4. The mail is being sent to the particular mailid entered in password recovery form(if it is matching)

As per the setting in patron preferences, iam understanding that, if the mailid associated with userid is verified and matching, then the mail trigger should be based on the autoemailprimaryaddress preference and not the mailid entered in the password recovery form. 

Password recovery form is not going by the patron preference setting though other notices are using that preference. I think this should be rectified. 

Please correct me if iam understanding this incorrectly.
Comment 1 Katrin Fischer 2017-08-15 16:09:27 UTC
Hm, I am not sure about this, I think this might need some discussion.

If the user has entered an email address while resetting their password, they will expect the e-mail sent to this address and will check this address for the expected email. They might also have forgotten which other emails they have registered with the library. So the current behaviour makes sense to me.
Comment 2 Kumar 2017-08-15 16:37:24 UTC
Iam able to achieve this by hiding the email using jquery statement in opacuserjs. Now mails are going as per autoemailprimaryaddress preference. 

Sorry for posting a bug on this. This can be closed.
Comment 3 Kumar 2017-08-15 16:52:05 UTC
But I feel that as all other mails are going by that preference, this also go by that.

If the member is not receiving any emails like dues, checkout slips etc... on his regular mail id, then the member will contact the library and ask to update the mail id generally. 

or can the mail be sent to all the multiple ids entered in the borrower table?

Also I noticed that the password recovery mail going to the BCC mail id mentioned in the system administration - Is this correct thing? The BCC id person can also reset the password using that link.
Comment 4 Katrin Fischer 2017-08-15 17:46:06 UTC
Hi Suresh, don't feel sorry for filing a bug ever :)

I think there are arguments for both - using autoemailprimaryaddress or not. If you want, you can try asking on the mailing list to get some more opinions.

There is another long standing enh bug, that would enable to send to multiple addresses - bug 12802.

The BCC should usually be a staff member account. As staff members can always reset a patron's password, I feel this is not so problematic.