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

[Bug 14060] Remove readonly on date inputs
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14060 --- Comment #25 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- I think this version should be push as it, and follow-ups could come later... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13301] Call number link in search results is broken
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13301 --- Comment #9 from Barton Chittenden <barton(a)bywatersolutions.com> --- (In reply to Owen Leonard from comment #8) > Can this bug be reproduced in versions newer than 3.18.x? If so, please > update the report's version information. If not, please close. I just tested this at the library that reported the issue; they're still seeing the problem under 3.22.07. I'll dig back through the templates and through the code and see if I can't find out what's triggering the behavior in question. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15261] Verify if checkouts or reserves requests periods overlap with existing reserves
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15261 Alex Arnaud <alex.arnaud(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #49001|0 |1 is obsolete| | Attachment #49002|0 |1 is obsolete| | Attachment #49003|0 |1 is obsolete| | --- Comment #31 from Alex Arnaud <alex.arnaud(a)biblibre.com> --- Created attachment 52704 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=52704&action=ed… Bug 15261: Verify if checkouts/reserves requests periods overlap... ... with existing reserves When checking out or placing hold, we should check if an existing reserve whose period overlap exists. A user place an hold from opac whose requested period overlap an existing reserve period => prevent reserve, A librarian place an hold from staff whose requested period overlap an existing reserve period => Warn librarian (Ask for confirmation), A librarian make a checkout from staff whose requested period overlap an existing reserve period => Warn librarian (Ask for confirmation). Test plan: Enable syspref: AllowHoldDateInFuture OPACAllowHoldDateInFuture PreventChechoutOnSameReservePeriod and PreventReservesOnSamePeriod 1 (staff side): Place a hold on title (which has only one items) level with start date and expiration date. Place another hold (also title level) with period overlaping this reserve. Check you are warned about an existing reserve 2 (staff side): Place a hold on title (which has more than one items) level with start date and expiration date. Place another hold (also title level) with period overlaping this reserve. Check you are NOT warned about an existing reserve. Because it remains at least one item not reserved. 3 (staff side): Place a hold on item level with start date and expiration date. Place another hold on item level with period overlaping this reserve. Check you are warned about an existing reserve. 4 (opac side): Do the same than for staff side. Instead of a warn, reserve is prevented. 5: Place a hold on title (which has only one items) level with start date and expiration date. Try to checkout the unique item from this title with period overlaping the reserve period. Check you are warned about an existing reserve 6: Place a hold on title (which has more than one items) level with start date and expiration date. Checkout an item from this title with period overlaping the reserve period. Check you are NOT warned about an existing reserve. 7: Place a hold on item level with start date and expiration date. Checkout this item period overlaping the reserve period. Check you are warned about an existing reserve Rabased on master Rebased on master (2016-06-23) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 16044] New: Define a L2 cache for all objects set in cache
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16044 Bug ID: 16044 Summary: Define a L2 cache for all objects set in cache Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 11998 I have added a POC on bug 11998 ( patch "Add a L1 cache for sysprefs" ) to use a L1 cache instead of retrieving infos from memcache everytime. If it works for sysprefs, we could use it for any objects set in cache (I have Marc structure and framework in mind). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11998 [Bug 11998] Syspref caching issues -- You are receiving this mail because: You are watching all bug changes.

1 69

[Bug 16412] New: Cache undef in L1 only
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16412 Bug ID: 16412 Summary: Cache undef in L1 only Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org No need to cache undef in L2. Prevent numerous warnings like: Use of uninitialized value in subroutine entry at /usr/share/koha/masterclone/Koha/Cache.pm line 284 -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 16221] New: Use Storable::dclone() instead of Clone::clone() for L1 cache deep-copying mode
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16221 Bug ID: 16221 Summary: Use Storable::dclone() instead of Clone::clone() for L1 cache deep-copying mode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org Storable dclone() is over 3x faster then Clone::clone() when used for creating a deep copies of the big, complex data structures like MARC frameworks. See also Bug 16044 comments #18 & #20. This is a trivial version of Bug 16166. Performance test results (see Bug 16140 comment #23 for test setup description): # master 146.29 (14.64+14.53+14.51+14.57+14.72+14.56+14.53+15.06+14.56+14.61) # master + patch from this bug report 96.5 (9.77+9.63+9.77+9.77+9.68+9.05+9.68+9.83+9.63+9.69) # master + Bug 16166 90.7 (9.15+9.10+9.16+8.41+9.19+9.19+9.11+9.19+9.02+9.18) Bug 16166 is a bit faster and more comprehensive implementation, but also more complex and harder to test/evaluate. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 16229] New: Koha::Cache should be on the safer side
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16229 Bug ID: 16229 Summary: Koha::Cache should be on the safer side Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 16044 Blocks: 16221 Theoretically our Koha::Cache is not as safe as possible, the set_in_cache and get_from_cache subroutines should always clone the structure to avoid uncontrollable behaviors. There are, at least, 2 issues to cover: - get_from_cache does not deep copy on first call - set_in_cache does not deep copy Note that bug 16221 plans to replace Clone::clone with Storable::dclone, it should be built on top of this patch. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16044 [Bug 16044] Define a L1 cache for all objects set in cache https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16221 [Bug 16221] Use Storable::dclone() instead of Clone::clone() for L1 cache deep-copying mode -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 9814] KohaAdminEmailAddress syspref webpage field doesn't handle double quotes
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9814 Marc Véron <veron(a)veron.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=5471 CC| |veron(a)veron.ch --- Comment #1 from Marc Véron <veron(a)veron.ch> --- Still valid on current master. After entering something like "The Library" <thelibrary(a)example.com>, saving and refreshing the page, I get an empty field for KohaAdminEmailAddress, followed by some html snippet: Use [ ] " autocomplete="off" /> as the email address for the administrator of Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 5471] Quotes in tags cause moderation approval/rejection to fail
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5471 Marc Véron <veron(a)veron.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=9814 -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 3679] Specify "from" address when emailing a list or cart from opac
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '16

23 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3679 Marc Véron <veron(a)veron.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |veron(a)veron.ch -- You are receiving this mail because: You are watching all bug changes.

1 0