December 2017 - Koha-bugs - lists.koha-community.org

[Bug 19803] New: SQL report export can fail HTTP 414 Request-URI Too Large
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '18

03 Jan '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19803 Bug ID: 19803 Summary: SQL report export can fail HTTP 414 Request-URI Too Large Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org After running a saved SQL report, one can download result into a file. This uses a link with the SQL query as URL argument. If this query is really big, the download may fail with HTTP 414 "Request-URI Too Large". This link should use the report id to retrieve SQL query. There is a comment asking this in reports/guided_reports.pl : my $sql = $input->param('sql'); # FIXME: use sql from saved report ID#, not new user-supplied SQL! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19883] New: Add a selenium script to hit all the pages
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '18

02 Jan '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19883 Bug ID: 19883 Summary: Add a selenium script to hit all the pages Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 19384 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19384 [Bug 19384] [OMNIBUS] Add Selenium tests -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 19894] New: adadadada
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '17

30 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19894 Bug ID: 19894 Summary: adadadada Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyuzenxmarch1(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 70207 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=70207&action=ed… adada ad -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 19895] New: adadadada
by bugzilla-daemon＠bugs.koha-community.org 30 Dec '17

30 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19895 Bug ID: 19895 Summary: adadadada Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyuzenxmarch1(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org ad -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 8962] Restore Any index behavior and add Anywhere index
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '17

29 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8962 --- Comment #57 from Magnus Enger <magnus(a)libriotech.no> --- (In reply to Katrin Fischer from comment #55) > Hi Magnus, I think this is out of scope if this aims to restore the former > behaviour - you'd have to remove the place of publication from indexes. > Maybe a next step could be a configurable Any index? Sounds good! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6685] circ rules by groups of items
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '17

29 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6685 Hugh Rundle <hughr(a)brimbank.vic.gov.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hughr(a)brimbank.vic.gov.au --- Comment #12 from Hugh Rundle <hughr(a)brimbank.vic.gov.au> --- Great idea, and would resolve a problem for us too. We have different itemtypes for games for adults vs games for children because we fine adults but not children, but we want to maintain a limit on the number of games you can borrow on a single card, regardless of item type. Definitely should use itemtypecat. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '17

29 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Hugh Rundle <hughr(a)brimbank.vic.gov.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hughr(a)brimbank.vic.gov.au --- Comment #99 from Hugh Rundle <hughr(a)brimbank.vic.gov.au> --- Is anyone still working on this? Being able to provide extended hold dates (e.g. for items set aside for our housebound patrons) would be very useful. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9834] Should reverting a waiting hold keep the item number?
by bugzilla-daemon＠bugs.koha-community.org 29 Dec '17

29 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9834 Hugh Rundle <hughr(a)brimbank.vic.gov.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hughr(a)brimbank.vic.gov.au --- Comment #5 from Hugh Rundle <hughr(a)brimbank.vic.gov.au> --- Definitely needed for all the reasons mentioned: if holds are 'next available' (which is nearly always the case for us) then turning it into an item-level hold on allocation isn't ideal. Also, usually if you're reverting the waiting status it's because the item has gone missing, so the only way to fix this is actually to cancel the hold and then place a new hold and push the borrower to the top of the list again, which is ...suboptimal. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 8962] Restore Any index behavior and add Anywhere index
by bugzilla-daemon＠bugs.koha-community.org 28 Dec '17

28 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8962 --- Comment #56 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- As this would be a change of behavior now after a long time of dom indexing... should we make it possible to switch the one that is used in the GUI when selecting 'keyword'? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8962] Restore Any index behavior and add Anywhere index
by bugzilla-daemon＠bugs.koha-community.org 28 Dec '17

28 Dec '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8962 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de --- Comment #55 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Magnus, I think this is out of scope if this aims to restore the former behaviour - you'd have to remove the place of publication from indexes. Maybe a next step could be a configurable Any index? -- You are receiving this mail because: You are watching all bug changes.

1 0