February 2025 - Koha-bugs - lists.koha-community.org

[Bug 25847] New: Set item to CART location when recording local use with statistical patron
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25847 Bug ID: 25847 Summary: Set item to CART location when recording local use with statistical patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When checking an item out to a statistical patron to record a local use, it would make sense to set the item to shelving location CART is the library is doing the same on checking (by setting _ALL_: CART in UpdateItemLocationOnCheckin. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 22179] New: Hide columns of all the subscriptions of a record with columns settings (id=subscriptionst) for the OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22179 Bug ID: 22179 Summary: Hide columns of all the subscriptions of a record with columns settings (id=subscriptionst) for the OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Hi, When you have multiple subscriptions from different sites for a bibliographic record, if you decide to hide some columns from the OPAC using Columns settings in the Koha's administration(id=subscriptionst), the columns will not be hidden for all the subscriptions of the record.It will be nice that when we hide a column it is hidden for all the subscriptions of the different sites. Thanks, Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 10756] Add carousel/coverflow display of new titles to the OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10756 Koha collecto <koha(a)collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koha(a)collecto.ca -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10756] Add carousel/coverflow display of new titles to the OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10756 Irene <i.tortorella(a)arts.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i.tortorella(a)arts.ac.uk -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10762] Make it possible to adjust the barcode height and width on labels
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10762 --- Comment #54 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hm, I think it might have only been the 0.08 vs 0.8 and not the datatype. But this should have a new bug number now as the original is so old. the "oldness" could also explain why we didn't spot it. We did comparisons between the previous and the new, but not from 23.11 upwards. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39059] New: Do not use "semi: false" for .vue files
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39059 Bug ID: 39059 Summary: Do not use "semi: false" for .vue files Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 38664 .vue files are kept tidy since we introduced them. And the prettier rule "semi: false;" has been used since then. In JavaScript, the use of semicolons (;) to terminate statements is optional due to a feature called Automatic Semicolon Insertion (ASI). This mechanism allows developers to write code without explicit semicolons: the JS engine automatically inserts them where necessary. Pro: omitting semicolons leads to cleaner and more readable code by reducing visual clutter. Modern tools catch potential issues arising from ASI, making explicit semicolons redundant. However, relying only on ASI can introduce subtle bugs. For instance: ``` function getValue() { return { value: 42 } } ``` A semicolon is automatically inserted after the return statement: the function returns undefined instead of the object. This happens because it is interpreted as: ``` function getValue() { return; { value: 42 } } ``` Such unintended behavior can be avoided by explicitly using semicolons. One source: https://github.com/airbnb/javascript?tab=readme-ov-file#semicolons Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38664 [Bug 38664] Tidy the whole codebase -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 10762] Make it possible to adjust the barcode height and width on labels
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10762 --- Comment #53 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Marcel de Rooy from comment #52) > (In reply to Katrin Fischer from comment #51) > > (In reply to Marcel de Rooy from comment #50) > > > This patch set added an inconsistency in the db schema: > > > > > > kohastructure > > > + `scale_width` decimal(28,6) NOT NULL DEFAULT 0.08, > > > + `scale_height` decimal(28,6) NOT NULL DEFAULT 0.01, > > > > > > dbrev > > > ADD COLUMN scale_width FLOAT default 0.8 NOT NULL AFTER font_size > > > ADD COLUMN scale_height FLOAT default 0.01 NOT NULL AFTER scale_width > > > > > > > > > Could the authors of this patch set please give follow-up on that and > > > correct? Thanks. > > > > > > PS Not completely sure but I feel that for a scale like this DECIMAL would > > > be a better choice than FLOAT. > > > > Did we not fix this? It looks familiar at least and we did a lot of > > comparisons between updated and new. > > Ah. You are right. I didnt catch the correction on master. I came from 23.11 > here. > Master is fine indeed. No wait. I cannot find a correcting dbrev on master. So structure and DBIX schema are in sync. And a new install will have DECIMAL. But if you come from an upgrade, you will still have FLOAT because of the dbrev. Am I overlooking something? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10762] Make it possible to adjust the barcode height and width on labels
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10762 --- Comment #52 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #51) > (In reply to Marcel de Rooy from comment #50) > > This patch set added an inconsistency in the db schema: > > > > kohastructure > > + `scale_width` decimal(28,6) NOT NULL DEFAULT 0.08, > > + `scale_height` decimal(28,6) NOT NULL DEFAULT 0.01, > > > > dbrev > > ADD COLUMN scale_width FLOAT default 0.8 NOT NULL AFTER font_size > > ADD COLUMN scale_height FLOAT default 0.01 NOT NULL AFTER scale_width > > > > > > Could the authors of this patch set please give follow-up on that and > > correct? Thanks. > > > > PS Not completely sure but I feel that for a scale like this DECIMAL would > > be a better choice than FLOAT. > > Did we not fix this? It looks familiar at least and we did a lot of > comparisons between updated and new. Ah. You are right. I didnt catch the correction on master. I came from 23.11 here. Master is fine indeed. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10762] Make it possible to adjust the barcode height and width on labels
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10762 --- Comment #51 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Marcel de Rooy from comment #50) > This patch set added an inconsistency in the db schema: > > kohastructure > + `scale_width` decimal(28,6) NOT NULL DEFAULT 0.08, > + `scale_height` decimal(28,6) NOT NULL DEFAULT 0.01, > > dbrev > ADD COLUMN scale_width FLOAT default 0.8 NOT NULL AFTER font_size > ADD COLUMN scale_height FLOAT default 0.01 NOT NULL AFTER scale_width > > > Could the authors of this patch set please give follow-up on that and > correct? Thanks. > > PS Not completely sure but I feel that for a scale like this DECIMAL would > be a better choice than FLOAT. Did we not fix this? It looks familiar at least and we did a lot of comparisons between updated and new. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10762] Make it possible to adjust the barcode height and width on labels
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '25

10 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10762 --- Comment #50 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- This patch set added an inconsistency in the db schema: kohastructure + `scale_width` decimal(28,6) NOT NULL DEFAULT 0.08, + `scale_height` decimal(28,6) NOT NULL DEFAULT 0.01, dbrev ADD COLUMN scale_width FLOAT default 0.8 NOT NULL AFTER font_size ADD COLUMN scale_height FLOAT default 0.01 NOT NULL AFTER scale_width Could the authors of this patch set please give follow-up on that and correct? Thanks. PS Not completely sure but I feel that for a scale like this DECIMAL would be a better choice than FLOAT. -- You are receiving this mail because: You are watching all bug changes.

1 0