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

[Bug 31596] New: LDAP ACTIVE DIRECTORY with different domain suffix
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '23

18 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31596 Bug ID: 31596 Summary: LDAP ACTIVE DIRECTORY with different domain suffix Change sponsored?: --- Product: Koha Version: unspecified Hardware: Other OS: Linux Status: NEW Severity: blocker Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: hamsiah(a)interxs.com.my QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Koha version: 18.11.13.000 OS version ('uname -a'): Linux 3.16.0-6-amd64 #1 SMP Debian 3.16.57-2 (2018-07-14) x86_64 Hi, I have success connecting KOHA with ACTIVE DIRECTORY for staff. However if I want to authenticate student, login is failed due to different domain suffix. This is my working ldap-activedirectory authentication. ------------------------------------------------------------ <useldapserver>1</useldapserver> <ldapserver id="ldapserver" listenref="ldapserver"> <hostname>ldap://ldaphostname:389</hostname> <base>OU=Staf,OU=Student,OU=User,OU=uuu,DC=dc,DC=local</base> <replicate>0</replicate> <update>0</update> <auth_by_bind>1</auth_by_bind> <anonymous_bind>0</anonymous_bind> <principal_name>%s(a)uuu.edu.my</principal_name> <update_password>0</update_password> <mapping> <userid is="CN" ></userid> </mapping> </ldapserver> ------------------------------------------------------------- This config is already working smoothly. But since STUDENT's email has different suffix domain such as %s(a)student.uuu.edu.my, hence the login is failed. Is there a way to combine multiple principal_name to make this work? I have read other bugs that said multiple ldapserver is not developed. In this case, it's not multiple ldapserver cause it has the same hostname and details. Only the domain in principal_name is different. ------------------------------------------------------------- The error I got when student is logged in is: >> LDAP bind failed as kohauser MA19126: LDAP error #49: LDAP_INVALID_CREDENTIALS >> The wrong password was supplied or the SASL credentials could not be processed -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31508] New: Authorities link in new marc fields created
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '23

18 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31508 Bug ID: 31508 Summary: Authorities link in new marc fields created Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: vbovictor(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I created a new field MARC 697 – local subject I also created a “local subjectc” authority type and then linked it to field MARC 697. I imported some records and authorities with the information into the appropriate fields. I ran the misc/link_bibs_to_authorities.pl script to link the authorities with the records information. Fields 650, 100, etc. were linked normally, but field 697 was not linked. Is this a bug in the system? Is Koha not linking newly created MARCS fields? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29788] New: Make Koha::Item->safe_to_delete return a Koha::Result::Boolean object
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '23

18 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29788 Bug ID: 29788 Summary: Make Koha::Item->safe_to_delete return a Koha::Result::Boolean object Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 29746 Same as bug 29765 for the existing Koha::Item->safe_to_delete Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29746 [Bug 29746] Add a handy Koha::Result::Boolean class -- You are receiving this mail because: You are watching all bug changes.

1 39

[Bug 32064] New: Add missing test to template permission calculation
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '23

18 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32064 Bug ID: 32064 Summary: Add missing test to template permission calculation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Test Suite Assignee: dcook(a)prosentient.com.au Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Bug 31389 refactored how permissions are calculated for the templates. Today I realized there was 1 missing test to test that all subpermission authorizations are set when the top level permission is set. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 31950] New: Page section on library view is too wide / not aligned with toolbar
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '23

18 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31950 Bug ID: 31950 Summary: Page section on library view is too wide / not aligned with toolbar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff Client 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 Depends on: 31939 When viewing a library (click on the library name in admin > libraries) the page section is too wide and not aligning with the toolbar above. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31939 [Bug 31939] Add page-section to admin > libraries area -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 29955] New: Move C4::Acquisition::populate_order_with_prices to Koha::Acquisition::Order
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '23

17 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29955 Bug ID: 29955 Summary: Move C4::Acquisition::populate_order_with_prices to Koha::Acquisition::Order Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 21204 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21204 [Bug 21204] Move C4::Acquisition code to the Koha namespace [OMNIBUS] -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 18186] New: Amounts with decimal comma instead of decimal dot breaking payments
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '23

16 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18186 Bug ID: 18186 Summary: Amounts with decimal comma instead of decimal dot breaking payments Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: major 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 In our current installations running under Plack, the amounts on the pay and paycollect pages suddenly started showing with a decimal comma instead of a decimal point. This causes quite a bit of trouble, as Koha expects a . and amounts entered didn't result in the expected payments. We got several reports about payments being broken in Koha. Test plan: - Add manual invoice - View the "fines" tag - Verify that individual fees and totals display with , instead of . - Pay selected or any amount - Verify that the input field for the amount is also showing the , - Verify that paying something like 1,10 doesn't work as expected. The problem with the test plan is, that you might not see the ,. This appears only on our productions servers, but not in my development environment. We tested: - different language settings in Koha - different language settings in the browser - verified that CurrencyFormat isn't used in the code on those page - verified that all the formatting done was using the TT filter format('%.2f') In the end the problem turned out to be related to Plack. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 30739] New: Fatal errors during MARC import force status of "Importing" forever
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '23

16 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30739 Bug ID: 30739 Summary: Fatal errors during MARC import force status of "Importing" forever Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org We need to be careful when processing MARC imports. I was trying to import 1 MARC record with 1 item, and it kept getting stuck as 0% job progress and "Importing" status forever. Thanks to Bug 30738, I saw this was due to the following error: [2022/05/12 03:37:37] [WARN] DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Data too long for column 'coded_location_qualifier' at row 1 at /kohadevbox/koha/Koha/Object.pm line 170 main::__ANON__ /kohadevbox/koha/tools/manage-marc-import.pl (339) -- Either we need to fail the whole import or we need to catch the error and just report on it at the end. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 21809] New: Deleting a request does not delete its log entries
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '23

14 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21809 Bug ID: 21809 Summary: Deleting a request does not delete its log entries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Bug 20750 adds the ability for events on ILL requests to be logged in the action logs. Currently changes to request status can be logged. However, when a request is deleted, the logs associated with that request are not. Since the request ID then becomes available, the next time a request is created, it will re-use the ID of the deleted request and instantly be associated with the log entries for that request. It's not currently possible to fix this since C4::Log doesn't provide any methods to delete log entries. So I'm going to add an enhancement bug for that. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 31030] New: Add a tab in patron account for pending ILL requests (staff)
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '23

14 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31030 Bug ID: 31030 Summary: Add a tab in patron account for pending ILL requests (staff) Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de When a user has placed ILL requests the open requests are only visible in the ILL request history tab. This table can grow over time and is not a good way to quickly see any outstanding requests. We should add a new tab to the table at the bottom of the checkouts and details tabs that displays the pending/awaiting pick-up ILL requests. The status to display might need to be defined in a system preference, as not all backends do have a 'awaiting pickup' status. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2