Bug 16646

Summary: Error message always displays for circulation in 3.22.07
Product: Koha Reporter: Kyle M Hall (khall) <kyle>
Component: CirculationAssignee: Kyle M Hall (khall) <kyle>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: abl, gmcharlt, jonathan.druart, kyle.m.hall, srdjan
Version: 3.22   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15823
Change sponsored?: --- Patch complexity: Trivial patch
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: Bug 16646 - Error message always displays for circulation in 3.22.07

Description Kyle M Hall (khall) 2016-06-03 11:10:27 UTC
This message is always displayed for circulation in 3.22.07: Staff members are not allowed to discharge borrowers, nor borrowers to request a discharge.
Comment 1 Kyle M Hall (khall) 2016-06-03 11:12:29 UTC
Created attachment 51990 [details] [review]
Bug 16646 - Error message always displays for circulation in 3.22.07

This message is always displayed for circulation in 3.22.07: Staff members
are not allowed to discharge borrowers, nor borrowers to request a
discharge.

Test Plan:
1) Go to circulation.pl
2) Note message
3) Apply the patch
4) Reload circulation.pl
5) No message!
Comment 2 Srdjan Jankovic 2016-06-06 03:32:50 UTC
I will sign it off if you wish, but I'm not getting any errors on master.
Comment 3 Jacek Ablewicz 2016-06-06 09:43:22 UTC
(In reply to Srdjan Jankovic from comment #2)
> I will sign it off if you wish, but I'm not getting any errors on master.

In master and 16.05, there is no warning / no error message in the GUI - for now, in those branches it only results in some extra warnings in log files ("CGI->param() called in the list context"). But the underlying issue is still there in master and 16.05 as well.
Comment 4 Jacek Ablewicz 2016-06-06 09:44:37 UTC
See also Bug 15823 comments #24 - #26.
Comment 5 Jonathan Druart 2016-06-06 12:32:06 UTC

*** This bug has been marked as a duplicate of bug 16670 ***