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

[Bug 21090] New: Description of itemtype group doesn't show when there is an itemtype with the same code
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '19

10 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21090 Bug ID: 21090 Summary: Description of itemtype group doesn't show when there is an itemtype with the same code 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When an ITEMTYPECAT is using the same code as an itemtype, the description is not showing on the advanced search in OPAC. To test: - Create an itemtype BK - Create an ITEMTYPECAT BK - Link 2 itemtypes to this search category - Verify the description is not showing up on advanced search in the OPAC -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 18944] New: ITEMTYPCAT description is no longer used
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '19

10 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18944 Bug ID: 18944 Summary: ITEMTYPCAT description is no longer used Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When grouping several itemtypes using the ITEMTYPECAT authorised value, the grouping works, as seen on the advanced search page, but it doesn't display the correct description from the authorised value, but is still using one of the itemtype descriptions. So far tested on 16.11.x Used to work with 3.22.x - so this is a regression -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 17212] New: ITEMTYPECAT broken if there is another authorised value with same code
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '19

10 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17212 Bug ID: 17212 Summary: ITEMTYPECAT broken if there is another authorised value with same code Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The grouping of itemtypes on the advanced search doesn't work correctly, if there is another authorised value in another category with the same code. To test: - Add a collection TEST with a description - Add a ITEMTYPECAT TEST with a different description - Use TEST to group some itemtypes together - Take a look at OPAC advanced search - notice itemtypes are grouped, but description of the collection is shown. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 17470] New: overdue_notices.pl produces X emails with the SAME list of ALL overdue items if a patron has overdue items from X branches
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '19

10 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17470 Bug ID: 17470 Summary: overdue_notices.pl produces X emails with the SAME list of ALL overdue items if a patron has overdue items from X branches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org If patron P has two overdue items: I1 from branch B1 and I2 from branch B2, then overdue_notices.pl will produce two emails coming from B1 and B2 that have the same list of BOTH items I1 AND I2 in BOTH emails. I believe that this is not an intended behavior and that each email coming from each branch should show overdue items belonging to that respective branch only. Steps to reproduce: 0/ Have (or create) at least two branches B1 and B2 1/ Make sure you're logged in with an account belonging to B1, or switch to branch B1 2/ checkout item I1 (belonging to B1) to patron P (preferably while specifying a due date < today) 3/ switch to branch B2 4/ checkout item I2 (belonging to B2) to patron P (preferably while specifying a due date < today) 5/ make sure you have defined "Overdue notice/status triggers" for that patron category, ie with Delay=1 so that "Overdue Notice" is selected and "Email" is checked. 6/ from cli run 'perl ./misc/cronjobs/overdue_notices.pl' (optionally specifying also '-library B1 -library B2') 7/ (at least) two new entries will be generated in message_queue DB table, coming from different branches that have the SAME list of overdue items 8/ either see the 'content' field in these entries, or run 'perl ./cronjobs/process_message_queue.pl' to receive the actual emails (provided the email is properly setup) I have verified the same behavior with versions 3.20.x, 3.22.x and master (but must also apply to all recent Koha versions). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 17196] New: Move marcxml out of the biblioitems table
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '19

10 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17196 Bug ID: 17196 Summary: Move marcxml out of the biblioitems table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 162

[Bug 18658] New: Prevent Modify action when reserved item is awaiting collection
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '19

10 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18658 Bug ID: 18658 Summary: Prevent Modify action when reserved item is awaiting collection Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org Modify opac-modrequest.pl to have it check to see if item has arrived for collection, and either suppress Modify option to prevent users cancelling the reservation (hold) when item is ready to collect, or warn the user the reservation (hold) cannot be cancelled as it is now too late. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 16333] New: Google Calendar integration don't work
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '19

07 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16333 Bug ID: 16333 Summary: Google Calendar integration don't work Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: wosch(a)freebsd.org On the page https://koha-community.org/calendar/ is a link 'g+ Add to Google'. I tried it out and google calendar reports an error message: "This email address isn't associated with an active Google Calendar account: https://koha-community.org/?plugin=all-in-one-event-calendar&controller…. Please check the email address and try again." -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16347] New: many news articles are tagged excessively or not tagged at all
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '19

07 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16347 Bug ID: 16347 Summary: many news articles are tagged excessively or not tagged at all Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: mirko(a)abunchofthings.net The usage of categories in news posts is weird. The Koha newsletter seems to be using every category available, while 3.22 is not tagged at all. https://koha-community.org/category/release/ has mostly 3.20. Where is 3.22? Why are all the community newsletters showing up there? https://koha-community.org/category/release/3-22/ has newsletters almost exclusively. 3.22.1 is the last one listed. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 16840] New: URLs for old releases are broken with every new release
by bugzilla-daemon＠bugs.koha-community.org 07 Feb '19

07 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16840 Bug ID: 16840 Summary: URLs for old releases are broken with every new release Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: jsn.sherman(a)gmail.com I'm working up a nice CentOS 7 ansible role that builds Koha from the tarball release. The way you shuffle tarball upon release makes automating koha builds more difficult than it has to be, and is user hostile. When you move tarballs under old releases, you don't offer a redirect to the new location, instead you return a 404. When you publish content to the web, you should treat that URL as valid for as long as you have the associated content. In this case, you still have the content, and you know exactly where it is. Ideally, you would offer clients a 301 redirect to the new location. You should only return a 404 when you deleted content or honestly have no idea what the client is asking for. This is a general website stewardship issue, and it may not seem like the most critical thing when you are trying to get a release out the door, so I would be happy to contribute my expertise and/or time to improve this aspect of release management for Koha. Thanks! -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 19818] New: Add id into tag html from moremember.tt
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '19

06 Feb '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19818 Bug ID: 19818 Summary: Add id into tag html from moremember.tt Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: stephane.delaye(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In this screen /cgi-bin/koha/members/moremember.pl? I have several li tags html without id. So when I want custom the labels with the preference system 'intranetuserjs', i can't... from the record patron (memberentry.pl)...it is possible .... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33