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

[Bug 34410] New: Allow for alternative or better customization of items.content in digest notices
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34410 Bug ID: 34410 Summary: Allow for alternative or better customization of items.content in digest notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The PREDUEDGST and DUEDGST use the <<items.content>> syntax to define the repeatable parts of those notices. I have often heard the complaint that this is not flexible enough and makes for somewhat confusing notices. Many libraries would like to be able to make these digest notices looks something like this: TITLE: Abc AUTHOR: Cba DUE DATE: 07/25/23 This is not possible using items.content. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 33901] New: Only one issue shown in Test prediction pattern
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33901 Bug ID: 33901 Summary: Only one issue shown in Test prediction pattern Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I think this is similar to bug 32554, but in another page/context. When creating a numbering pattern, you have the option to test it before saving it. However, it doesn't show the number of issues you select in the test. To recreate: 1. Go to Serials > Manage numbering patterns 2. Click Edit next to one of the existing patterns (e.g. Number) 3. Enter information in the Test prediction pattern section - Frequency: choose one (e.g. 1/month) - First issue publication date: enter a date (e.g. 2023-06-01) - Subscription length: issues + enter a number of issues (e.g. 12) - Locale: leave empty - Begins with: enter a number in the X column, e.g. 42 4. Click Test pattern --> Only one issue is shown, no matter how many you enter in Subscription length. Having only one issue doesn't help at all to know if your numbering pattern will work correctly. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 19192] New: Update default DUEDGST and PREDUEDGST notices
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19192 Bug ID: 19192 Summary: Update default DUEDGST and PREDUEDGST notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The current default digest notices are DUEDGST You have <<count>> items due PREDUEDGST You have <<count>> items due soon These are not terribly useful defaults -- the whole reason for having digest notices is to display item detail for items which are due or coming due. I suggest the following instead: DUEDGST Dear <<borrowers.firstname>> <<borrowers.surname>>, You have <<count>> items due: <<items.content>> PREDUEDGST Dear <<borrowers.firstname>> <<borrowers.surname>>, You have <<count>> items due soon: <<items.content>> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 1993] Task Scheduler Needs Re-write
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993 --- Comment #59 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to David Cook from comment #58) > As Martin has noted elsewhere: > > (In reply to Martin Renvoize from comment #6) > > I've long felt our use of 'at' in scheduler was wrong, but we've not had a > > reasonable alternative. We now have BackgroundJobs and I could see us using > > that system as an alternative to using 'at' and calling a script. > > I agree about using BackgroundJobs for the execution. > > We'll still need a scheduler, and I think the shortest path forward is a > cronjob-based scheduler script, which polls the database every X interval > looking for jobs to run. If we do this, could we make it work for scheduled repeated sending? I am thinking of something like daily, on a specific day of the week, first of the month, etc. and also a time for each of those. A specific time might not work I guess or at least not exactly. Maybe something like "after 8:00" and then the first cron run after that time would run it and set a 'last run on' date? -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 34416] New: Upgrade error bug
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34416 Bug ID: 34416 Summary: Upgrade error bug Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: afrane55(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Upgrade to 23.05.00.002 [10:11:46]: Bug 21983 - Deleted biblio handling on ILL Added column 'illrequests.deleted_biblio_id' ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate key name 'illrequests_bibfk' at /usr/share/koha/lib/C4/Installer.pm line 741 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 33241] New: Manual: Typo "Records changed to recalls"
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33241 Bug ID: 33241 Summary: Manual: Typo "Records changed to recalls" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org "Records changed to recalls" in the FAQ section should be "changes". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31872] New: Remove warning in cron-jobs section of the manual about needing StaticHoldsQueueWeight to use RandomizeHoldsQueueWeight
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31872 Bug ID: 31872 Summary: Remove warning in cron-jobs section of the manual about needing StaticHoldsQueueWeight to use RandomizeHoldsQueueWeight Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Cron jobs section of the manual (https://koha-community.org/manual/22.05/en/html/cron_jobs.html#circulation) still contains the warning: "Leaving StaticHoldsQueueWeight empty is contraindicated at this time. Doing so will cause the build_holds_queue script to ignore RandomizeHoldsQueueWeight, causing the script to request hold fulfillment not randomly, but by alphabetical order." This warning was removed from other sections of the manual in bug 22846 but seems to have survived here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 29248] New: Manual 21.05 - 'position' missing in syspref UNIMARCAuthorityField100
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29248 Bug ID: 29248 Summary: Manual 21.05 - 'position' missing in syspref UNIMARCAuthorityField100 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: e.betemps(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, Translating syspref in this manual, I think some positions are missing Emplacements : ../../source/authoritiespreferences.rst:189 Asks: Use the following text for the contents of UNIMARC authority field 100 position ??? (fixed length data elements). have a nice day, Manu. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 34419] New: koha-plack contains a wrong test about missing Apache modules
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34419 Bug ID: 34419 Summary: koha-plack contains a wrong test about missing Apache modules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org All needed Apache modules are installed but koha-plack tells me: WARNING: koha-plack requires some Apache modules that you are missing. You can install them with: sudo a2enmod headers proxy_http This really is not true. What happened? There is a syntax error in one of my local sed changes in a config file. Looking a bit deeper, I see this test in sub check_env_and_warn() if ! /usr/sbin/apachectl -M 2> /dev/null | grep -q ${module}; then missing_modules="${missing_modules}${module} " fi Altough the grep -q part looked mysterious to me at first, the problem seems to be the pipe. If the first process exits with an error, the second will have an error too on the closed handles. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 33717] New: Typo in search_for_data_inconsistencies.pl
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '23

26 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33717 Bug ID: 33717 Summary: Typo in search_for_data_inconsistencies.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz If a biblio has no title, the script output reads == Biblio without title 245$a == * Biblio with biblionumber=768 does not have title defined => Edit these biblio records to defined a title "defined" in the last sentence should be "define" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11