Bug 17366

Summary: create patron list, software error
Product: Koha Reporter: Arun <arunet>
Component: PatronsAssignee: Bugs List <koha-bugs>
Status: CLOSED INVALID QA Contact: Testopia <testopia>
Severity: minor    
Priority: P5 - low CC: arunet, gmcharlt, J.P.Knight, jonathan.druart, kyle.m.hall, lmoraes
Version: 16.05   
Hardware: PC   
OS: Linux   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Arun 2016-09-28 10:50:35 UTC
When we try to create patron lists the getting software error 

cgi-bin/koha/patron_lists/add-modify.pl

getting software error 

Software error:
Can't call method "patron_list_id" on an undefined value at /usr/share/koha/intranet/cgi-bin/patron_lists/add-modify.pl line 55.
Comment 1 Jonathan Druart 2016-10-05 07:46:47 UTC
I do not recreate.
Could you check your koga log file please, there is certainly an error in it.
Comment 2 Lucio Moraes 2016-10-20 07:45:18 UTC
Hi Arun,
I couldn't reproduce.
Have you checked logfile?
Cheers,
Lucio
Comment 3 Jonathan Druart 2016-11-01 09:05:38 UTC
Closing, please reopen if it persists.
Comment 4 Jon Knight 2017-03-15 10:45:02 UTC
I've just had the same thing happen on a fresh install of Koha.  The logs show:

[Wed Mar 15 10:29:35 2017] [error] [client p.q.r.s] [Wed Mar 15 10:29:35 2017] add-modify.pl: No owner passed in or defined! at /usr/share/koha/intranet/cgi-bin/patron_lists/add-modify.pl line 54., referer: http://koha-dev.lboro.ac.uk:8080/cgi-bin/koha/patron_lists/add-modify.pl
[Wed Mar 15 10:29:35 2017] [error] [client p.q.r.s] [Wed Mar 15 10:29:35 2017] add-modify.pl: Can't call method "patron_list_id" on an undefined value at /usr/share/koha/intranet/cgi-bin/patron_lists/add-modify.pl line 55., referer: http://koha-dev.lboro.ac.uk:8080/cgi-bin/koha/patron_lists/add-modify.pl

where p.q.r.s is my machine's IPv4 address.

However I've "solved" the problem - I was playing about as the Koha database admin setting the system up when I hit the error.  When I switched to use my own (superlibrarian) staff account, the error went away.  So this may be the case for other users and I thought it was a good idea to note it here.