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

[Bug 8742] New: Example uses perl 5.8 in Makefile.PL
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8742 Priority: P5 - low Change sponsored?: --- Bug ID: 8742 Assignee: gmcharlt(a)gmail.com Summary: Example uses perl 5.8 in Makefile.PL Severity: trivial Classification: Unclassified OS: All Reporter: mtompset(a)hotmail.com Hardware: All Status: NEW Version: unspecified Component: Installation and upgrade (command-line installer) Product: Koha When running a tarball or git install, the following is printed at the end of the process: --- BEGIN SNIPPET --- To change any configuration setting, please run perl Makefile.PL again. To override one of the target directories, you can do so on the command line like this: perl Makefile.PL PERL_MODULE_DIR=/usr/share/perl/5.8 You can also set different default values for parameters or override directory locations by using environment variables. --- END SNIPPET --- Seeing as 5.10 is the minimum version for Perl as of 3.6.x, this should be reflected. Test -------- $ perl Makefile.PL # hold down the enter key to accept all the defaults # scroll back up, if necessary, to see it does say 5.8 as above. Apply patch retest. The results should reflect an appropriate version. If there is /usr/share/perl/ in @INC, the first match is used. Otherwise, /usr/share/perl/5.10 is used (since the text does say LIKE this, and not EXACTLY this). Patch to follow shortly. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 8812] New: Staff Client: Patron search should display branch name instead of branch code in results table
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8812 Priority: P5 - low Change sponsored?: --- Bug ID: 8812 CC: gmcharlt(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Staff Client: Patron search should display branch name instead of branch code in results table Severity: normal Classification: Unclassified OS: All Reporter: veron(a)veron.ch Hardware: All Status: NEW Version: master Component: Staff Client Product: Koha Result list in patron search should display branchname instead of branchcode. Similar reason as with Bug 8810: The name of the branch can change and the original meaning of the branchcode could be lost (that happened to us and we need a solution asap). Since branchcode is used as database key as well it would be very difficult to change it in all the tables. Patch follows. Marc -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 8831] New: gstrate should say 'Tax rate'
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8831 Priority: P5 - low Change sponsored?: --- Bug ID: 8831 Assignee: nengard(a)gmail.com Summary: gstrate should say 'Tax rate' Severity: minor Classification: Unclassified OS: All Reporter: nengard(a)gmail.com URL: cgi-bin/koha/acqui/neworderempty.pl?booksellerid=1&bas ketno=34 Hardware: All Status: ASSIGNED Version: master Component: Acquisitions Product: Koha Created attachment 12533 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=12533&action=edit gstrate GST was replaced with Tax everywhere, so this patch fixes the one last occurrence of that. Patch coming. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 8741] New: crontab.example missing username, fails in some systems
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8741 Priority: P5 - low Change sponsored?: --- Bug ID: 8741 Assignee: gmcharlt(a)gmail.com Summary: crontab.example missing username, fails in some systems Severity: enhancement Classification: Unclassified OS: All Reporter: tomascohen(a)gmail.com Hardware: All Status: NEW Version: master Component: Command-line Utilities Product: Koha The default Ubuntu cron daemon needs the user that will be used to run the command defined for each line. It is a standard nowadays and will not break other OS's, but will address issues from some users. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 8610] New: Normalize records imported from Z39.50 servers to prevent Zebra search problems.
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8610 Priority: P5 - low Change sponsored?: --- Bug ID: 8610 CC: m.de.rooy(a)rijksmuseum.nl Assignee: gmcharlt(a)gmail.com Summary: Normalize records imported from Z39.50 servers to prevent Zebra search problems. Severity: enhancement Classification: Unclassified OS: All Reporter: fcapovilla(a)live.ca Hardware: All Status: NEW Version: rel_3_8 Component: Z39.50 / SRU / OpenSearch Servers Product: Koha Created attachment 11512 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=11512&action=edit Normalize records imported from Z39.50 servers. Records with separated diacritics might not show up in Zebra searches if the search terms use accented characters, because typed UTF-8 accented characters normally use combined diacritics. Some Z39.50 server may use the MARC-8 encoding, which uses separated diacritics. By forcing a normalization, all imported records will have combined diacritics. Example serveur using separated diacritics (MARC-21): http://www.collectionscanada.gc.ca/amicus/006002-400-f.html Hostname: amicus.collectionscanada.gc.ca Port: 210 Database: BN Syntax: MARC21/USMARC Encoding: MARC-8 -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 8811] New: can't run report after saving
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8811 Priority: P5 - low Change sponsored?: --- Bug ID: 8811 Assignee: gmcharlt(a)gmail.com Summary: can't run report after saving Severity: major Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Reports Product: Koha Created attachment 12472 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=12472&action=edit run report after saving After saving a new report, the link to run this report is gone, but the button remains (which is good), however if you click the button to run report it brings you to a blank screen that just has the 'New' button on it. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 8829] New: can't import authorities
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8829 Priority: P5 - low Change sponsored?: --- Bug ID: 8829 CC: m.de.rooy(a)rijksmuseum.nl Assignee: gmcharlt(a)gmail.com Summary: can't import authorities Severity: critical Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: master Component: Cataloging Product: Koha I cannot import authority files via the staff client, but can import bib records. ---------- FROM IRC: [10:45] <nengard> jcamins, i'm testing the authority import in master and it's frozen [10:45] <nengard> and the list of processes on my server doesn't show it running anymore [10:45] <nengard> it did work the first time I tested it … last week I think [10:45] <jcamins> nengard: your javascript was out of date. Go to the manage MARC import screen. [10:45] <nengard> it's not there [10:46] <jcamins> And it's not running? [10:46] <jcamins> Weird. [10:46] <nengard> but the one I did on the 20th is there [10:46] <nengard> It is stuck at processing [10:46] <nengard> on the browser [10:46] <nengard> and the process is not running anymore on the server [10:46] <nengard> what has changed for me since the 20th is that I upgraded to mountain lion … but don't think that's it [10:46] <jcamins> When I imported authorities yesterday it worked. [10:47] <nengard> hmmm [10:47] <jcamins> Actually, it was two days ago. [10:47] <jcamins> Monday. [10:47] * jcamins can eventually figure out what the calendar says. [10:48] <nengard> heh [10:48] <nengard> well i did pull down new updates to master yesterday [10:48] <nengard> so maybe something broke it yesterday [10:48] <jcamins> Right, but I didn't think there was anything new since Monday. [10:49] <nengard> here's what happens … [10:49] <nengard> 1. browse for file [10:49] <nengard> 2. change type to authority [10:49] <nengard> 3. don't look for matches [10:49] <nengard> 4. click button [10:49] <nengard> server says : www-data 1915 0.0 3.3 109904 24300 ? R 10:43 0:00 /usr/bin/perl /home/nengard/kohaclone/tools/background-job-progress.pl [10:49] <nengard> 1 minute later that line is gone from the processes, but the browser still says it's processing [10:50] <nengard> same process with a bib record finishes in no time -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 8370] New: Default checkout, hold and return policy for all library => wrong term
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8370 Priority: P2 Change sponsored?: --- Bug ID: 8370 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, nengard(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Blocks: 8362 Summary: Default checkout, hold and return policy for all library => wrong term Severity: normal Classification: Unclassified OS: All Reporter: paul.poulain(a)biblibre.com Hardware: All Status: NEW Version: master Component: Circulation Product: Koha The string "Default checkout, hold and return policy for all library" that appear in issuingrules when you're on "All" library is wrong. It's related to the rule that is applied by default if there is no library-level rule. Same problem with "Checkout limit by patron category for all libraries" and "Holds policy by itemtype for all libraries" => they refer to the behaviour if no library-level rule is set -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 8738] New: DateTime object being compared to a date string in circulation
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8738 Priority: P5 - low Change sponsored?: Sponsored Bug ID: 8738 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: DateTime object being compared to a date string in circulation Severity: enhancement Classification: Unclassified OS: All Reporter: mjr(a)software.coop URL: http://intranet/cgi-bin/koha/circ/circulation.pl Hardware: All Status: NEW Version: rel_3_8 Component: Circulation Product: Koha A DateTime object can only be compared to another DateTime object (DateTime=HASH(0x54110d8), 0). at /home/coop/koha/unstable/src/circ/circulation.pl line 346 at /usr/lib/perl5/DateTime.pm line 1801 DateTime::_compare('DateTime=HASH(0x54110d8)', 0, 0) called at /usr/lib/perl5/DateTime.pm line 1780 DateTime::compare('DateTime=HASH(0x54110d8)', 0) called at /usr/lib/perl5/DateTime.pm line 1762 DateTime::_compare_overload('DateTime=HASH(0x54110d8)', 0, '') called at /home/coop/koha/unstable/src/circ/circulation.pl line 346 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 8860] New: can't merge if you don't have fast cataloging permissions
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '13

21 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8860 Priority: P5 - low Change sponsored?: --- Bug ID: 8860 CC: m.de.rooy(a)rijksmuseum.nl Assignee: gmcharlt(a)gmail.com Summary: can't merge if you don't have fast cataloging permissions Severity: critical Classification: Unclassified OS: All Reporter: nengard(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Cataloging Product: Koha A couple of libraries so far have reported that they are unable to merge records through the Lists feature. They can create a list, add records to it, and select two records to merge without a problem, but when they get to the Merge Reference screen and click Next, they get logged out of koha and put back to the Login screen with an error. When logging back in, they get the error message "an unexpected number of records was provided for merging. Currently only two records at a time can be merged." They have only selected two records for merging but they still receive this message. We have tested this in 3.8 and master and in Chrome, Firefox and IE. It actually works in IE, but doesn't in FF or Chrome (the browsers we tell people to use for the staff client). It turns out this happens to users who have edit catalog and edit items permission but not fast cataloging permissions. You shouldn't need fast cataloging permissions to merge items, all it should require is edit catalog and edit items. Also, the error message is misleading since it's a permissions issue and not an issue with the number of items you're merging. -- You are receiving this mail because: You are watching all bug changes.

1 11