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

[Bug 12162] Add class="branchcode" to body tag to make OPAC CSS-styleable per branch
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

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

1 0

[Bug 6421] ability to have different opac styles for different libraries
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6421 Marc Véron <veron(a)veron.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |veron(a)veron.ch See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=12162 --- Comment #2 from Marc Véron <veron(a)veron.ch> --- Branch specific CSS can be added in opaclayoutstylesheet, OpacAdditionalStylesheet, or OPACUserCSS using the class branch-??? in the body tag, e.g.: <body ID="opac-main" class="branch-CPL" > See: Bug 12162 - Add class="branchcode" to body tag to make OPAC CSS-styleable per branch -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 14402] Add --fees option to cleanup_database.pl to purge all 0 balance fees and payments older than the given number of days
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14402 --- Comment #38 from vimal kumar <vimal0212(a)gmail.com> --- (In reply to Katrin Fischer from comment #37) > *** Bug 4076 has been marked as a duplicate of this bug. *** Thank you Katrin. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4076] Clearing payment history
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4076 --- Comment #2 from vimal kumar <vimal0212(a)gmail.com> --- (In reply to Katrin Fischer from comment #1) > There is now a cronjob available to delete old and resolved fines and fees > (bug 14402) > > *** This bug has been marked as a duplicate of bug 14402 *** Thank you brother. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 14822] Fine totals on circulation.pl don't include manually added fees
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14822 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

[Bug 9259] batch delete marc batches
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9259 --- Comment #7 from Aleisha Amohia <aleishaamohia(a)hotmail.com> --- (In reply to Katrin Fischer from comment #6) > (In reply to Owen Leonard from comment #5) > > What about the eraser icon instead? > > > > http://fontawesome.io/icon/eraser/ > > Looks good to me! Agreed, will continue with this asap! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14822] Fine totals on circulation.pl don't include manually added fees
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14822 Liz Rea <liz(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |liz(a)catalyst.net.nz --- Comment #1 from Liz Rea <liz(a)catalyst.net.nz> --- Why not include them? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 16315] New: OPAC Shelfbrowser doesn't display the full title
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16315 Bug ID: 16315 Summary: OPAC Shelfbrowser doesn't display the full title Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The OPAC shelf browser function uses the title from biblio.title database field, which means it only displays the 245$a. The remainder of the title (in the 245$b and $c) doesn't display. An example of this can be seen here: https://sthlibraries.koha-ptfs.co.uk/cgi-bin/koha/opac-detail.pl?biblionumb… It would be better if the whole title could be displayed. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 13895] Add API routes for checkouts retrieval and renewal
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13895 --- Comment #15 from Jiří Kozlovský <mail(a)jkozlovsky.cz> --- By holds i meant checkouts of course, sorry :) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6447] Add a button to allow people to choose 'Next Budget' when ordering
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '16

20 Jun '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6447 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de --- Comment #2 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- What you can currently do is start your new budget early and then already order against it - even if it's still marked inactive. Or you can move the orders to a new fund on receiving them. Does this help? -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. You are watching all bug changes.

1 0