October 2014 - Koha-bugs - lists.koha-community.org

[Bug 10509] New: Using updates instead of inserts in translated mysql files
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '15

11 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10509 Bug ID: 10509 Summary: Using updates instead of inserts in translated mysql files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl CC: gmcharlt(a)gmail.com Currently, all languages in installer/data/mysql contain a few subfolders with .sql files mostly containing insert statements. There is a lot of redundancy and maintaining this construction is more work. I propose to use en (English) as a global folder, or even a separate folder global (with English just being one of the languages). The global folder should contain inserts; these sql files should be run first. The translation folder should update only the descriptions etc. This is based on a recent discussion on the dev list. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 9184] New: Ordering from staged file in acq should not offer authority records
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '15

11 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9184 Bug ID: 9184 Summary: Ordering from staged file in acq should not offer authority records Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de To reproduce: 1) Stage an authority file 2) Create a new basked in acquisitions 3) Create a new order line by selecting "From a staged file" 4) Check if the list of staged files includes the uploaded authority file -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 11038] New: Custom CSS for Staff Login like OPAC/StaffIntranet
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '15

11 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11038 Bug ID: 11038 Summary: Custom CSS for Staff Login like OPAC/StaffIntranet Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: ssammons(a)npelem.com QA Contact: testopia(a)bugs.koha-community.org Performing a simple color change to staff login screen, required file system access to create a new CSS file. As documented @ http://www.myacpl.org/koha/?p=612 , you must do that OR use the javascript hack. I am suggesting there be a simple way to add custom CSS without the need for file system access. You can use a text box with OPACUserCSS, can a that just be duplicated? As stated in bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7424 a custom store for custom-css is great, perhaps we could look at having an "upload file" buttom, or a simple file editor like WordPress uses for its theme editor, so you have file write access without being in the file system for said custom-css files? -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 9857] New: Did you mean? from authorities uses incorrect punctuation
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '15

11 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9857 Bug ID: 9857 Summary: Did you mean? from authorities uses incorrect punctuation Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: jcamins(a)cpbibliography.com Reporter: jcamins(a)cpbibliography.com The Did you mean? from authorities creates links that use = rather than : for indexes. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 12225] New: SIP renewals do not respect the "no block" flag
by bugzilla-daemon＠bugs.koha-community.org 11 Dec '15

11 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12225 Bug ID: 12225 Summary: SIP renewals do not respect the "no block" flag Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com If a renewal via SIP would produce an error due to being on reserve, or exceeding maximum renewals, Koha's SIP2 implementation will refuse to renew the item even if the "no block" flag is set to Y. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 7012] New: limit to available not limiting anymore
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7012 Bug #: 7012 Summary: limit to available not limiting anymore Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org When I limit to only available items in the OPAC it doesn't appear to be limiting anymore. -- 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 6

[Bug 11311] New: Browse selected authorities
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11311 Bug ID: 11311 Summary: Browse selected authorities Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 13068] New: New feature for DB update and sandbox
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13068 Bug ID: 13068 Summary: New feature for DB update and sandbox Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.poulain(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Most patches with a DB update cannot be applied automatically on sandboxes, because they have a conflict in updatedatabase.pl I propose to have a new directory (say dev_update), that will be used during the development process. * when you submit a patch with a db update, you developer must put the DB update part into the dev_update/ directory, NOT in updatedatabase.pl * the updatedatabase.pl, at the end of the update process, checks if there is something in the dev_update. If there is, what's here is applied. * when the patch is pushed by the Release Manager, the DB update is moved out from the dev_update directory, and included into updatedatabase.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 152

[Bug 12772] New: Overdue Notice/Status triggers tool
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '15

10 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12772 Bug ID: 12772 Summary: Overdue Notice/Status triggers tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: francois.charbonnier(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Sponsored by Halland County Library RFC (with mockup) : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement#Overdue_Noti… Description : The ergonomy of the notice triggers tool will be enhanced with two new parameters : the item type et the on-hold status. We will re-use the ergonomy and the logic of the circulation rules model. The rules will apply from the more specific to the less specific. One will be able to set up a notice trigger for a specific patron catagory and a specific item type. A default value for the item types and the patron categories will be available to generalize the rules. For a specific notice level, we will prevent the user to set up different delay for the same combination of options. For each rule created, the new "on-hold" option will specify that the rule applies for the « on hold » items only. These new features will allow for example : to set up different rules for free of charge items or items with rental fee (since we can set up rules per item types). to set up different rules for available item or "on hold" item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 57

[Bug 11051] New: Performance of opac-search
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '15

09 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11051 Bug ID: 11051 Summary: Performance of opac-search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: robin(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org I did a profile of opac-search and am going to make a few improvements to it. You can see the results here: http://debian.koha-community.org/~robin/opac-search/ This was run on a production 3.12.2 system, with 10 branches, with a database server on a different machine. This means that database latency is more visible. -- You are receiving this mail because: You are watching all bug changes.

1 45