January 2014 - Koha-bugs - lists.koha-community.org

[Bug 7707] New: Add fines placeholders in notices to display fine information on notices
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7707 Priority: P5 - low Change sponsored?: --- Bug ID: 7707 Assignee: henridamien(a)koha-fr.org Summary: Add fines placeholders in notices to display fine information on notices QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: wizzyrea(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Notices Product: Koha Add <<fines.total>> and other fines placeholders in notices to display total owed in fines on notices. It would be cool to be able to let patrons know how much they owed in fines in their overdue notices. This could take a couple forms * Per item fines (<<fines.item>> or <<items.content.fines>> * Total balance of account (<<fines.total>>) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 7424] New: Koha should have a designated place for custom CSS
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7424 Bug #: 7424 Summary: Koha should have a designated place for custom CSS Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: wizzyrea(a)gmail.com QAContact: ian.walls(a)bywatersolutions.com We allow people to define custom CSS templates for varying things - opac, intranet, and (hopefully soon) slips and notices. It makes sense to have a sanctioned place within Koha to keep those files. I propose the following location: OPAC - koha-tmpl/opac-tmpl/prog/custom_css Intranet - koha-tmpl/intranet-tmpl/prog/custom_css Additionally, it would be nice to update the packages to dump these folders into the backup, to save any custom files stored there. We should also take care to *never* clobber anything in this directory on upgrade. We could provide "sample" CSS files (notices.sample, receipts.sample, to name a couple) but never overwrite anything else in that folder. Documentation for administrators should also be updated to tell system folks the "proper," "best practice" or "suggested" location to keep custom CSS files. The path to external CSS files can still be defined in the syspref, so administrators can define an external server if they so choose (many need this functionality because they have no shell or ftp access to their server). Questions? Concerns? Things I have not considered? -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 1

[Bug 8156] New: allow users to put things in lists that are not in the catalog (free text entries to lists)
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8156 Priority: P5 - low Change sponsored?: --- Bug ID: 8156 Assignee: wizzyrea(a)gmail.com Summary: allow users to put things in lists that are not in the catalog (free text entries to lists) Severity: enhancement Classification: Unclassified OS: All Reporter: wizzyrea(a)gmail.com Hardware: All Status: NEW Version: unspecified Component: OPAC Product: Koha One of our libraries came up with the idea that it would be cool to allow library users (and presumably staff) to put things on lists that are not in the catalog. One possible way to do it: in the lists interface, have a "add your own item" form, that allows entering title, author fields. In the list display, list those user created items with the title and author linked to searches for that exact title/author string. The idea being that a user could put a book they knew was coming on their reading list, but that wasn't already in the catalog, and easily search for it later. Another example would be for librarians to use this to create award winners lists of items that were award winners, but displaying title/authors that the library didn't own alongside titles/authors that the library *did* own. I think there are more applications for this - I recall there were several more when I floated the idea originally in the IRC channel. It's a nice-to-have, not a must-have. Pretty cool feature though, I think. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 9311] New: How to access Koha from internet
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9311 Bug ID: 9311 Summary: How to access Koha from internet Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.8 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Websites, Mailing Lists, etc Assignee: wizzyrea(a)gmail.com Reporter: tung.tung11191(a)gmail.com I have a static IP, i do not know how to setting Koha to access throw Internet? thanks in advanced -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 11056] New: dead code in basketgroup.pl : remove code depending on "validate" param
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11056 Bug ID: 11056 Summary: dead code in basketgroup.pl : remove code depending on "validate" param Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathieu.saby(a)univ-rennes2.fr QA Contact: testopia(a)bugs.koha-community.org Some code is dead in basketgroup.pl all the block depending on "($op eq 'validate')" clause the "validate" parameter is no more used in template, since a Biblibre commit has rewritten basketgroup template in 2009 : http://git.koha-community.org/gitweb/?p=koha.git;a=commit;h=263961312c1ff76… M. Saby -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 2152] eliminate OPACBaseURL system preference and replace with SERVER_NAME
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2152 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.koha-community. | |org/bugzilla3/show_bug.cgi? | |id=11575 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8766] New: OPACBaseURL still called as OPACBaseurl in many files
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8766 Priority: P5 - low Change sponsored?: --- Bug ID: 8766 Assignee: oleonard(a)myacpl.org Summary: OPACBaseURL still called as OPACBaseurl in many files Severity: minor Classification: Unclassified OS: All Reporter: dcook(a)prosentient.com.au Hardware: All Status: NEW Version: master Component: Templates Product: Koha OPACBaseurl is still being used in opac-results.tt and opac-opensearch.tt It also shows up in many Poodle files. Note: opac-results.tt doesn't currently get passed OPACBaseURL anyway, but it's still probably a good idea to have it spelled correctly. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 2152] eliminate OPACBaseURL system preference and replace with SERVER_NAME
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2152 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au --- Comment #1 from David Cook <dcook(a)prosentient.com.au> --- After some experimenting on proxied and non-proxied connections, it appears that $ENV{'SERVER_NAME'} is the domain name of the URL that a user hits the page with, and NOT the ServerName provided in the Apache configuration. This means that the OPACBaseURL set in Auth.pm during the "get_template_and_user" call will depend on the URL that a user provided to get to that page. Except...when the Koha server is sitting behind a proxy server. In that case, the $ENV{'SERVER_NAME'} appears to come from the proxy server (I'm not certain what name is used...but it looks like some kind of local identifier), while $ENV{'HTTP_X_FORWARDED_HOST'} will contain the domain of the URL provided by the user. I'm opening bug 11575 to investigate further into this. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11477] New: Add names for librarian and borrowers in the logs
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11477 Bug ID: 11477 Summary: Add names for librarian and borrowers in the logs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Currently, borrowernumber is shown without any other information in the logs. One of our libraries has pointed out that it would be much more useful if they saw the firstname/lastname of the librarian performing tasks and the users connected to those tasks. Seems reasonable to me. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 11476] Opac self registration title pull down offers 2 empty options
by bugzilla-daemon＠bugs.koha-community.org 17 Jan '14

17 Jan '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11476 Galen Charlton <gmcharlt(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to Master CC| |gmcharlt(a)gmail.com --- Comment #4 from Galen Charlton <gmcharlt(a)gmail.com> --- Pushed to master. Thanks, Owen! -- You are receiving this mail because: You are watching all bug changes.

1 0