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

[Bug 29061] New: max_holds rule not saving a value of Unlimited
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29061 Bug ID: 29061 Summary: max_holds rule not saving a value of Unlimited Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 To recreate: - Set your Default checkout, hold and return policy value for Maximum total holds allowed (count) to 1 - find a patron, confirm you can only place 1 hold for this patron before getting a "too many holds" error - create a Checkout, hold policy by patron category for your patron's category, with a Total Holds value of Unlimited - confirm you still get a "too many holds" error, even though your circ rules say your holds should be unlimited We don't save a max_holds rule with a blank value for the patron category, so Koha ends up falling back to the more restrictive default. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 15349] Problem with email pattern check on forms
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15349 --- Comment #10 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- (In reply to Katrin Fischer from comment #9) > (In reply to Tomás Cohen Arazi from comment #8) > > Bug 28870 solves the backend email validation issues, and accepts formatted > > addresses. The remaining problems are related to the jquery library we use: > > > > https://jqueryvalidation.org/email-method/ > > > > one path for solving it, could be trying to extract the regex from > > Email::Address and override the one in the jQuery library with it. Another > > option could be to add a route for email validation so an async check is > > done. > > I missed this comment, so it looks like they should not cause issues and > it's only a matter of the validation now, right? You mean validating in the form. Right? I'm that case, that's what I think -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15349] Problem with email pattern check on forms
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15349 --- Comment #9 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Tomás Cohen Arazi from comment #8) > Bug 28870 solves the backend email validation issues, and accepts formatted > addresses. The remaining problems are related to the jquery library we use: > > https://jqueryvalidation.org/email-method/ > > one path for solving it, could be trying to extract the regex from > Email::Address and override the one in the jQuery library with it. Another > option could be to add a route for email validation so an async check is > done. I missed this comment, so it looks like they should not cause issues and it's only a matter of the validation now, right? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15048] Genre/Form (655) searches fail on searches with $x 'General subdivision' subfield values
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15048 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Patch doesn't apply --- Comment #19 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Can we please have a rebase? Apply? [(y)es, (n)o, (i)nteractive] y Applying: Bug 15048 - subject/genre (650/655) searches fail on searches with $x 'General subdivision' subfield values Applying: Bug 15048: Index all possible searched subfields for index-term-genre Using index info to reconstruct a base tree... M etc/zebradb/marc_defs/marc21/biblios/biblio-koha-indexdefs.xml M etc/zebradb/marc_defs/marc21/biblios/biblio-zebra-indexdefs.xsl Falling back to patching base and 3-way merge... Auto-merging etc/zebradb/marc_defs/marc21/biblios/biblio-zebra-indexdefs.xsl CONFLICT (content): Merge conflict in etc/zebradb/marc_defs/marc21/biblios/biblio-zebra-indexdefs.xsl Auto-merging etc/zebradb/marc_defs/marc21/biblios/biblio-koha-indexdefs.xml CONFLICT (content): Merge conflict in etc/zebradb/marc_defs/marc21/biblios/biblio-koha-indexdefs.xml error: Failed to merge in the changes. Patch failed at 0001 Bug 15048: Index all possible searched subfields for index-term-genre hint: Use 'git am --show-current-patch=diff' to see the failed patch When you have resolved this problem run "git bz apply --continue". If you would prefer to skip this patch, instead run "git bz apply --skip". To restore the original branch and stop patching run "git bz apply --abort". Patch left in /tmp/Bug-15048-Index-all-possible-searched-subfields-fo-UEZYrg.patch -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8214] Create a bound with function
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8214 --- Comment #12 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think it would be more like EasyAnalytics (actually that could be used as a bound with). There would only be one physical thing, so only one barcode to check out.. and ideally you'd see it's gone on all the records/titles it contains. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8214] Create a bound with function
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8214 --- Comment #11 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- So many similar but different functions.. how would this relate too the recently pushed bundles and item groups bugs. Almost sounds like an automatic multi-checkout? I.e if you checkout an item that's bound with another you automatically get the other item checked out too. Spitballing, I have no idea how this works really -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8214] Create a bound with function
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8214 --- Comment #10 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Martin Renvoize from comment #9) > (In reply to Katrin Fischer from comment #8) > > There is a difference: > > > > "Bound withs" are on item level. The library might have something twice, but > > once it's bound with something else and once it's on its own. That can > > happen especially in libraries with old and rare books. > > > > bug 11175 is talking about showing relationships between bibliographic > > records, so it's on a different level. For example in Germany for a multi > > volume work you'd usually have a 'set record' that represents the whole work > > and then a record for each volume. They are tied together using 7xx and 8xx. > > The goal of bug 11175 would then be to show the volume records on the set > > record. > > Oh, I wasn't thinking of this at the item level.. so does this really need > the Holdings level MARC support before it can be implemented then? i.e. > should it depend on bug 20447 No, I think the holdings are more for grouping several items or holdings of one record. A bound with would be items from different records, I believe this is yet another use case. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26347] New: Wrong publication pattern locale on months
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26347 Bug ID: 26347 Summary: Wrong publication pattern locale on months Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Configuring publication patterns with locale ca-ES we have discovered that months are wrong translated january = gener and now it is translating = de gener februry = febrer and now it is translating = febrer march.....etc locale should use just months not full name -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 13559] Forced item level hold should be highlighted on return
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13559 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |31169 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31169 [Bug 31169] [OMNIBUS] Problems with forced holds (AllowHoldPolicyOverride) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 28987] New: Record search by date broken in label management
by bugzilla-daemon＠bugs.koha-community.org 16 Jul '22

16 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28987 Bug ID: 28987 Summary: Record search by date broken in label management Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 24735 If you go to Tools -> Label creator -> New batch -> Add items you'll trigger a popup window with a search form. Searching by date returns no results. I think Bug 24735, "Remove QueryParser-related code" is to blame. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24735 [Bug 24735] Remove QueryParser-related code -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4