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

[Bug 35718] New: Remove ES6 warnings from JavaScript system preferences
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35718 Bug ID: 35718 Summary: Remove ES6 warnings from JavaScript system preferences Change sponsored?: --- Product: Koha Version: master 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using any of the UserJS system preferences there are warnings if you use any ES6 features/syntax. To recreate: 1. Add some JS like this to any of the UserJS system preferences: $(document).ready( function() { let something = 1; const another_thing = 2; let an_arrow_function = (a, b) => a + b; console.log( an_arrow_function(something, another_thing) ); }); 2. Notice the icons and warnings to the left of the line numbers: let is available in ES6 const is available in ES6 arrow_function_syntax is available in ES6 ES6 syntax is pretty commonly used now, I don't think we need those warnings. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 36004] New: Typo in "Your concern was successfully submitted" text
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36004 Bug ID: 36004 Summary: Typo in "Your concern was successfully submitted" text Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Turn on the syspref 'OpacCatalogConcerns' 2. Go to view a record in the OPAC and click on "Report a concern" in the column located on the right-hand side. 3. Fill out the title on the form and leave everything else the same. Click on submit and notice that the message on the screen says "Your concern was sucessfully submitted." Successfully is spelled incorrectly. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 36005] New: Typo in "Your concern was successfully submitted" Staff Intranet text
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36005 Bug ID: 36005 Summary: Typo in "Your concern was successfully submitted" Staff Intranet text Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1. Turn on the syspref 'CatalogConcerns' 2. Go to view a record in the staff intranet and click on "New catalog concern" which is located in the "+New" dropdown. 3. Fill out the title on the form and leave everything else the same. Click on submit and notice that the message on the screen says "Your concern was sucessfully submitted." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 36070] New: "Place recall" hover not consistent
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36070 Bug ID: 36070 Summary: "Place recall" hover not consistent Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 35538] New: List of libraries on OPAC self registration form should sort by branchname rather than branchcode
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35538 Bug ID: 35538 Summary: List of libraries on OPAC self registration form should sort by branchname rather than branchcode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The dropdown list of libraries on the OPAC self registration form is ordered by branchcode. It would be great if this list was ordered by branchname as it is for the Libraries search filter. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 35924] New: The 'checkin slip' button should not be available for patrons whose privacy is set to never
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35924 Bug ID: 35924 Summary: The 'checkin slip' button should not be available for patrons whose privacy is set to never Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com If a patron anonymizes their checkins, the checkin slip cannot retrieve any info to print the checkin slip. We should not show the button in this scenario -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 36101] New: Deleting an item removes the itemnumber from old_reserves when it should not
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36101 Bug ID: 36101 Summary: Deleting an item removes the itemnumber from old_reserves when it should not Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: lmstrand(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Unless there's a good reason for this data loss, the itemnumber should be preserved in old_reserves after deleting an item. To reproduce: 1.1 Create an item level hold or a hold on a biblio with just one item for it 1.2 Cancel the hold 1.3 Check old_reserves, the itemnumber for the reserve is present 1.4 Delete the item linked to the reserve 1.5 Check old_reserves again, the itemnumber is now NULL or: 2.1 Create a hold for a biblio with multiple items 2.2 checkin one of the items linked to the biblio the reserve was made for and confirm the hold 2.3 Cancel the hold 2.3 Check old_reserves, the itemnumber for the reserve is present 2.4 Delete the item linked to the reserve 2.5 Check old_reserves again, the itemnumber is now NULL The constraint that does the deletion from old_reserves-table when an item is deleted: CONSTRAINT `old_reserves_ibfk_3` FOREIGN KEY (`itemnumber`) REFERENCES `items` (`itemnumber`) ON DELETE SET NULL ON UPDATE SET NULL This should be removed. After removal the itemnumber does not get deleted from the old_Reserves table when the item is deleted. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 32029] New: Automatic item modifications by age missing biblio table
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32029 Bug ID: 32029 Summary: Automatic item modifications by age missing biblio table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In automatic item modifications by age missing, conditions can be on columns of tables items or biblioitems. Table biblio is missing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 36170] New: Wrong warning in memberentry
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36170 Bug ID: 36170 Summary: Wrong warning in memberentry Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal 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 - warn "Patron creation failed! - $@"; # Maybe we must die instead of just warn $@ is never set here, we need $_ (inside a try-catch) -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 31427] New: Automatic renewal too_many error is confusing in notices
by bugzilla-daemon＠bugs.koha-community.org 19 Mar '24

19 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31427 Bug ID: 31427 Summary: Automatic renewal too_many error is confusing in notices 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I am not sure if this error, too_many, should be removed or just handled differently. It is confusing for patrons, here is why: Day 1, a patron gets an email telling them an item has been successfully renewed. It is auto renewal 5/5, the item will no longer renew. Day 2: The next a patron receives a new auto renewal message telling them the same item, from yesterday, cannot be renewed. Patrons are confused. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 69