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

[Bug 25423] New: Methods update and empty from Koha::Objects are not class methods
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25423 Bug ID: 25423 Summary: Methods update and empty from Koha::Objects are not class methods Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org They should be called with an instance of the class, not directly as class methods: Koha::Object->new->empty vs Koha::Object->empty A trick has been done earlier to accept the second form, but as we notice the same need/problem for another method it seems better to enforce a rule and forbid such calls. An exception will be raised if the methods are called without an instantiated object. See also commit 4805b9b9dd0a95d79faf450ed1aaaec62d544ec6 Bug 25296: Make ->empty work for uninstantiated calls -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 33038] New: Add classes to patroncategorycode in patronbriefinfo for easier customization
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33038 Bug ID: 33038 Summary: Add classes to patroncategorycode in patronbriefinfo for easier customization Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 In the patronbriefinfo there is a line for patroncategorycode. It contains both the description and the code. Some libraries like to only display one or the other and that is a bit difficult to achieve currently. If we added some extra classes this would become easy. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 31432] New: Make 245 n and p subfields visible in editor by default
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31432 Bug ID: 31432 Summary: Make 245 n and p subfields visible in editor by default Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org As we now have nice mappings for these in the tables, we should make also sure hat they are visible in the cataloguing editor by default in new installations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 32642] New: Loading spinner always visible when cover image is short (OPAC)
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32642 Bug ID: 32642 Summary: Loading spinner always visible when cover image is short (OPAC) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Same as bug 28314, but for the OPAC We noticed that if the cover image is somewhat short (i.e. the height is under 80-90 px), the loading spinner indicating that the image is currently loading still appears after the image is loaded. The spinner should be hidden when the image is loaded, regardless of the image size. To test: 1. Make sure the OPACLocalCoverImages system preference is enabled 1.1. Go to Administration > Global system preferences 1.2. Search for Coverimages 1.3. Set OPACLocalCoverImages to 'Show' 1.4. Click 'Save all Enhanced content preferences' 2. Add a short local cover image to a record (I added one which is just a grey rectangle with the size printed on it, to facilitate the test) 2.1. Download the attached image 2.2. Find a record without an image 2.3. Click the 'Images' tab 2.4. Click 'Upload' 2.5. Click 'Drop files here or click to select a file' and choose the downloaded image 2.6. Click 'Process images' 3. View the record in the OPAC 3.1. From the image upload page, click on the title of the record in the page heading to access the detailed record in the staff interface 3.2. Click on 'OPAC view: Open in new window.' --> Note that the image is displayed normally, but the spinner is also displayed In the OPAC, the problem is only on the detailed record page. The search results are OK. -- You are receiving this mail because: You are watching all bug changes.

1 47

[Bug 18398] New: CHECKIN/CHECKOUT/RENEWAL don' t use AutoEmailPrimaryAddress but first valid e-mail
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18398 Bug ID: 18398 Summary: CHECKIN/CHECKOUT/RENEWAL don't use AutoEmailPrimaryAddress but first valid e-mail Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If the system preference AutoEmailPrimaryAddress is set to alternate or work this e-mail addresses should be used to send out all emails. This works for most notices, but sadly not for CHECKIN, CHECKOUT and RENEWAL notices. http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=C4/Message.pm;hb=… sub _to_address is hardcoded to use the first e-mail field that is set in the patron record. It should follow the AutoEmailPrimaryAddress setting instead. Bug 12802 fixed it, but it's a new feature. Woudl still be good to fix this especially for stable releases. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 31695] New: Type standard number is missing field ci_raw in field_config.yaml
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31695 Bug ID: 31695 Summary: Type standard number is missing field ci_raw in field_config.yaml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com In Elasticsearch fields config field_config.yaml, default type as a field 'ci_raw'. This is used for exact search. This field is missing for type standard number 'stdno'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 33088] New: background-job-progressbar.js no longer needed in batch_record_modification.tt
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33088 Bug ID: 33088 Summary: background-job-progressbar.js no longer needed in batch_record_modification.tt Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 22417 It must be removed from there, we don't need it since bug 22417 koha-tmpl/intranet-tmpl/prog/en/modules/tools/batch_record_modification.tt: [% Asset.js("js/background-job-progressbar.js") | $raw %] Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 [Bug 22417] Add a task queue -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 32716] New: update NGINX config examples
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32716 Bug ID: 32716 Summary: update NGINX config examples Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor 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 We recently encountered a situation with a Starman --> Apache --> NGINX setup where responses from /api/v1/patrons (particularly when doing pagination) could fail with an NGINX error message like this: upstream sent too big header while reading response header from upstream We determined that on the proxy server in question, the default NGINX proxy_buffer_size value of 4096 (the PAGESIZE on that server) was a bit too small for the Link header returned by the API response. Consequently, example NGINX configs in the code and the wiki should include the following: proxy_buffer_size 8k; This is related to bug 31104, but its fix of splitting up the Link headers won't be sufficient, as NGINX will drop the response if the total size of the headers is greater than proxy_buffer_size. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 33077] New: Improve ease of translating template title tags
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33077 Bug ID: 33077 Summary: Improve ease of translating template title tags Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 15395 Title tags (<title>) in templates present an especially difficult case for translators because we can't use our usual trick of wrapping text elements with <span>. This results in strings like this waiting for translation: #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/cities.tt:6 #, c-format msgid "" "%s %s Modify city %s New city %s &rsaquo; %s %s Confirm deletion of city " "&rsaquo; %s %s Cities &rsaquo; Administration &rsaquo; Koha " We can instead use the i18n template plugin introduced by Bug 15395 to wrap individual title tag elements like so: [% t("Modify city") | html %] Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15395 [Bug 15395] Internationalization: plural forms, context, and more -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 32301] New: Show correct defaultSortField in Staff Client Advanced Search
by bugzilla-daemon＠bugs.koha-community.org 23 May '23

23 May '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32301 Bug ID: 32301 Summary: Show correct defaultSortField in Staff Client Advanced Search Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: wainuiwitikapark(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 144096 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144096&action=e… Sort by option in Staff Client Advanced Search The defaultSortField system preference doesn't seem to affect the Staff Client Advanced Search, it still shows 'relevance' as the sort field whichever option you use in the syspref. However, when you submit the search it does in fact search by the value of the syspref. Need to: - In the advanced search in the staff client, display the correct default "sort by" option that is chosen in the defaultSortField system preference -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33