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

[Bug 14715] Results per page setting for catalog search in staff client and OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '21

10 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14715 --- Comment #117 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi Holly, when using OpacHiddenItems the results are filtered "after" paging, is what I was told, so it leaves holes in the result lists like you see. That cannot be changed easily it seems, which is why it was chosen to remove the numbering of results when OpacHiddenItems is used to hide this a bit. See also: bug 23923 and bug 18989 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14715] Results per page setting for catalog search in staff client and OPAC
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '21

10 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14715 Holly <hc(a)interleaf.ie> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hc(a)interleaf.ie --- Comment #116 from Holly <hc(a)interleaf.ie> --- I'm noticing something in situations where the OPAC is suppressing records that I would appreciate some feedback on. I walk through what I'm seeing below using a general example from a site I'm testing on. In the below example, the system preferences have been set so that the results per page dropdown appears and a search will show 10 results per page for both the OPAC and the staff side. 1. I use the advanced search on the OPAC to search for all items with a specific item type called "General items". 3. The results per page display shows that there should be 10 results on the first and all other pages. 4. There are actually 9 results on the first results page. 5. There are 10 results on all other pages. 6. Doing the same search on the staff side, the results per page display shows that there should be 10 results on the first and all other pages. 7. There are 10 results on the first page and all other pages. 8. The first result on the first page of the staff side does not appear on the OPAC. Looking at it, this seems to be because all items on the bibliographic record are marked as lost. 9. It is fine that the OPAC is not showing the suppressed record, but I would assume in cases like this, instead of showing nine results on the first page, it should show 10, moving the first result from the second page up one, and so on for all the other pages. To summarise, my understanding is that there should be 10 results on the first page of results, assuming that all subsequent pages have 10 or more results on them, even if one of the results for the first page is suppressed. Is anyone else seeing this? Would this require a new bug to be opened? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 28351] New: Cannot set restrictions when dateformat is other than mm/dd/yyyy
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '21

09 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28351 Bug ID: 28351 Summary: Cannot set restrictions when dateformat is other than mm/dd/yyyy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Format is not correctly applied, so any date that doesn't parse well as mm/dd/yyyy is reset to current date. To reproduce: 0. Set dateformat to mm/dd/yyyy 1. Go to a patron detail page 2. Open the 'Restrictions' tab 3. Choose a future date in which the day is higher than 12 => SUCCESS: The input has the date we chose 4. Set dateformat to dd/mm/yyyy 5. Repeat 3 => FAIL: It sets the current date, the browser console shows an error. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 7972] GUI for Crons
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '21

09 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7972 Lisette Scheer <lisetteslatah(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisetteslatah(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7972] GUI for Crons
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '21

09 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7972 koha-US bug tracker <bugzilla(a)koha-us.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla(a)koha-us.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7972] GUI for Crons
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '21

09 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7972 Daniel Gaghan <daniel.gaghan(a)pueblolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.gaghan@pueblolibrary | |.org --- Comment #11 from Daniel Gaghan <daniel.gaghan(a)pueblolibrary.org> --- Having this enhancement would be a big help. Scheduling crons is not the biggest need for us (PCCLD) right now. However, knowing if the report is running or if it failed is, IMHO. So I would vote for a GUI that shows the name of the report, when it's scheduled for, when it was last ran and whether it failed or not. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 27169] New: sip2 not enable
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '21

09 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27169 Bug ID: 27169 Summary: sip2 not enable Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: ujjwalguptax202(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com sip2 not working after use of koha-sip --enable library and koha-sip --start library when check the status it shows sip2 running but but but its not connecting when i use ip and port to connect sip2 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 16181] New: Limit number of tags loaded initially for tag cloud
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '21

09 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16181 Bug ID: 16181 Summary: Limit number of tags loaded initially for tag cloud 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a patron has an large number of tags (say 3,421) the tag cloud takes an inordinately long time to load. Maybe we could enforce a limit on initial load and then allow user to load more or paginate through all? -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 27899] New: Missing description for libraryNotPickupLocation on request.pl
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '21

08 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27899 Bug ID: 27899 Summary: Missing description for libraryNotPickupLocation on request.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org As the attached screenshot highlights, there's no description for that error status. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 28091] New: Add meta tag with Koha version number to staff interface pages
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '21

08 Jun '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28091 Bug ID: 28091 Summary: Add meta tag with Koha version number to staff interface pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com On the OPAC in the HTML head there is a line like this: <meta name="generator" content="Koha 20.1200024"> This is super helpful when writing jQuery that is only useful for a particular version of Koha. The staff client pages should include the same. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17