December 2024 - Koha-bugs - lists.koha-community.org

[Bug 30116] New: When using UseACQFrameworkForBiblioRecords visibility settings have no effect
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30116 Bug ID: 30116 Summary: When using UseACQFrameworkForBiblioRecords visibility settings have no effect Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When UseACQFrameworkForBiblioRecords is active the form for adding a bibliographic record can be configured via the ACQ framework. But you can't hide/preset fields as removing the editor checkbox has no effect. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 31098] New: The option tohe option of "export database" and "export settings" are not available.
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31098 Bug ID: 31098 Summary: The option tohe option of "export database" and "export settings" are not available. Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: vbovictor(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I enabled in instance-conf.xml <backup_db_via_tools>1</backup_db_via_tools> <backup_conf_via_tools>1</backup_conf_via_tools> In Tools --> Export Data The option tohe option of "export database" and "export settings" are not available. Here's the information that appears: "Note: This generated file will be very large, and will be generated daily." "Unfortunately, there are no backups available." -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 8268] Koha should offer way to backup entire db
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8268 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |38763 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38763 [Bug 38763] Missing documentation of export database and export configuration options -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 --- Comment #137 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- (In reply to Mathieu Saby from comment #133) > Hi > We would be interested by testing too. Thibauld do you plan to provide a > fixed patch in next months ? Hello Mathieu, I'm glad to read about this patch. I look forward to reading your feedback. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 --- Comment #136 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- (In reply to Brendan Lawlor from comment #132) > Thanks for working on this Thibaud! A global checkout limit is important for > our consortium. > > I am happy to test this again when this error is resolved. > > The patch applies, but after running updatedatabase and dbic I get an error > when running restart_all: > > Starting Z39.50/SRU daemon for kohadev:"my" variable $self masks earlier > declaration in same scope at /kohadevbox/koha/Koha/CirculationRules.pm line > 324. > "my" variable $params masks earlier declaration in same scope at > /kohadevbox/koha/Koha/CirculationRules.pm line 324. > "state" variable @_ masks earlier declaration in same scope at > /kohadevbox/koha/Koha/CirculationRules.pm line 324. > > Also the QA script complains on a few things: > > FAIL Koha/CirculationRules.pm > FAIL pod coverage > POD coverage was greater before, try perl > -MPod::Coverage=PackageName -e666 > FAIL valid > "my" variable $self masks earlier declaration in same scope > "my" variable $params masks earlier declaration in same scope > "state" variable @_ masks earlier declaration in same scope > "my" variable $rule_name masks earlier declaration in same > scope > "my" variable $categorycode masks earlier declaration in > same scope > "my" variable $itemtype masks earlier declaration in same > scope > "my" variable $branchcode masks earlier declaration in same > scope > "my" variable $rule masks earlier declaration in same scope > "my" variable $self masks earlier declaration in same scope > "my" variable $params masks earlier declaration in same scope > "state" variable @_ masks earlier declaration in same scope > "my" variable $categorycode masks earlier declaration in > same scope > "my" variable $itemtype masks earlier declaration in same > scope > "my" variable $branchcode masks earlier declaration in same > scope > "my" variable $has_priority masks earlier declaration in > same scope > "my" variable $self masks earlier declaration in same scope > "my" variable $params masks earlier declaration in same scope > "state" variable @_ masks earlier declaration in same scope > "my" variable $branchcode masks earlier declaration in same > scope > "my" variable $categorycode masks earlier declaration in > same scope > "my" variable $itemtype masks earlier declaration in same > scope > "my" variable $rule_name masks earlier declaration in same > scope > "my" variable $has_priority masks earlier declaration in > same scope > "my" variable $rule masks earlier declaration in same scope > "my" variable $memory_cache masks earlier declaration in > same scope > syntax error > Can't use global @_ in "my" > Global symbol "$params" requires explicit package name (did > you forget to declare "my $params"?) > syntax error > Can't use global @_ in "my" > syntax error > Can't use global @_ in "my" > syntax error > Can't use global @_ in "my" > syntax error > /kohadevbox/koha/Koha/CirculationRules.pm has too many > errors. > Compilation failed in require > > WARN Koha/Schema/Result/CirculationRule.pm > WARN tidiness > The file is less tidy than before (bad/messy lines before: > 41, now: 43) > > FAIL Koha/Template/Plugin/CirculationRules.pm > FAIL pod coverage > POD coverage was greater before, try perl > -MPod::Coverage=PackageName -e666 > FAIL valid > "my" variable $self masks earlier declaration in same scope > "my" variable $params masks earlier declaration in same scope > ... > > FAIL admin/smart-rules.pl > WARN tidiness > The file is less tidy than before (bad/messy lines before: > 137, now: 154) > FAIL valid > "my" variable $self masks earlier declaration in same scope > "my" variable $params masks earlier declaration in same scope > "state" variable @_ masks earlier declaration in same scope > ... > > FAIL installer/data/mysql/atomicupdate/Bug_8137-add-column-has_priority.pl > FAIL file permissions > File must have the exec flag > > FAIL installer/data/mysql/kohastructure.sql > FAIL tinyint_has_boolean_flag > The new column circulation_rules.has_priority is using > TINYINT(1) as type but is not defined as boolean in the schema file > (Koha/Schema/Result/CirculationRule.pm), see the SQL12 coding guideline > > FAIL koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt > FAIL forbidden patterns > forbidden pattern: tab char (line 1835) > forbidden pattern: tab char (line 1837) > FAIL spelling > librairies ==> libraries > librairies ==> libraries Hello Brendan and thanks for your feedback, I miss some bracket :/ during the last rebase. It's fixed ! And I also add a follow up for QA fixes -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 --- Comment #135 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 175838 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=175838&action=e… Bug 8137: (follow-up) remove forbidden pattern and fix atomic file permission -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173608|0 |1 is obsolete| | --- Comment #134 from Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> --- Created attachment 175837 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=175837&action=e… Bug 8137: Add 'global checkout limits' table The aim here is to avoid the accumulation of checkouts possibilities through the rules of the various branches, in order to have a global quota. Test plan: 1) Apply this patch 2) Run updatedatabase script and rebuild schema, restart_all.. 3) On circulation rules page you will find a new table "Global checkout limits". 4) If you enter values, they will overwrite the existing values, creating limits for all branches combined. 5) Test it by set a "current checkouts allowed" to 2 on "standard rules section" and set a "global" maxissueqty to 1. Normally 1 is the new limit for now. 6) You can also add a "current checkouts allowed" on other branches and see that you can't accumulate checkouts (you can also delete "global" values and see that if you have 3 on a branch and 2 on other, you can perform 5 checkouts in total. 7) Note that on specific branch circulation rules page the table cannot be modified, but just shown as a reminder. If main matrix is empty on specific branch the table is hidden by default (cause if none values it's referred to standard rules). Sponsored-by: BibLibre Signed-off-by: Lisette Scheer <lisette(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38741] New: define a secondary sort order search results where primary sort field matches for several results
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38741 Bug ID: 38741 Summary: define a secondary sort order search results where primary sort field matches for several results Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: jake.bateman(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When several search results are returned whose relevance and defaultSortOrder field match (a series with many volumes with the same publication date, in my case), it would be desirable to have these results ordered by some deliberately chosen field, or by a sensible default (title alphanumeric desc would I think would be correct in all cases, potentially negating the need for an additional syspref). In my testing (with Elasticsearch), I believe the current secondary sort order to be [biblionumber asc, plus some randomness from a race condition introduced by the multiple concurrent processing threads used by the Elasticsearch reindex task, if multithreading was used]. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 30503] New: Ability to include graphic in labels
by bugzilla-daemon＠bugs.koha-community.org 20 Dec '24

20 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30503 Bug ID: 30503 Summary: Ability to include graphic in labels Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org I wonder if koha could include a graphic/image to its labels -even better in overlay form- so that a decent ex-libris label could be produced. -- You are receiving this mail because: You are watching all bug changes.

1 1