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

[Bug 29030] New: Problems introduced by bugg 25728
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29030 Bug ID: 29030 Summary: Problems introduced by bugg 25728 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: klas.blomberg(a)skovde.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl There are two problems with the feature of creating new authorized values introduced by bugg 25728 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25728 The MINOR problem is that you can save a new authorized value without actually entering a new authorized value, you just need a description The MAJOR problem is that this feature isn't optional! Introducing a new authorized value is a complex process where you have to take library limitaions into consideration, authorized values are used in sysprefs and conjobs, often you have to rewrite some reports when you introduce a new authorized value &c, &c. In short: We certainly don't want anyone to create new authorized values on the fly! Not even I should have that possibility. We have had this unwelcome feature for some weeks, and there are already dozens of new athorized values created by mistake. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 28484] New: Elasticsearch fails to parse query if colon or exclamation point is in 245$a
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28484 Bug ID: 28484 Summary: Elasticsearch fails to parse query if colon or exclamation point is in 245$a Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: b.pastern4k(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We have Elasticsearch 6.8.15 and the following error happens when trying to enter colon or exclamation point into 245$a as the last symbol [query_shard_exception] Failed to parse query [(host-item:osteuropa:)], with: {"index_uuid": ....} called from sub Search::Elasticsearch::Role::Client::Direct::__ANON__ at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 96 'Failed to parse query [(host-item:osteuropa:)]'}],'failed_shards' => [{'shard' => 0,'node' => 'node','reason' => {'type' => 'query_shard_exception','caused_by' => {'caused_by' => {'type' => 'parse_exception','reason' => 'Encountered " ":" ": "" at line 1, column 20. Error does not happen when entering either of these symbols in 245$b. Are these symbols not properly escaped in that subfield? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 28438] New: Capitalization: Various corrections
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28438 Bug ID: 28438 Summary: Capitalization: Various corrections Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: katrin.fischer(a)bsz-bw.de, testopia(a)bugs.koha-community.org I did a search for capitalization errors in the templates and found many. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 29049] New: Holds page shows too many priority options in pulldown
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29049 Bug ID: 29049 Summary: Holds page shows too many priority options in pulldown Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1 - Place 5 holds on a biblio 2 - 'Find' two holds i.e. check them in to set them as transit or waiting 3 - Load the holds page for the biblio 4 - Check the pull down for priority 5 - Note holds has priority 1-3 but dropdown is 1-5 6 - Click 4 or 5 and note nothing happens -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 29070] New: Accessibility: OPAC Purchase Suggestions on search results page has insufficient contrast
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29070 Bug ID: 29070 Summary: Accessibility: OPAC Purchase Suggestions on search results page has insufficient contrast Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The "Not finding what you're looking for? Make a purchase suggestion" text box on the search results page (opac-search.pl) is hard to read and fails to meet accessibility guidelines. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: - Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; - Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. - Logotypes: Text that is part of a logo or brand name has no contrast requirement." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 29068] New: Accessibility: OPAC search results summary text has insufficient contrast
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29068 Bug ID: 29068 Summary: Accessibility: OPAC search results summary text has insufficient contrast Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The OPAC search results summary text ("Edition", "Material type", "Format" etc) is hard to read (grey text on a grey background) and the contrast ratio fails to meet accessibility guidelines. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: - Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; - Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. - Logotypes: Text that is part of a logo or brand name has no contrast requirement." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 29065] New: Accessibility: OPAC clear search history link has insufficient contrast
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29065 Bug ID: 29065 Summary: Accessibility: OPAC clear search history link has insufficient contrast Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The contrast ratio for the OPAC Delete your search history link fails to meet accessibility guidelines. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: - Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; - Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. - Logotypes: Text that is part of a logo or brand name has no contrast requirement." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 29038] New: Accessibility: OPACUserSummary heading doesn't have sufficient contrast
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29038 Bug ID: 29038 Summary: Accessibility: OPACUserSummary heading doesn't have sufficient contrast Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The "heading" of the OPACUserSummary table has bad contrast (grey script on grey background). This makes the text difficult to read and fails to meet accessibility criteria. The Summary table is only visible if you are logged in, have some checkouts and OPACUserSummary is active. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1..." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 29037] New: Accessibility: OPAC breadcrumb links don't have sufficient contrast
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29037 Bug ID: 29037 Summary: Accessibility: OPAC breadcrumb links don't have sufficient contrast Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The OPAC breadcrumb links are on a grey background and don't have sufficient contrast. This makes the text difficult to read and fails to meet accessibility criteria. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: - Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; - Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. - Logotypes: Text that is part of a logo or brand name has no contrast requirement." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 29035] New: Accessibility: OPAC masthead_search label doesn't have sufficient contrast ratio
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '21

08 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29035 Bug ID: 29035 Summary: Accessibility: OPAC masthead_search label doesn't have sufficient contrast ratio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bolshawh(a)parliament.uk QA Contact: testopia(a)bugs.koha-community.org The contrast ratio for the OPAC mast_head search label fails to meet accessibility guidelines. WCAG 2.1 1.4.3 Contrast (Minimum) Level AA: "The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: - Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; - Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. - Logotypes: Text that is part of a logo or brand name has no contrast requirement." (https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#contrast-minimum) There are several free websites for checking the contrast ratio, e.g. https://webaim.org/resources/contrastchecker/ You can also use the built-in accessibility functions in Firefox and Chrome, as well as specialist accessibility browser extensions like WAVE (https://wave.webaim.org/) -- You are receiving this mail because: You are watching all bug changes.

1 13