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

[Bug 25409] New: Required dropdown missing "required" class near label
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25409 Bug ID: 25409 Summary: Required dropdown missing "required" class near label Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Templates Assignee: slavashishkin(a)gmail.com Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 104486 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=104486&action=e… Screenshot of missing 'required' class Select tag 'itemtype' in "onboardingstep5.tt" has 'required' attribute, accordingly to that, related label tag should also have 'required' class. Simple fix which slavashishkin(a)gmail.com will implement under my supervision. Similar cases I have found in history, which are pretty old: Bug 11812, Bug 4294, Bug 7670 -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 22437] New: Subsequent authority merges in cron cause biblios to lose authority information
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22437 Bug ID: 22437 Summary: Subsequent authority merges in cron cause biblios to lose authority information Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: pjamorim91(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Here's how to reproduce the problem: AuthorityMergeLimit syspref is default 50. Here's an example list of 3 authorities (A, B and C) that should be merged together - resulting in 1 authority - and the total count of biblios linked to each respective authority (similar to the interface you get when searching authorities): A 100 B 60 C 2 The good scenario: If you merge the authorities like this: First: C -> A Second: B -> A All is good, after the first merge (C -> A), A has 102 biblios. After second merge (B -> A), B no longer exists and A still has 102 - as expected, because the merge is scheduled to the cron. After forcing the cron koha-foreach --chdir --enabled /usr/share/koha/bin/cronjobs/merge_authorities.pl -b -v authority A now has 162 biblios, as expected. The bad scenario: The problem occurs if authorities are merged like this: First: C -> B Second: B -> A After the first merge (C -> B), B has 62 biblios. After the second merge (B -> A), B no longer exists and A still has 100 - as expected, because the merge is scheduled to the cron. However, after forcing the cron koha-foreach --chdir --enabled /usr/share/koha/bin/cronjobs/merge_authorities.pl -b -v authority A still has 100 biblios, and the 62 biblios that were previously linked to B have effectively lost the authority information they previously had. After some testing, I noticed that Koha will schedule an authority merge for the same authority (on itself), even when the biblios count doesn't surpass AuthorityMergeLimit, I'll explain: For the C -> B merge, the 2 biblios from C will be updated immediately in the application (because 2 < 50), but simultaneously Koha will schedule the cron merge B -> B. I think this happens because the merge.pl script first modifies the reference authority using ModAuthority (that calls the merge function), and then calls the merge function, can be seen here: https://github.com/Koha-Community/Koha/blob/18.11.x/authorities/merge.pl#L79 Which means that Koha will run the merge function, twice, for each authority merge made in the application. I think this is by design, because if B gets modified, Koha will have to update 60 biblios with the new authority information, updated subfields information etc, and this should be indeed postponed to the cron, hence the merge on itself B -> B caused by ModAuthority. However, because B -> A happened (deleting B) after C -> B and before the cron had the chance to run, by the time the cron has to run B -> B, B has already been deleted, cleaning the authority information from the 60 (or 62) biblio records. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 62

[Bug 25082] New: Unknown language code if 041 $a is linked to an authorized value list
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25082 Bug ID: 25082 Summary: Unknown language code if 041 $a is linked to an authorized value list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org >From Bug 20364, comment 13: When 041 $a (Language code of text/sound track or separate title) is associated with the LANG authorized value list, then the detail view of the record (OPAC and Intranet) show an "Unknown language code", even if the value of the subfield is a valid language code. This text comes from MARC21Languages.xsl. This behavior was expected? Maybe MARC21Languages.xsl code → Language list should be just a fallback if the code is not present/translated on associated list (probably LANG). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[Bug 25484] New: Public routes added by plugins are no longer accessible
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25484 Bug ID: 25484 Summary: Public routes added by plugins are no longer accessible Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com access to 'contrib' routes from plugins are no longer available after bug 25045 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 24905] New: log4perl.conf.in missing entries for the z39.50 server
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24905 Bug ID: 24905 Summary: log4perl.conf.in missing entries for the z39.50 server Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Bug 13937 introduced new log4perl.conf changes, but missed to tweak the packages' log4perl.conf.in template. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 14055] Bug 13979 breaks package upgrades
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14055 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|Oldversions |--- David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=25485 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13881] Add desk management
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13881 --- Comment #54 from Nicolas Legrand <nicolas.legrand(a)bulac.fr> --- (In reply to Katrin Fischer from comment #53) > Nicolas, should we add sponsorship by BULAC here? maybe! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24526] Auto renewal cronjob should have verbose and test mode options
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24526 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au --- Comment #21 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Katrin Fischer from comment #20) > I wonder if we could highlight this breaking change a bit more in the > release notes - currently it's almost lost: > > The patches make the --confirm switch required, without it script will be > run in test mode. Existing scheduled cronjobs will need to be updated to > supply this switch. Oh wow yeah that's a good idea. Easy to be caught out by that one. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25339] Validate biblionumber on opac-basket.pl and opac-review.pl
by bugzilla-daemon＠bugs.koha-community.org 18 May '20

18 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25339 --- Comment #9 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Marcel de Rooy from comment #8) > + $biblionumber = int($biblionumber); > > I think we have a few places where we do that. And it is really ugly imo. > If you dont pass a valid biblionumber, you should not get a valid response. > > Furthermore int does not like strings. We will have warnings like: > Argument "3abc" isn't numeric in int > > I would rather get rid of the other places.. Yeah, that's a good point. > > Changing status: ID or FQA ? Probably FQA for now, and maybe we should have a separate bug for returning a 404 or something when an invalid biblionumber is given. (And then this bug report would either become a duplicate or implement that new strategy.) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25522] New: Touched By ./GoldGanz
by bugzilla-daemon＠bugs.koha-community.org 17 May '20

17 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25522 Bug ID: 25522 Summary: Touched By ./GoldGanz Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: lanang.gaming06(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 104982 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=104982&action=e… Hi admin:v -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2