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

[Bug 14099] RESERVESLIP shows incorrect information in items.holdingbranch on first scan
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14099 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE CC| |jonathan.druart(a)bugs.koha-c | |ommunity.org --- Comment #4 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- I think it has been fixed by bug 24612, can you confirm? *** This bug has been marked as a duplicate of bug 24612 *** -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 5428] Back to results after deleting a record
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5428 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off --- Comment #9 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- This now works as described so I'm signing off.. However, I wonder if it might be nicer reverse the logic and redirect back to the search results by default instead of redirected to advanced search and displaying a button to get to the prior results... -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 5428] Back to results after deleting a record
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5428 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #107866|0 |1 is obsolete| | --- Comment #8 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- Created attachment 107868 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=107868&action=e… Bug 5428: Jump back to the search result after deleting a record This patch adds the ability to jump back to the search result after a record has been deleted. Also it keeps the "browser" when all items are deleted from a bibliographic record Test plan: - Start a new search - Select a record with items - Delete all the items => You still see the browser - Delete the record => You are back to the adv search form but we new link "Go back to the results" is present at the top of the page Limitation: As we delete the record we do not longer know the offset, we are back to the first page of the result list Signed-off-by: Martin Renvoize <martin.renvoize(a)ptfs-europe.com> -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 5428] Back to results after deleting a record
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5428 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #107753|0 |1 is obsolete| | --- Comment #7 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- Created attachment 107866 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=107866&action=e… Bug 5428: Jump back to the search result after deleting a record This patch adds the ability to jump back to the search result after a record has been deleted. Also it keeps the "browser" when all items are deleted from a bibliographic record Test plan: - Start a new search - Select a record with items - Delete all the items => You still see the browser - Delete the record => You are back to the adv search form but we new link "Go back to the results" is present at the top of the page Limitation: As we delete the record we do not longer know the offset, we are back to the first page of the result list -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 5428] Back to results after deleting a record
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5428 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 26140] New: Move .tt files to a tt/ template root directory
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26140 Bug ID: 26140 Summary: Move .tt files to a tt/ template root directory Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, Koha deploys Template::Toolkit *.tt files to /usr/share/koha/intranet/htdocs and /usr/share/koha/opac/htdocs. Those are the directories (ie DocumentRoot) from which Apache serves static files. If you type in http://<mykoha>/opac-tmpl/bootstrap/en/modules/opac-main.tt, Apache will serve you the template file. It's not really a security issue per se, but it's completely unnecessary. It would be better to store templates somewhere like /usr/share/koha/tt/intranet and /usr/share/koha/tt/opac. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 25361] New: Support X-Forwarded-* headers
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25361 Bug ID: 25361 Summary: Support X-Forwarded-* headers 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Thanks to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23068 we are able to use X-Forwarded-For to pass the client IP via a reverse proxy. Now it would be useful to use other X-Forwarded-* headers like X-Forwarded-Proto in the same way. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 26155] New: Hacked by in sanz
by bugzilla-daemon＠bugs.koha-community.org 06 Aug '20

06 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26155 Bug ID: 26155 Summary: Hacked by in sanz Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: ganssanz9(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 107862 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=107862&action=e… Yuy Wlawkawka -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 11469] Publication date range assumes that years must always be 4 digits
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '20

05 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11469 --- Comment #4 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- > The adv search did not allow publication years prior to 1000 > We are now ready for year 10000 We might be - but MARC definitely is not :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6725] Make patron duplicate matching flexible
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '20

05 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6725 ByWater Sandboxes <bws.sandboxes(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #107846|0 |1 is obsolete| | --- Comment #8 from ByWater Sandboxes <bws.sandboxes(a)gmail.com> --- Created attachment 107859 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=107859&action=e… Bug 6725: Make patron duplicate matching flexible This patch adds a new system preference PatronDuplicateMatchingAddFields to list the patron's attributes to use for deduplication. The default value is surname, firstname and dateofbirth to keep existing behaviour. Test plan: 0. Apply the patch and execute the update DB entry 1. Create a new patron with surname, firstname 2. Create another patron with the same surname, firstname values => Confirm you get the duplicate warning 3. Modify the syspref to edit the list of attributes used to dedup 4. Repeat 1 and 2 with different values and confirm that you get the behaviours you expect Note: This is only impacting the add patron form from the UI, not the import patrons tool. Signed-off-by: Kelly McElligott <kelly(a)bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0