Bug 37185 - Notices won't pull in database fields
Summary: Notices won't pull in database fields
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: 24.05
Hardware: All All
: P5 - low major
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-25 17:12 UTC by Sara Brown
Modified: 2025-06-02 20:46 UTC (History)
0 users

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sara Brown 2024-06-25 17:12:10 UTC
In 24.05, if I create a new notice or edit an existing one and try to insert database fields, there are two problems:

1) They don't pull into the notice using the 'Insert' button

2) If I manually type fields into the notice, the added fields are not included when the notice sends

To recreate:
-Select an existing notice (I tried CHECKOUT)
-Try to use 'Insert' to add a field (I tried <<branches.branchphone>> after the library's name) - note that it does not copy over
-Manually type the field into the notice - note that it saves with the typed field
-Trigger the notice
-View the notice in the patron's account - note that the added field is not there
Comment 1 Sara Brown 2024-06-25 17:15:39 UTC
I saw 37059 after submitting this, but that one doesn't describe the issue with data not pulling in for manually-added fields. That might also be fixed by the patch, but I'm not able to tell.