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

[Bug 12721] Prevent software error if incorrect fieldnames given in sypref StatisticsFields
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12721 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #50668|0 |1 is obsolete| | Attachment #50669|0 |1 is obsolete| | Attachment #50855|0 |1 is obsolete| | --- Comment #21 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 50897 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=50897&action=ed… [PASSED QA] Bug 12721 - Prevent software error if incorrect fieldnames given in sypref StatisticsFields To reproduce issue: See comment #1 To test: - Apply patch - Leave syspref StatisticsFields empty - Display statistics for an author => Result: Table displays Shelving location, Collection code, Item type (as before) - Change syspref to any combination of location|itype|ccode => Result: Table displays columns as appropriate - Change syspref to some garbage => Result: Same as with empty syspref (was crashing without patch) - Change syspref to valid combination with trailing | => Result: Table displays columns as appropriate (was crashing without patch) - Change syspref to a combination of valid and invalid fields (location|blah|ccode) => Result: Table displays column of valid fields only (was crashing without patch) Signed-off-by: Aleisha <aleishaamohia(a)hotmail.com> Signed-off-by: Katrin Fischer <katrin.fischer.83(a)web.de> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12721] Prevent software error if incorrect fieldnames given in sypref StatisticsFields
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12721 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|--- |Small patch -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10459] borrowers should have a timestamp
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10459 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Signed Off --- Comment #33 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- It looks like we have a 'ton' of timestamp in the database. Apart from that there seems to be no existing other schema for timestamps columns that I could spot. I am not opposed to changing it - I think that's what Marcel wanted to do? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10459] borrowers should have a timestamp
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10459 Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |In Discussion --- Comment #32 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Kyle M Hall from comment #31) > I really dislike having a field name being the same as a mysql data type. I > think it introduces ambiguity. Would you or anyone else be opposed to naming > it "updated_on"? Have a look the discussion from some time ago. I introduced bortimestamp (an ugly but unique name so no ambiguous column problems), but the majority pressed me back to use timestamp and first resolving possible clashes in joins here and there.. Moving this back to In Discussion -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10459] borrowers should have a timestamp
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10459 Kyle M Hall <kyle(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle(a)bywatersolutions.com --- Comment #31 from Kyle M Hall <kyle(a)bywatersolutions.com> --- I really dislike having a field name being the same as a mysql data type. I think it introduces ambiguity. Would you or anyone else be opposed to naming it "updated_on"? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15675] Add issue_id column to accountlines and use it for updating fines
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15675 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |16378 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16378 [Bug 16378] Overdues.pm: Can't call method "store" without a package or object reference -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 16356] New: Error 500 when returning an item whose itemtype is not defined in ItemTypes
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16356 Bug ID: 16356 Summary: Error 500 when returning an item whose itemtype is not defined in ItemTypes Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sophie.meynieux(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When returning an item, Koha searches if it should show a specific message for this itemtype, using C4/ItemType->get() In 3.22, if item itemptype is not defined in itemtypes table, this will result in 500 Error -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 15675] Add issue_id column to accountlines and use it for updating fines
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15675 Jacek Ablewicz <abl(a)biblos.pk.edu.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=16378 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15675] Add issue_id column to accountlines and use it for updating fines
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15675 --- Comment #35 from Jacek Ablewicz <abl(a)biblos.pk.edu.pl> --- One pretty nasty regression got introduced by this bug, see Bug 16378 for details. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13877] seasonal predictions showing wrong in test
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '16

28 Apr '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13877 --- Comment #11 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Created attachment 50896 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=50896&action=ed… [PASSED QA] Bug 13877 - Fix QA issues Signed-off-by: Bernardo Gonzalez Kriegel <bgkriegel(a)gmail.com> No koha-qa errors Signed-off-by: Katrin Fischer <katrin.fischer.83(a)web.de> -- You are receiving this mail because: You are watching all bug changes.

1 0