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

[Bug 24873] New: Linking between files and manual pages should support URL parameters (label-manage.pl)
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24873 Bug ID: 24873 Summary: Linking between files and manual pages should support URL parameters (label-manage.pl) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 24848 When linking to different sections of the manual, you currently can only map the name of a file to the corresponding section in the manual. In the label creator, this proves to be a problem: /cgi-bin/koha/labels/label-manage.pl?label_element=template This should link to the templates section, while /cgi-bin/koha/labels/label-manage.pl?label_element=batch should link to the batches. It would be nice, if the mapping also supported URL parameters. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24848 [Bug 24848] Help link from label creator batch/layout/template points to card creator in manual -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 15148] Serials: Test prediction pattern starts at First issue date, not Subscription start date
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15148 --- Comment #9 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Myka, I think there might be some possible misunderstanding there: >The expected/desired behavior is for Koha to start the prediction pattern based on the subscription start date, listing the number of issues based on the subscription length value. Koha will need to calculate the issue number based on the numbering pattern and the first issue publication date. >What is presently happening is the prediction pattern is based on the first date of publication and length of subscription. This is a problem for libraries that start a new subscription in the middle of a publication, need to predict issues from the starting point of their subscription, and want to preserve the first date of publication in Koha. In Koha, it was always documented: "In ‘First issue publication date’ you want to enter the date of the issue you have in your hand, the date from which the prediction pattern will start". See: https://koha-community.org/manual/19.11/en/html/serials.html?highlight=firs… So I wonder how changing that would affect libraries already using subscriptions for a long time. At the moment, it could look something like this for a lot of libraries: Subscription start date: January 1st First issue publication: March 15th (the first issue that was tracked when starting to use the serials module) It's possible to start in the middle of a prediction pattern - if you give me an example that you are not sure about, I'd be happy to help and see if we can make it work. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13547] Item field 'Materials specified' would be useful to see in OPAC
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13547 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Item field 3 (Materials |Item field 'Materials |specified) would be useful |specified' would be useful |to see on OPAC |to see in OPAC --- Comment #8 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- This patch works as expected, but there is a little catch: For libraries, that have used this field to add information that is patron privacy relevant (like the name of someone), this change might be problematic. I have seen this happening, as the field will show up on checkout/checkin in a prominent way. (When returned, hand over to X next or something like that). Even when the materials column is hidden, it's still fully visible in the source code. Would it be possible not to pass it to the template if the column configuration is set to not display it? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24730] New: Enhancing hold cancellations
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24730 Bug ID: 24730 Summary: Enhancing hold cancellations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, patrons cannot cancel a hold that is triggered (waiting). It would be great if a patron had this ability. Staff currently do, but not the patron. Not sure why this is. It would also be great if there were options for e-mail to staff when a hold has been cancelled, and an alert on the staff home page, along with the suggestion notifications and patron update requests. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 24684] New: Adding text "Address: 1" as circulation note makes field disappear - moremember.pl
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24684 Bug ID: 24684 Summary: Adding text "Address: 1" as circulation note makes field disappear - moremember.pl Change sponsored?: --- Product: Koha Version: 18.11 Hardware: PC OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Edit patron record Add the text Address: 1 into the circulation note field Save record Circulation note is not visible. Also, in editing the record, the field is not available to edit. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 24717] New: Koha should set a referrer policy
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24717 Bug ID: 24717 Summary: Koha should set a referrer policy Change sponsored?: --- Product: Koha Version: unspecified 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: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Koha should set a referrer policy [0] to restrict what is passed in the Referer header when external resources (e.g., cover images, added content of various stripes, electronic resources, external images and CSS, etc.) are embedded or navigated to. If a referrer policy is not set, the default policy of no-referrer-when-downgrade means that (say) the full referring URL, which can include record IDs and catalog search strings, will be sent to outside webservers providing external resources provided that loading the external resource doesn't mean downgrading from HTTPS to HTTP. Better values for the referrer policy include: * strict-origin-when-cross-origin * origin-when-cross-origin Values that might break current Koha functionality that inspects the Referer header include: * no-referrer * origin * strict-origin Values that might break legitimate inspection of the Referer header by services that perform referring URL "authentication" include: * no-referrer * same-origin A referrer policy can be set in various ways: - Using a Referrer-Policy HTTP header configured at the Apache or NGINX level - Using a meta tag: <meta name="referrer" content="strict-origin-when-cross-origin"> - Using a referrerpolicy attribute in <a>, <area>, <img>, <iframe>, <script>, or <link> tags - Using a noreferrer link relation in <a>, <area>, or <link> elements. [0] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 3137] Add sys pref to collapse areas of the patron add by default
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3137 --- Comment #31 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Thx, Aleisha! Added a small follow-up, hope you agree. First and second patch could be squashed by RM, as both have same author/sign-offer. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 3137] Add sys pref to collapse areas of the patron add by default
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3137 --- Comment #30 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 100708 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=100708&action=e… Bug 3137: (QA follow-up) Switch hidden for collapsed in text Changes the text and tooltip on top of the add/edit patron screen to use collapsed instead of hidden. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 3137] Add sys pref to collapse areas of the patron add by default
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3137 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #100599|0 |1 is obsolete| | --- Comment #29 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 100707 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=100707&action=e… Bug 3137: (follow-up) Rename using 'collapse', remove syspref lettering and fix guarantor section collapsing Signed-off-by: David Nind <david(a)davidnind.com> Signed-off-by: Katrin Fischer <katrin.fischer.83(a)web.de> -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 3137] Add sys pref to collapse areas of the patron add by default
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '20

16 Mar '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3137 --- Comment #28 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 100706 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=100706&action=e… Bug 3137: HideFieldsPatronAddForm syspref This patches adds a syspref - HideFieldsAddPatronFrom - that controls which fieldsets are hidden by default in the add patron form. To test: 1) Apply patch and update database 2) Go to System preferences and confirm HideFieldsPatronAddForm has no fields selected 3) Go to add a patron / edit an existing patron (any patron category). confirm everything still works as expected. 4) Tick some of the fields in the syspref to hide them in the form 5) Go back to add patron form. 6) Confirm these fields are hidden and listed at the top of the page 7) Toggle the checkbox and confirm the hidden fields show or hide as expected. 8) Go back to the HideFieldsPatronAddForm system preference and ensure the Main address option is checked to be hidden 9) Go to the patron's details page 10) Click to edit the Contact Information section 11) Confirm the Main address option shows and the checkbox to show hidden fields is not present. 12) Confirm you can click the legend of each section to show and hide sections Sponsored-by: Catalyst IT Signed-off-by: David Nind <david(a)davidnind.com> Signed-off-by: David Nind <david(a)davidnind.com> Signed-off-by: David Nind <david(a)davidnind.com> Signed-off-by: Katrin Fischer <katrin.fischer.83(a)web.de> -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0