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

[Bug 39646] New: Send overdue notice to guarantor when guarantee has no email
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39646 Bug ID: 39646 Summary: Send overdue notice to guarantor when guarantee has no email Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: william.lavoie(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org If a guarantee does not have an email address registered to their account, then the script overdue_notices.pl doesn't send an email to their guarantors either. Additionally, if an email is sent, the letter should not be printed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 15834] New: Options to supress e-mail generated by AutoEmailOpacUser
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15834 Bug ID: 15834 Summary: Options to supress e-mail generated by AutoEmailOpacUser Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com Would love to see a selection when creating a new account to suppress the welcome e-mail generated by AutoEmailOpacUser. Sometimes, like when creating accounts for ILL, you don't want to send the info. It would also be great if there were a preference where you could choose patron groups to not send this e-mail to. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 34994] New: Consider translations in updatedatabase
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34994 Bug ID: 34994 Summary: Consider translations in updatedatabase Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr I wanted to open the discussion on this subject. Currently, when we insert things in the database using db_revs or updatedatabase, the strings are inserted in English. For a lot of things, like database structure changes and that type of stuff, it's fine. But for new letters, authorized values or additional content, it inserts in English no matter what the language of the installation is. That means that when we update Koha, we have to go in and translate all of those new things in the interface. We already translate the strings for new Koha installations through the translation of yaml files. I was wondering if it was somehow possible to use the yaml files and their translations to insert the new values? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 36737] New: Use translations in db_rev
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36737 Bug ID: 36737 Summary: Use translations in db_rev Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com When something is inserted in the db through a db_rev, it is inserted in English. For most things, it doesn't really matter. But in the case of authorized values and letters in particular, this is problematic in installations that are not in English. >From what I understand, people who have non-English installations correct these in an ad hoc fashion, sometimes through SQL UPDATE statements and other times manually in the interface. Since all the terms used in db_revs are also included in the installer yaml files, and those are translated, we should find a way to reuse the translations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 38365] Add Content-Security-Policy HTTP header to HTML responses
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38365 --- Comment #236 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Jonathan Druart from comment #234) > (In reply to Jonathan Druart from comment #232) > > 3. Is there a good reason to use Plack::Test in > > t/db_dependent/Koha/Middleware/ContentSecurityPolicy.t? IMO we should have a > > Cypress test. > > Oh, it won't work with Cypress because you want to mock the config. Interesting. See also bug 41961. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38365] Add Content-Security-Policy HTTP header to HTML responses
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38365 --- Comment #235 from Lari Taskula <lari.taskula(a)hypernova.fi> --- Thanks Jonathan for taking a look at this :) (In reply to Jonathan Druart from comment #234) > (In reply to Jonathan Druart from comment #232) > > 3. Is there a good reason to use Plack::Test in > > t/db_dependent/Koha/Middleware/ContentSecurityPolicy.t? IMO we should have a > > Cypress test. > > Oh, it won't work with Cypress because you want to mock the config. I was initially looking for a way to test the feature without actually enabling the CSP middleware outside of this test. The initial plan was to enable CSP for OPAC alone. As this Bug evolved we are now activating the middleware in both interfaces (although not yet enabling the feature of course). As for why not cypress tests in particular, I have simply not written them before and am not aware of its limitations. As long as we can test this with different configurations coming namely from KOHA_CONF, I'm not demanding to use any particular testing framework. I can see cypress tests being very useful for verifying the absence of CSP errors on various different pages in Koha. > 13. I didn't manage to see something in the violation logs. I enabled dom.reporting.* in about:config, what else is needed? Is that Firefox? Firefox only supports report-uri (not report-to + Reporting-Endpoints response header) so first make sure that report-uri is defined in your KOHA_CONF. Also https should be enabled for the browsers to become willing to send reports. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14962] Temp Shelving Location / On Display Module
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14962 Jake Deery <jake.deery(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |41976 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41976 [Bug 41976] [Vue] LinkWrapper.vue isn't scoped properly -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41973] New: Remove C4::Context from Koha::Config::SysPref
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41973 Bug ID: 41973 Summary: Remove C4::Context from Koha::Config::SysPref Initiative type: --- Sponsorship --- status: 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: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 41891 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41891 [Bug 41891] Move C4::Context->preferences to a separate package -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 38365] Add Content-Security-Policy HTTP header to HTML responses
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38365 --- Comment #234 from Jonathan Druart <jonathan.druart(a)gmail.com> --- (In reply to Jonathan Druart from comment #232) > 3. Is there a good reason to use Plack::Test in > t/db_dependent/Koha/Middleware/ContentSecurityPolicy.t? IMO we should have a > Cypress test. Oh, it won't work with Cypress because you want to mock the config. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38365] Add Content-Security-Policy HTTP header to HTML responses
by bugzilla-daemon＠bugs.koha-community.org 03 Mar '26

03 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38365 --- Comment #233 from Jonathan Druart <jonathan.druart(a)gmail.com> --- Created attachment 194374 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=194374&action=e… Bug 38365: Fix new_line_at_the_end_of_file QA failure [FAIL] api/v1/swagger/definitions/csp_report.yaml FAIL new_line_at_the_end_of_file Missing new line at the end of file, make sure your editor correctly reads .editorconfig ('insert_final_newline = true'). See bug 40541. -- You are receiving this mail because: You are watching all bug changes.

1 0