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

[Bug 18710] New: Wrong subfield modified in batch item modification
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '19

17 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18710 Bug ID: 18710 Summary: Wrong subfield modified in batch item modification Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In Tools > Batch item modification, one can modify or delete a subfield. When deleting a subfield et modifying another, the wrong subfield gets modified. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 20216] New: Editing itemtypes does not pull existing values correctly
by bugzilla-daemon＠bugs.koha-community.org 11 Oct '19

11 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20216 Bug ID: 20216 Summary: Editing itemtypes does not pull existing values correctly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: System Administration 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 - Edit an item type, define a replacement cost,processing fee, and remote image url 2 - Save the item type 3 - Values are correct in list 4 - Edit again 5 - note values in fields are not populated 6 - Save itemtype, values are lost -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 16111] New: RSS feed for OPAC search results has wrong content type
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '19

10 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16111 Bug ID: 16111 Summary: RSS feed for OPAC search results has wrong content type 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: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org As a result of (ancient) commit f6e1214c, OPAC search result RSS feeds come over with the content type text/html. It should be at least text/xml, and with the demise of Internet Explorer 6, arguably application/rss+xml. The cause: prior to that commit, setting the CGI parameter format to rss2 resulted in passing "rss" as the content type parameter to output_with_http_headers; after that commit, rss2 was no longer properly recognized when setting that parameter. The main user-visible consequence is that clicking on the RSS link in Chrome (when no feed-reader plugin is installed) renders the feed as HTML rather than XML. -- You are receiving this mail because: You are watching all bug changes.

1 115

[Bug 19066] New: Add branchcode to accountlines
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '19

09 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19066 Bug ID: 19066 Summary: Add branchcode to accountlines Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com For the purposes of statistics, it appears that it would help many libraries to have branchcode recorded in the accountlines table. For payments, the field would contain the code for the branch the payment was made at. For manual invoices, it would be the code of the library that created the invoice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 136

[Bug 19238] New: CORPO_NAME authority file ignores first indicator of new headings saved
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '19

09 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19238 Bug ID: 19238 Summary: CORPO_NAME authority file ignores first indicator of new headings saved Change sponsored?: --- Product: Koha Version: master 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: imingchan(a)yahoo.com.au QA Contact: testopia(a)bugs.koha-community.org When saving new headings to CORPO_NAME authority, first indicator value is not saved. So when you selected such authority heading (as part the cataloguing), you have to manually re-enter the indicator value concerned. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 18893] New: The dateformat sys pref not used everywhere
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18893 Bug ID: 18893 Summary: The dateformat sys pref not used everywhere Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: fiona.borthwick(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr The dateformat system preference is set to dd/mm/yyyy but this does not carry through to every screen. Examples noted are: Batch item modification - after entering barcodes the second screen shows date formats as 2017-07-03 Also the specific due date helper in checkout displays the chosen date in a different format. It should be consistent. Tested at 16.11 and 17.05. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 18707] New: Background jobs post disabled inputs
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '19

08 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18707 Bug ID: 18707 Summary: Background jobs post disabled inputs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org For example, in Tools > Batch item modification input of deleted subfields are disabled. This form is posted using background job via JS code. Looks like this JS code converts a POST form into a GET URL, including inputs that are disabled : koha-tmpl/intranet-tmpl/prog/js/background-job-progressbar.js function submitBackgroundJob(f) { ... $(':input', f).each(function() { ... -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 18514] New: Allow library to search their Koha and Overdrive collections using ElasticSearch
by bugzilla-daemon＠bugs.koha-community.org 04 Oct '19

04 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18514 Bug ID: 18514 Summary: Allow library to search their Koha and Overdrive collections using ElasticSearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org Building on the Elasticsearch and Overdrive work, this feature will allow users to run a cronjob to populate their elastic index with collection information from Overdrive. This makes both local Koha records, and Overdrive ones searchable. This bug will add the code to fetch and index the records, and to search and display them in the OPAC Subsequent bugs will add the detail display to the staff side -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 18969] New: Elasticsearch - _all field is deprecated - should use copy_to to prepare for ES6
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '19

02 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18969 Bug ID: 18969 Summary: Elasticsearch - _all field is deprecated - should use copy_to to prepare for ES6 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P3 Component: Searching Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Reindex on a clean ES, you get a warning: [DEPRECATION] 299 Elasticsearch-5.4.1-2cfe0df "field [include_in_all] is deprecated, as [_all] is deprecated, and will be disallowed in 6.0, use [copy_to] instead." -- You are receiving this mail because: You are watching all bug changes.

1 47

[Bug 20335] New: Stage MARC records for import does not work under Plack
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '19

16 Sep '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20335 Bug ID: 20335 Summary: Stage MARC records for import does not work under Plack Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: arouss1980(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In a vanilla 17.11.03 installation with Plack enabled, attempting to stage a MARC record for import fails with a pop-up message that reads: "Failed to submit form: error". In intranet-error.log the following information appears: stage-marc-import.pl: /usr/share/koha/intranet/cgi-bin/tools/stage-marc-import.pl: cannot open input file /tmp/koha_hax_upload/3f11cee01b610984d5dbd6430106d173_koha.mrc: No such file or directory The permissions of the directory and file above are as follows: drwxr-xr-x 2 hax-koha hax-koha 4096 Mar 5 16:18 /tmp/koha_hax_upload -rw-r--r-- 1 hax-koha hax-koha 1058 Mar 5 16:18 /tmp/koha_hax_upload/3f11cee01b610984d5dbd6430106d173_koha.mrc To reproduce, simply enable Plack in a vanilla 17.11.03 installation, then go to Home -> Tools -> Stage MARC records for import, browse for a file, hit the "Upload file" button, and then click the "Stage for import" button. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2