November 2011 - Koha-bugs - lists.koha-community.org

[Bug 7209] New: incomprehensible character after a search in the database USER INTERFACE
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '12

08 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7209 Bug #: 7209 Summary: incomprehensible character after a search in the database USER INTERFACE Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 - low Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: alexandre.lengereau(a)biblibre.com QAContact: ian.walls(a)bywatersolutions.com Created attachment 6273 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=6273 Advanced Search Hi, I'm french sorry for my english if i do some mistake. For frech like me, there is something i d'idnt' like in the user interface is the keyword when i launch a search who appear. For example: If i search "Victor hugo" in the search bar i get: “kw,wrdl: victor hugo ” returned 75 results. What is this keyword "kw,wrdl" Is it necessary to see this keyword for most of the user ? I think not. I recommand to remove this keyword. So if i lanch a very advanced search. I can get all this keyword: “ mc-itemtype,phr:LIVR ln,rtrn:ita aud:b Material-type:e Literature-Code:b Biography-code:a ctype:b Type-Of-Serial:z” In one line. For the user interface is not really good. It's why i consider this a bug. In attachement some screenshot... -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 4

[Bug 6627] New: [security] insecure file creation
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '12

07 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6627 Bug #: 6627 Summary: [security] insecure file creation Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: semarie-koha(a)latrappe.fr QAContact: koha-bugs(a)lists.koha-community.org Some files are insecurely created in /tmp system-directory. File: C4/Auth.pm '/tmp/sessionlog' File: installer/InstallAuth.pm '/tmp/sessionlog' File: installer/externalmodules.pl '/tmp/modulesKoha.log' File: C4/Print.pm '/tmp/kohares' As all have well-know names, don't survive a reboot and are hosted in 1777 directory (/tmp), it is possible, for *any* user on the host, to create a symlink, that koha will use to alter any files (respecting his permissions). I suggest to create (and use) a special directory for all of them. The debian place should be /var/lib/koha/. This directory should be readable/writeable by the apache user (www-data) only (and eventually, by the owner of crontab, if need). -- 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 20

[Bug 6145] New: ModBiblio double encoding items information
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '12

03 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6145 Bug #: 6145 Summary: ModBiblio double encoding items information Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: julian.maurice(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com diacritics would be double encoded when using ModBiblio multiple times on the same biblio. -- 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 9

[Bug 5873] New: Change holds_queue to work with new isssuing rules system
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '12

03 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5873 Bug #: 5873 Summary: Change holds_queue to work with new isssuing rules system Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: chris(a)bigballofwax.co.nz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 5872 Blocks: 5575 -- 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 9

[Bug 6210] New: Choose framework on Merge
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '12

03 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6210 Bug #: 6210 Summary: Choose framework on Merge Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Right now when you merge two bibs they have to be the same framework, I'd like to see the librarian be able to choose which framework to apply to the newly merged record instead of just stopping them from merging two records with different frameworks. -- 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 39

[Bug 6913] New: Improving koha-list and koha-create
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '12

02 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6913 Bug #: 6913 Summary: Improving koha-list and koha-create Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: robin(a)catalyst.net.nz ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org A place to track some patches I got sent that add some niceness to these scripts. -- 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 16

[Bug 6843] New: Renew membership from expiry date not from current date
by bugzilla-daemon＠bugs.koha-community.org 02 Feb '12

02 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6843 Bug #: 6843 Summary: Renew membership from expiry date not from current date Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: savitra.sirohi(a)osslabs.biz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Currently, upon membership renewal, due date is calcuated from current date. Some libraries want the due date to be calculated from current membership expiry date. Incude a system preference. -- 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 10

[Bug 6099] New: pagination error on GROUP BY guided reports
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '12

01 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6099 Bug #: 6099 Summary: pagination error on GROUP BY guided reports Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Reports AssignedTo: gmcharlt(a)gmail.com ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org The calculation of length of report is wrong in case of a select with GROUP BY. -- 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 16

[Bug 5924] New: Authorities search : Heading Main is defined in unimarc record.abs
by bugzilla-daemon＠bugs.koha-community.org 25 Jan '12

25 Jan '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5924 Bug #: 5924 Summary: Authorities search : Heading Main is defined in unimarc record.abs Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: MARC Authority data support AssignedTo: gmcharlt(a)gmail.com ReportedBy: chris(a)bigballofwax.co.nz QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Blocks: 5581 -- 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 10

[Bug 6790] New: C4::Serials::getroutinglist returns unnecessary variable
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '12

23 Jan '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6790 Bug #: 6790 Summary: C4::Serials::getroutinglist returns unnecessary variable Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: colin.campbell(a)ptfs-europe.com QAContact: koha-bugs(a)lists.koha-community.org The subroutine getroutinglist returns a "count" variable along with the array. Not only is this unnecessary but it causes the routine to execute an unnecessary loop and results in some ugly, unidiomatic code in the calling cgi. Refactor count away. -- 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 10