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

[Bug 15428] Different timeout preference for OPAC and staff interface
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15428 --- Comment #12 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to David Cook from comment #11) > (In reply to Marcel de Rooy from comment #10) > > (In reply to David Cook from comment #9) > > > (In reply to Katrin Fischer from comment #7) > > > > Marked bug 32385 as a dependency for this one. I think in order to have > > > > different timeouts, we need different sessions first. > > > > > > Actually, thinking about this again, you would already have different > > > sessions between the OPAC and staff interface, so long as your hostname is > > > different, which should be 99% of Koha instances... > > > > How do you calculate that 99% ? > > Perhaps I should say 99% of commercially supported Koha instances. Even then > you're right that it's a total guess based off the idea that Koha defaults > to separate hostname for OPAC and staff interface when using Debian > packages, and most commercial support vendors for Koha seem to use Debian > packages. You are right that different subdomains will create separate sessions, but I think the 99% is wrong. Koha used ports for a long time in its default setup and there are still reasons why you would want to do so. We do, with packages, use ports, for the installations we support. And it doesn't solve the problem here... different sessions, one timeout. How could you attach a different timeout to each? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 --- Comment #236 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Nick Clemens from comment #235) > (In reply to Aleisha Amohia from comment #234) > > There are lots of signoffs on these patches, can this be marked Passed QA? > > Hi Aleisha, > > It appears I was wrong in comment 187, see comment 222 > > It is a question of how the fallback should work, so we either need a DB > update, or to change the expectation for when a rule is not set It sounds like this needs a little bit more work? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33636] New: Move C4::Stats to Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33636 Bug ID: 33636 Summary: Move C4::Stats to Koha namespace Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Plan is to move code already to Koha on bug 33608. But to replace calls and remove module on this report. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 33616] New: JavaScript error in when using claims return button in checkout table
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33616 Bug ID: 33616 Summary: JavaScript error in when using claims return button in checkout table 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Set ClaimReturnedLostValue to a LOST value 2. Check out an item to a patron. 3. Click the Claim returned button within the checkout table. 4. Get spinning icon in place of the button 5. In the web developer tools console: Uncaught TypeError: value.match is not a function Looks like this is coming from includes/js-date-format.inc: 46 if ( ! value.match(/^\d{4}-\d{2}-\d{2}$/ ) ) { 47 m = m.tz(tz); 48 } -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 31818] New: Advanced editor doesn't show keyboard shortcuts
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31818 Bug ID: 31818 Summary: Advanced editor doesn't show keyboard shortcuts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using the advanced cataloguing editor, the modal showing the defined keyboard shortcuts no longer works. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 32804] New: Importing and replacing items causes inconsistency when itemnumber match and biblio match disagree
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32804 Bug ID: 32804 Summary: Importing and replacing items causes inconsistency when itemnumber match and biblio match disagree Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When 'Item processing' option during import is set to 'replace' itemnumber matches do not check any other data - so the item's biblionumber is set to the matched biblionumber, but the biblioitemnumber is not updated or checked This means that if you import a record containing an item with an itemnumber from another record you will end up with an item with mismatched biblio and biblioitem numbers This happens in consortia when multiple libraries have ordered the same biblio. Two biblios are created, later the final import with barcodes etc. is imported to replace items, and the more full bib is chosen for the biblio match, so items are half moved. To recreate: 1 - Be using the sample data in koha testing docker 2 - Stage the sample file on this report 3 - Match on KohaBiblio(999$c) / Item processing: replace 4 - Note the biblio match is "The complete novels / Austen, Jane" 5 - View the staged marc, note the barcode 39999000004090 in an item 6 - Search for that barcode 7 - You find biblio "Five novels : complete and unabridged / Gustave Flaubert" 8 - Import the file 9 - Check the db: SELECT * FROM items WHERE biblionumber != biblioitemnumber; 10 - Note the mismatch -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 --- Comment #235 from Nick Clemens <nick(a)bywatersolutions.com> --- (In reply to Aleisha Amohia from comment #234) > There are lots of signoffs on these patches, can this be marked Passed QA? Hi Aleisha, It appears I was wrong in comment 187, see comment 222 It is a question of how the fallback should work, so we either need a DB update, or to change the expectation for when a rule is not set -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15428] Different timeout preference for OPAC and staff interface
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15428 --- Comment #11 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Marcel de Rooy from comment #10) > (In reply to David Cook from comment #9) > > (In reply to Katrin Fischer from comment #7) > > > Marked bug 32385 as a dependency for this one. I think in order to have > > > different timeouts, we need different sessions first. > > > > Actually, thinking about this again, you would already have different > > sessions between the OPAC and staff interface, so long as your hostname is > > different, which should be 99% of Koha instances... > > How do you calculate that 99% ? Perhaps I should say 99% of commercially supported Koha instances. Even then you're right that it's a total guess based off the idea that Koha defaults to separate hostname for OPAC and staff interface when using Debian packages, and most commercial support vendors for Koha seem to use Debian packages. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15428] Different timeout preference for OPAC and staff interface
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15428 --- Comment #10 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to David Cook from comment #9) > (In reply to Katrin Fischer from comment #7) > > Marked bug 32385 as a dependency for this one. I think in order to have > > different timeouts, we need different sessions first. > > Actually, thinking about this again, you would already have different > sessions between the OPAC and staff interface, so long as your hostname is > different, which should be 99% of Koha instances... How do you calculate that 99% ? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15428] Different timeout preference for OPAC and staff interface
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '23

28 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15428 --- Comment #9 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Katrin Fischer from comment #7) > Marked bug 32385 as a dependency for this one. I think in order to have > different timeouts, we need different sessions first. Actually, thinking about this again, you would already have different sessions between the OPAC and staff interface, so long as your hostname is different, which should be 99% of Koha instances... -- You are receiving this mail because: You are watching all bug changes.

1 0