The action_trigger event def template for printing acq invoices was
syntatically broken. The collapse filter isn't important per se, but
it balances the extra [% END %] at the bottom of the template, and it
was there originally, and I see no reason not to put it back.
Incidentally, maybe the database upgrade script in the commit will be
the first in master to successfully use the new
evergreen.upgrade_deps_block_check() function ?
Reported by Sally Fortin.
Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
install_date TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT NOW()
);
-INSERT INTO config.upgrade_log (version) VALUES ('0535'); -- dbs
+INSERT INTO config.upgrade_log (version) VALUES ('0538'); -- senator
CREATE TABLE config.bib_source (
id SERIAL PRIMARY KEY,
'ProcessTemplate',
'print-on-demand',
$$
+[% FILTER collapse %]
[%- SET invoice = target -%]
<!-- This lacks general refinement -->
<div class="acq-invoice-voucher">
--- /dev/null
+BEGIN;
+
+SELECT evergreen.upgrade_deps_block_check('0538', :eg_version); -- senator
+
+UPDATE action_trigger.event_definition
+SET template = '[% FILTER collapse %]' || template
+WHERE id = 22 AND
+ SUBSTR(template, 0, 24) NOT LIKE '%FILTER collapse%';
+
+COMMIT;