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

[Bug 11180] IP branch attribute should accept CIDR notation and add multiple ip
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11180 --- Comment #10 from Michael Hafen <michael.hafen(a)washk12.org> --- Please check the bug in the "See also" for an alternate implementation. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 16440] New: Update report parameters
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16440 Bug ID: 16440 Summary: Update report parameters Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 51217 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51217&action=ed… Placement of report parameters on report results. Let's say you have a report that asks you for parameters. You run the report, get the results, and then you want to run the report again with different parameters. Or maybe you made a mistake and need to change it. Yes, you could back up and change things and run it again. But what if the parameters were showing over on the left of the report under the "Useful resources" section? You could see what you set, and change whatever you needed and then click update. Perhaps the row setting and update button could also be on the left of the report. Just a thought. I was able to change a parameter up in the URL, and hit update, and it worked. It was nice because I set the report to show more than 20 records, and I didn't have to repeat that step after updating. Christopher -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 31004] New: MS Teams notifications
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31004 Bug ID: 31004 Summary: MS Teams notifications Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be great to support MS Teams Chat as a delivery medium for notices. https://docs.microsoft.com/en-us/graph/api/chatmessage-post?view=graph-rest… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 24797] New: xx-XX-messages.po line numbers are not correct
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24797 Bug ID: 24797 Summary: xx-XX-messages.po line numbers are not correct Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Running ./translate update xx-XX, then looking at po/xx-XX-message.po that contains the i18n.inc t(), tx(), tnx() etc translatable strings, the line numbers in the files where the message appears in are not correct: #: koha-tmpl/intranet-tmpl/prog/en/modules/suggestion/suggestion.tt:1 #: koha-tmpl/intranet-tmpl/prog/en/modules/suggestion/suggestion.tt:2 msgctxt "purchase suggestion created by" msgid "Created by:" msgstr "" The comments say that message appears on line 1 and on line 2, but this is not correct. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 11180] IP branch attribute should accept CIDR notation and add multiple ip
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11180 --- Comment #9 from Matthias Le Gac <matthias.le-gac(a)inlibro.com> --- Yes I apply the DB. I try again and I have again the 500 error. What I do : 1) git reset 2) git pull 3) update the DB 4) apply the patch 5) update DB 6) go to koha and I have the 500 error and log : /inlibro/git/koha-master-dev-matthias/C4/Auth.pm has too many errors. Compilation failed in require at /inlibro/git/koha-master-dev-matthias/errors/500.pl line 21. BEGIN failed--compilation aborted at /inlibro/git/koha-master-dev-matthias/errors/500.pl line 21. I missed something ? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25885] New: Koha takes you straight into detail.pl when there is only one result - bad for OverDrive link
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25885 Bug ID: 25885 Summary: Koha takes you straight into detail.pl when there is only one result - bad for OverDrive link Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I would like to suggest, if you have OverDrive (or other 3rd party databases) enabled on Koha, that Koha NOT push you straight into a record (detail.pl) if there is only one "Koha" result. You end up not being able to see OverDrive results, or switch over to OverDrive when it does that. Makes the connectivity useless for those with pin-point searching skills. When you enable one of these databases, that should be all you need to disable the default Koha behavior. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 33497] New: Reduce DB calls on staff detail page
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33497 Bug ID: 33497 Summary: Reduce DB calls on staff detail page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 35747] New: Some PUT endpoints wipe data if embeds are missing from the payload
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35747 Bug ID: 35747 Summary: Some PUT endpoints wipe data if embeds are missing from the payload Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com CC: jonathan.druart+koha(a)gmail.com, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com To reproduce: 0) Enable RESTBasicAuth syspref 1) Add a new license, visit: /cgi-bin/koha/erm/licenses/add 2) Fill in mandatory fields, click "Add document" and upload a file. 3) Click 'Submit' 4) Edit the license, visit: /cgi-bin/koha/erm/licenses/edit/1 5) Pretend you're a third-party app wanting to update name and description of the license. Run the following curl: curl -u "koha:koha" -X PUT \ 'http://localhost:8081/api/v1/erm/licenses/1' \ --header 'Accept: */*' \ --header 'User-Agent: Thunder Client (https://www.thunderclient.com)' \ --header 'Content-Type: application/json' \ --data-raw '{"description":"testing","name":"testing","status":"not_yet_active","type":"consortial"}' 6) Check the license again, visit: /cgi-bin/koha/erm/licenses/edit/1 7) Notice the file you uploaded in 2) has been wiped. This PUT request is missing the documents property, so Koha will wipe all documents related to that license. Same happens for users (property 'user_roles'). Same happens if the property is sent empty. I believe this is by design, as the Koha form will always be pre-populated with any existing data thus not wiping anything unintendedly. I understand this is how PUT is supposed to work, and that this should be a PATCH instead, but we're currently not supporting PATCH endpoints (?). What is the best approach here, support PATCH or change the logic behind the PUT endpoint? Other? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34349] Validate inputs for task scheduler
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

1 0

[Bug 11180] IP branch attribute should accept CIDR notation and add multiple ip
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11180 --- Comment #8 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Phan Tung Bui from comment #6) > Attempted to apply the batch, but encountered an Internal Server Error. Did you apply the database update? It looks like they forgot to mention that step in their test plan. -- You are receiving this mail because: You are watching all bug changes.

1 0