September 2019 - Koha-bugs - lists.koha-community.org

[Bug 16392] New: Tips & Tricks?
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16392 Bug ID: 16392 Summary: Tips & Tricks? Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: mirko(a)abunchofthings.net I found the category "Tips and Tricks" via Google. I wanted to browse it on the website. I don't see a link mentioning it anywhere? Browsing it is impossible, because the newsletter is in this category too. It appears to be in _every_ category, which makes categories useless. "Posted in 3.12, 3.14, 3.16, Events, IRC Meetings, Koha, Koha News, Koha Newsletter, Koha Tips & Tricks, KohaCon 2014". -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 16379] New: Add tests for Statistics.pm
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16379 Bug ID: 16379 Summary: Add tests for Statistics.pm 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: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org Statistics.pm has no tests. See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12721#c25 -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 16375] New: Add arg to 'koha-upgrade-schema' to run on a specific 'updatedb.pl' file
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16375 Bug ID: 16375 Summary: Add arg to 'koha-upgrade-schema' to run on a specific 'updatedb.pl' file Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Add arg to 'koha-upgrade-schema' to run on a specific 'updatedb.pl' file more info to come... -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 16374] New: Support cataloging fanzines
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16374 Bug ID: 16374 Summary: Support cataloging fanzines Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nicolasmaia(a)tutanota.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Fanzines can generally be difficult to catalog, since many lack basic info such as authorship, year and place of production or contact address. Koha should probably do something in the sense of making zines more easily catalogued. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 16306] New: C4::Context->setCommandlineEnvironment() convenience function
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16306 Bug ID: 16306 Summary: C4::Context->setCommandlineEnvironment() convenience function 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org There is no unified way to set the environment for commandline scripts, even if the C4::Context->interface('commandline') explicitly allows setting the cli interface. Also a default user environment must be set. This function wraps the complexity of environment setting in the command line. Usage: use C4::Context; BEGIN { C4::Context->setCommandlineEnvironment(); } ... #Load other dependencies that might depend on the environment or just: ... use C4::Context; C4::Context->setCommandlineEnvironment(); ... -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 16247] New: Attaching PDFs to New Patron E-mail
by bugzilla-daemon＠bugs.koha-community.org 11 Jan '20

11 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16247 Bug ID: 16247 Summary: Attaching PDFs to New Patron E-mail Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: jesse(a)meta21st.com QA Contact: testopia(a)bugs.koha-community.org A while back, I asked on the listserv if anyone had experimented with writing a script that would attach a PDF to the New Patron data email when it goes out. I am thinking specifically about attaching a PDF of library policies to that specific notification. I still think this is a good idea. I think it's helpful to be able to upload documents to patron records. But it might be a good idea if we could also attach documents - at least standard documents to standard/default e-mails. What kinds of tools, scripts or functionality would have to be added for this idea to be put into a future release? Curious... Thank you Jesse -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 23470] New: Elasticsearch - OpacSuppression not implemented in search result
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '20

10 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23470 Bug ID: 23470 Summary: Elasticsearch - OpacSuppression not implemented in search result Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca Hi, Records suppressed with OpacSuppression are always displayed in search result with ElasticSearch. If I try to consult the record in detailed view, the blocking message appears however. I read here https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16660#c1 : NB: OPAC suppression is not implemented for Elasticsearch Anyone work on it? Regards, Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 20278] New: Cancel Hold alert in OPAC provides confusing options
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '20

10 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20278 Bug ID: 20278 Summary: Cancel Hold alert in OPAC provides confusing options 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: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org When a patron cancels a hold, an alert pops up asking "Are you sure you want to cancel this reservation?" The two options available are "OK" or "Cancel". OK -> cancels hold Cancel -> does not cancel hold (cancels the operation) This is confusing, because clicking 'Cancel' stops the cancellation of the hold! It would be clearer if the options were "Yes" and "No": >Are you sure you want to cancel this hold? >Yes | No or perhaps: >Are you sure you want to cancel this hold? >Yes I'm sure| Undo -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 17151] New: Extended patron attributes not importing when using double quotes
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '20

10 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17151 Bug ID: 17151 Summary: Extended patron attributes not importing when using double quotes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: danielle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Patron import tool directions on Patron Import Tool Page states: _____________ Example 2: STARTDATE:January 1 2010,TRACK:Day If an input record has more than one attribute, the fields should either be entered as an unquoted string (previous examples), or with each field wrapped in separate double quotes and delimited by a comma: Example 3: "STARTDATE:January 1, 2010","TRACK:Day" The second syntax would be required if the data might have a comma in it, like a date string. ____________ Only the second example works "STARTDATE:January 1 2010,TRACK:Day" The double quotes import does not work. Loading the patron will fail with a "Line 2 could not be parsed!" error. Partners of BWS are also reporting this same behavior. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 23106] New: Totals are unclear when a credit is involved on the 'Pay fines' screen
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '20

09 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23106 Bug ID: 23106 Summary: Totals are unclear when a credit is involved on the 'Pay fines' screen Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- We currently display the unapplied credit lines (along with an 'apply credit' button) above the 'Total' line and then we include the un-applied credit amount in the total amount. This is confusing to the end user. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24