August 2012 - Koha-bugs - lists.koha-community.org

[Bug 5002] New: No error message if category code already exists
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '15

02 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5002 Summary: No error message if category code already exists Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All URL: /admin/categorie.pl OS/Version: All Status: NEW Severity: minor Priority: P5 Component: System Administration AssignedTo: paul.poulain(a)biblibre.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 When adding new patron categories you can save a new category with an existing category code. There is no error message and the new category is not saved. Koha Version: 3.01.00.142 -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 23

[Bug 8437] New: Plack and database backup
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '15

01 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8437 Priority: P2 Change sponsored?: --- Bug ID: 8437 Assignee: jcamins(a)cpbibliography.com Blocks: 8268 Summary: Plack and database backup Severity: major Classification: Unclassified OS: All Reporter: paul.poulain(a)biblibre.com Hardware: All Status: ASSIGNED Version: master Component: Tools Product: Koha I've found a problem with patch of bug 8268, that you can see when you run plack: Variable "$backupdir" is not available at /home/paul/koha.dev/koha-community/tools/export.pl line 334. => the backup features won't work under plack (problem of variable scoping with Plack that put the script in a sub, making main() variable unaccessible in other subs. Problem solved everywhere with a our instead of my. The best option, that I would prefer -from far- for this new feature, being that we don't use such a our variable, but define backupdir where it's needed (+ it's just reading of a syspref, so not something costly) -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 8198] New: Need to track the call to "C4::Context->userenv->{'xxxx'} without check if it is undefined
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8198 Priority: P5 - low Change sponsored?: --- Bug ID: 8198 Assignee: gmcharlt(a)gmail.com Summary: Need to track the call to "C4::Context->userenv->{'xxxx'} without check if it is undefined Severity: normal Classification: Unclassified OS: All Reporter: christophe.croullebois(a)biblibre.com Hardware: All Status: NEW Version: master Component: Architecture, internals, and plumbing Product: Koha linked with bug 8197, all the lines like that will return a koha error if session cookies have been deleted. It would be nice to correct all the relevant lines. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 8361] New: Issuing rule if no rule is defined
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8361 Priority: P5 - low Change sponsored?: --- Bug ID: 8361 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Issuing rule if no rule is defined Severity: major Classification: Unclassified OS: All Reporter: paul.poulain(a)biblibre.com Hardware: All Status: NEW Version: master Component: Circulation Product: Koha If we reach a case where no issuing rule is defined, Koha always grant issuing. Koha should refuse any check-out if no rule is found (validating the issuing is silent, while rejecting the check-out will clearly show that something is missing in your configuration) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 8389] New: BEGIN considered harmful
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8389 Priority: P5 - low Change sponsored?: --- Bug ID: 8389 Assignee: gmcharlt(a)gmail.com Summary: BEGIN considered harmful Severity: minor Classification: Unclassified OS: All Reporter: jcamins(a)cpbibliography.com Hardware: All Status: NEW Version: master Component: Architecture, internals, and plumbing Product: Koha Right now we are using BEGIN { } blocks in a lot of C4, including for database access in C4::Context. This means that any script that uses C4::Context, even if it doesn't actually need the database or is not being run, just compiled, will not function without a database present. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 8397] New: Can import patrons with duplicate userids
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8397 Priority: P5 - low Change sponsored?: --- Bug ID: 8397 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Can import patrons with duplicate userids Severity: normal Classification: Unclassified OS: All Reporter: oleonard(a)myacpl.org Hardware: All Status: NEW Version: master Component: Patrons Product: Koha If you use the "import patrons" tool to upload a CSV file of patron records it is possible to create more than one patron with the same userid. This should not be possible. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 8423] New: Koha/SearchEngine/Zebra/Search.pm fails 'perl -c' test
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8423 Priority: P5 - low Change sponsored?: --- Bug ID: 8423 Assignee: gmcharlt(a)gmail.com Summary: Koha/SearchEngine/Zebra/Search.pm fails 'perl -c' test Severity: blocker Classification: Unclassified OS: All Reporter: mtj(a)kohaaloha.com Hardware: All Status: NEW Version: master Component: Architecture, internals, and plumbing Product: Koha and here is the error... $ perl -c Koha/SearchEngine/Zebra/Search.pm Can't locate Data/SearchEngine/Zebra.pm in @INC (@INC contains: /home/mason/git/head /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at Koha/SearchEngine/Zebra/Search.pm line 5. BEGIN failed--compilation aborted at Koha/SearchEngine/Zebra/Search.pm line 5. a missing Data/SearchEngine/Zebra.pm file? -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 8471] New: loading an sql file into mysql, often fails when loading the 'letter' table
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8471 Priority: P5 - low Change sponsored?: --- Bug ID: 8471 Assignee: gmcharlt(a)gmail.com Summary: loading an sql file into mysql, often fails when loading the 'letter' table Severity: trivial Classification: Unclassified OS: All Reporter: mtj(a)kohaaloha.com Hardware: All Status: NEW Version: master Component: Database Product: Koha loading an sql file into mysql, often fails when loading the 'letter' table i have no idea why. the quick-fix is to drop - then create the database $ mysql koha_test < koha.sql ERROR 1005 (HY000) at line 3237: Can't create table 'koha_test.letter' (errno: 150) http://koha.1045719.n5.nabble.com/MySQL-Database-Restoring-Problem-from-3-4… -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 8504] New: patron import explains attributes import wrong
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8504 Priority: P5 - low Change sponsored?: --- Bug ID: 8504 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: patron import explains attributes import wrong Severity: normal Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Patrons Product: Koha On the Import patrons page there are notes on the right side of the screen. The fourth bullet displays incorrect information regarding the import of multiple patron type and value pairs in the patron_attributes field. If you are importing more than one patron_attribute pair then the entire comma-separated list of attribute types and value pairs must be surrounded by double quotes. I am not sure if this applies to the "second syntax" as mentioned in the last sentence in the bullet. Instead of STARTDATE:January 1 2010,TRACK:Day it should be "STARTDATE:January 1 2010,TRACK:Day" I don't know if this is a bug or a template change and I don't know about the second example given on that page yet. "STARTDATE:January 1, 2010","TRACK:Day" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 8658] New: Don't display patron attributes which have been limited to another patron category
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '15

31 Mar '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8658 Priority: P5 - low Change sponsored?: --- Bug ID: 8658 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Don't display patron attributes which have been limited to another patron category Severity: normal Classification: Unclassified OS: All Reporter: oleonard(a)myacpl.org Hardware: All Status: NEW Version: master Component: Patrons Product: Koha This probably only happens if you enter some data into patron attributes and then later limit entry of that attribute by category. I have a patron who has data stored in an attribute, but that attribute has since been limited to another patron category. Even though the data exists I don't think it should display if it no longer applies to that patron category. Otherwise you can see patron attributes displayed on a record which cannot be edited because the editor honors the limitation by category. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1