Bug 18896 - Changes to Patron's Contact Info Not Logged if Submitted Via OPAC
Summary: Changes to Patron's Contact Info Not Logged if Submitted Via OPAC
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Transaction logs (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-05 15:28 UTC by Chris Slone
Modified: 2020-11-30 21:44 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
Duplication of address on patron modification (312 bytes, text/plain)
2019-08-20 20:44 UTC, Laurel Moran
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Slone 2017-07-05 15:28:38 UTC
If a patron used the OPAC to update their contact information it is not recorded in the logs. 

To replicate:

1.) Make sure that Logging->BorrowersLog is  set to 'Log' and that Opac preferences->Features->Opacpatrondetails is set to 'Allow.'
2.) Log in to the OPAC, go to the 'your personal details' tab, make changes, and click 'submit update request.'
3.) In staff clien, go to the pending patron modification, select approve, and click 'submit.'
4.) Go to the patron's record and click on the 'Patron Modification Log' tab, the log will not reflect the modification.
Comment 1 Myka Kennedy Stephens 2018-05-31 22:39:45 UTC
I would like to +1 this. We just had an instance when the changes submitted by the patron in the OPAC and approved in the staff client caused some unintended changes. It was difficult to track down what exactly had happened since there was no log of the request or the change.
Comment 2 Laurel Moran 2019-08-20 20:44:02 UTC
Created attachment 92389 [details]
Duplication of address on patron modification
Comment 3 Katrin Fischer 2020-04-19 12:43:34 UTC
I just verified that this bug has been fixed in recent versions, but couldn't pin down the bug report fixing it.