May 2020 - Koha-bugs - lists.koha-community.org

[Bug 24559] New: Elasticsearch - add support for 'date' fields
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24559 Bug ID: 24559 Summary: Elasticsearch - add support for 'date' fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com There is a fixme in the code related to this. For dates like the 260c and 264c we need a way to parse p2014 into 2014 etc. This affects sorting on dates -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 14708] The patron set as the anonymous patron should not be deletable.
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14708 didier <didier.gautheron(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |didier.gautheron(a)biblibre.c | |om --- Comment #14 from didier <didier.gautheron(a)biblibre.com> --- Hi, nitpicking here but IMO: - tests in their own commit make it easier for double checking they fail on unpatched code, as they must. - some patches could be squashed, thinking of git bisect. - Tests are done with 'AnonymousPatron' set to $anonymous_patron, so far so good, but what if AnonymousPatron is set to a different patron or unset? It's not obvious if it's covered by older tests. Regards Didier -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13547] Item field 'Materials specified' would be useful to see in OPAC
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13547 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=25261 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10517] koha-restore fails to create mysqluser@mysql_hostname so zebra update fails
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10517 --- Comment #23 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Rudolf Byker from comment #21) > By the way: Is the test plan supposed to be in the commit message, in a > comment, or both? It shoudl be in the commit message - in bugzilla it will then appear automatically in a comment, if you use git bz. See here: https://wiki.koha-community.org/wiki/Commit_messages -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 22134] New: Add account expiration information to patron details
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22134 Bug ID: 22134 Summary: Add account expiration information to patron details Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- On the patron detail page in the staff client, expired patrons should show a message at the top like the checkout page does. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 9290] Restricting patron category for online purchase suggestion
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9290 --- Comment #16 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- There are 3 ways to implement this: Syspref with a list of code, define at category level (admin/categories.pl) or circ rules. Circ rules seem overkill, even if more flexible (we can discuss if "adding suggestions" is a *circ* rule however...) Defining at category level is a bit more difficult here, especially for librarians to configure it (you have to go through the different categories). So yes, we could go with the pref (the uglier), even if far from perfect. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10517] koha-restore fails to create mysqluser@mysql_hostname so zebra update fails
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10517 --- Comment #22 from Rudolf Byker <rudolfbyker(a)gmail.com> --- (In reply to David Cook from comment #20) > (In reply to Martin Renvoize from comment #16) > > > > I am, however, pretty keen to take such an approach and drop 5.5 support > > with this release and so this patch is 'on hold' for now. > > For what it's worth, I think koha-remove uses "DROP USER IF EXISTS", so we > already have mixed support for 5.5. > > I ended up removing "IF EXISTS" and updating koha-remove to use --force so > that it could survive fatal errors. Are you talking about the `--force` option on the MySQL command line utility? That smells like technical debt. Using it is the same or worse as using `|| true`, since you will hide lots of potential errors. We only need to handle one very specific error (which is not even an error, if you consider Idempotency to be a good programming pattern for such scripts – which it is). Using a catch-all to hide all errors is almost always a Bad Idea (TM). -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10517] koha-restore fails to create mysqluser@mysql_hostname so zebra update fails
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10517 --- Comment #21 from Rudolf Byker <rudolfbyker(a)gmail.com> --- (In reply to Victor Grousset/tuxayo from comment #18) > > 2) Remove the instance completely using `koha-remove`. > > I'm having an issue here. Maybe it's my dev environment. > > root@4dfd0fcc251b:kohadevbox$ koha-remove kohadev > Removing Koha instance kohadev > [ ok ] Stopping Plack daemon for kohadev:. > userdel: user kohadev-koha is currently used by process 1005 > /usr/sbin/deluser: `/usr/sbin/userdel kohadev-koha' returned error code 8. > Exiting. > > > > > Using koha-disable doesn't help. There are still starman and apache > processes running that are from the unix user of the instance. > > Could there be anything more to do before removing the instance? Probably your dev environment. I've never had this issue, and I'm using my own patch. Did you check which process is still using the user using `ps -u kohadev-koha`? By the way: Is the test plan supposed to be in the commit message, in a comment, or both? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13547] Item field 'Materials specified' would be useful to see in OPAC
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13547 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |release-notes-needed -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13547] Item field 'Materials specified' would be useful to see in OPAC
by bugzilla-daemon＠bugs.koha-community.org 06 May '20

06 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13547 --- Comment #23 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- https://wiki.koha-community.org/wiki/Holdings_data_fields_(9xx) likely needs updating to reflect this bug. -- You are receiving this mail because: You are watching all bug changes.

1 0