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

[Bug 4437] acq.js uses XMLHttpRequest() directly; should use jQuery
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4437 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 4437] acq.js uses XMLHttpRequest() directly; should use jQuery
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4437 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |ASSIGNED Assignee|hugh(a)davenport.net.nz |koha-bugs(a)lists.koha-commun | |ity.org --- Comment #15 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- acq.js appears to be the non-external library that still uses XMLHttpRequest: koha-tmpl/intranet-tmpl/prog/js/acq.js In: totalExceedsBudget() budgetExceedsParent() checkBudgetParent() The others are: koha-tmpl/opac-tmpl/bootstrap/js/Gettext.js koha-tmpl/opac-tmpl/bootstrap/lib/greybox/GreyBox_v5_5/greybox_source/base/AJS.js koha-tmpl/opac-tmpl/bootstrap/lib/jquery/jquery-3.6.0.min.js koha-tmpl/opac-tmpl/lib/verovio/000_acoustic_grand_piano.js koha-tmpl/opac-tmpl/lib/verovio/verovio-toolkit.js I am resetting assignee since this hasn't had an update in several years. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 4373] Placing and processing items simultaneously causes multiple issues
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4373 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Placing and Processing |Placing and processing |Items Simultaneously causes |items simultaneously causes |multiple issues |multiple issues --- Comment #4 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- The mentioned bug 4201 has been fixed since. I haven't seen newer reports on this, but it could still be an issue for bigger consortiums I guess. Could anyone weigh in here with their experience maybe? -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 4363] Support the patron internet resources field in Sip2
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4363 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle(a)bywatersolutions.com Assignee|colin.campbell@ptfs-europe. |martin.renvoize@ptfs-europe |com |.com --- Comment #4 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Martin or Kyle, could you have a look at this old bug from Colin please? -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 4330] Copyright statements out of date
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4330 --- Comment #49 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Is this still something we shoudl/could fix? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4304] autoBarcode should increment from user defined value
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4304 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED Summary|autoBarcode should |autoBarcode should |increment from user defind |increment from user defined |value |value --- Comment #3 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Katrin Fischer from comment #2) > The easiest way around this right now is to create the first item with your > 'start number' and then Koha will count from that as always the highest > existing barcode is used. I wonder if this is not easier than having to > maintain a different setting? I am closing this WONTFIX as the existing workaround seems a good option. Please reopen if you disagree. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 4274] Optionally allow sending cart without requiring login
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4274 --- Comment #16 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I am not sure if this is a feature that we should implement given the possible security/spam implications. A bot or human misusing the feature could get the library's email address blacklisted for example. Would someone else support a CLOSED WONTFIX? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug. You are the QA Contact for the bug.

1 0

[Bug 4264] Categories/Groups for authorized value categories
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4264 --- Comment #4 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- This might still be a pretty handy optional feature. For example we have several Authorised value categories that belong to the ERM module now and this is repeatedly stated in the description, but it would be so much nicer to have a separate sortable/searchable column for these. -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 4234] Automatic transfer shouldn't take precedence over a hold transit
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4234 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I have done tests with 2 different use cases: * Item from A is checked out to user in B * Hold is placed with pickup in C * Items return home * Item is checked in at B * Transfer is to library C for hold pickup Similar as above, but the item is not checked out, when returned in B: * Transfer is to library C for hold pickup And then to verify that the holds behavior took precedence: * Item from A (without holds) is checked in at B * Item is sent to return to A I assume that this is fixed, please reopen if I missed something! -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 4230] New icon for move to lowest priority on holds
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '23

08 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4230 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|new icon for move to lowest |New icon for move to lowest |priority on holds |priority on holds Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #5 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Katrin Fischer from comment #4) > This might be resolved by bug 16421 We have since changed all the icons for changing the holds priorities on bug 29057. Marking as RESOLVED DUPLICATE. *** This bug has been marked as a duplicate of bug 29057 *** -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0