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

[Bug 11583] Add WYSIWYG editor for HTML notices/letters
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '24

25 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11583 --- Comment #18 from David Cook <dcook(a)prosentient.com.au> --- Hmm... take a look at the premium TinyMCE plugin called "Merge Tags". That sounds interesting... I just tried out its CodePen... and I couldn't get <<Client.Name>> to work but << Client.Name >> looks pretty good in the TinyMCE visual editor. That said, in the source code editor it looks like << Client.Name >> And [%Client.Name => 'stuff' %] gets turned into [%Client.Name => 'stuff' %] Maybe it does something fancy at load/save time, but I doubt it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 11583] Add WYSIWYG editor for HTML notices/letters
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '24

25 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11583 --- Comment #17 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Sally Lodico from comment #15) > I rarely bother with TinyMCE. I find it to be more trouble than it's worth, > but the newer template designers, like https://grapesjs.com/, would make > creating responsive and email ready notices a dream. I'd much rather have a > tool like this than a WYSIWYG. TinyMCE does drive me crazy... I hadn't heard of GrapesJS but it looks interesting. It's actually like you read my mind. I was wondering what FOSS options there were for block content editing like this... -- Unfortunately, at a glance, it would have the same problem as TinyMCE. If you type in <<borrowers.firstname>> into a text block it will turn it into <<borrowers.firstname>> It's not just the <<>> syntax; it's also the Template Toolkit syntax. There's times we do things like [% stuff = { 'this' => 'that' } %] which could be turned into [% stuff = { 'this' => 'that'} %] But maybe GrapesJS is more customizable than TinyMCE. But I think it would be very challenging or impossible with GrapesJS too. -- We were probably overambitious using Template Toolkit in Notices after all. Many email templates could be done using a simple token replacement system, but AUTO_RENEWALS heavily requires Template Toolkit logic. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 14007] Values listed in OpacHiddenItems should not appear in OPAC facets
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '24

25 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14007 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #173243|0 |1 is obsolete| | --- Comment #33 from David Nind <david(a)davidnind.com> --- Created attachment 173309 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=173309&action=e… Bug 14007: Filter search result values to remove OpacHiddenItems values This change filters the values from the OpacHiddenItems syspref out of their corresponding search results facets. Note: This does not mean that all values from hidden items are filtered out of facets. Rather, it just means that facet data that matches OpacHiddenItems is filtered out. This is an imperfect fix, but it is a practical fix that has been requested by more than one library. Test plan: 0. Apply the patch and koha-plack --restart kohadev 1. Go to http://localhost:8081/cgi-bin/koha/catalogue/detail.pl?biblionumber=29 2. Add an item with an item type of "Maps" 3. Go to http://localhost:8081/cgi-bin/koha/admin/preferences.pl?op=search&searchfie… 4. Fill in OpacHiddenItems with the following: itype: ['MP'] 5. Go to http://localhost:8080/cgi-bin/koha/opac-search.pl?idx=&q=test&weight_search… 6. Note that "Maps" does not appear in the "Item types" facet 7. Go to http://localhost:8081/cgi-bin/koha/catalogue/search.pl?q=test 8. Note that "Maps" does appear in the "Item types" facet 9. ***Repeat this test plan using both Elasticsearch and Zebra indexing*** 10. prove -v t/Koha/SearchEngine/Search.t Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14007] Values listed in OpacHiddenItems should not appear in OPAC facets
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '24

25 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14007 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38086] New: UpdateItemLocationOnCheckin could be the return date
by bugzilla-daemon＠bugs.koha-community.org 25 Oct '24

25 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38086 Bug ID: 38086 Summary: UpdateItemLocationOnCheckin could be the return date Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When an items is returned, a library may have the UpdateItemLocationOnCheckin system preference set to CART. This is generic, and could be more useful. Some libraries might like the option of putting something like "Returned 4/10/2024" in place of CART. So, in UpdateItemLocationOnCheckin, instead of entering _ALL_: CART instead, we could enter something like _ALL_: RETURNDATE -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 38269] New: additem.pl subfield c shows item location instead of permanent location
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '24

24 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38269 Bug ID: 38269 Summary: additem.pl subfield c shows item location instead of permanent location Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This is confusing, when editing an existing item that was recently returned. It should only show the item.permanent_location field, not the item.location field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 24570] New: Cart location showing/duplicated when editing item
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '24

24 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24570 Bug ID: 24570 Summary: Cart location showing/duplicated when editing item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using the CART location to show recently returned items, that location displays in field c when editing or duplicating the item. This causes problems with cataloging as it will cause that location to permanently be assigned to that item or duplicated items. Field c should be reflecting the location in the permanent_location field, not the location field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 38267] New: Option to show a default cover image if no cover image is returned from source
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '24

24 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38267 Bug ID: 38267 Summary: Option to show a default cover image if no cover image is returned from source Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org It could be some default cover that we store in Koha, or perhaps a rectangle with the title text in it? -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 11583] Add WYSIWYG editor for HTML notices/letters
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '24

24 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11583 Michelle Spinney <mspinney(a)clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mspinney(a)clamsnet.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38223] New: Exporting holds from patron record lists all libraries in 'Pickup at' column
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '24

24 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38223 Bug ID: 38223 Summary: Exporting holds from patron record lists all libraries in 'Pickup at' column Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface 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 When exporting the holds table from a patron's record the dropdown for pickup locations is exported as a string of all libraries with (current) next to the selection To recreate: 1 - Place a few holds for a patron 2 - View their record in the staff interface 3 - Click the holds tab 4 - Click 'Export' - as CSV 5 - Open the downloaded file and view the Pickup at column -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1