Event badges, json may be broken (was CiviEvent - Date tokens may be misformatted)
(This is an offshoot from #3829 (closed). PR 24695 bundled in a partial fix for this date-token issue, but it looks to me like this is distinct from the barcode problem - and this still has some TODOs.)
v5.43 included an update for certain tokens. It recommended adding an explicit date filter:
-
{event.start_date}
=>{event.start_date|crmDate:"%B %E%f}
-
{event.end_date}
=>{event.end_date|crmDate:"%B %E%f}
Notably, the default content in civicrm_print_label
.data
has references to these tokens. It was updated by way of 873bfeb503caa413f17460 (see FiveFortyThree.php
and civicrm_navigation.tpl
). However, the data
field have special encoding requirements (JSON?), so it's not a simple string-substitution.
With 24695, it sounds like the escaping is fixed for new installs (5.54.1+). However, we probably need a cleanup/upgrade step for sites which either (a) installed 5.43-5.54 or (b) installed <5.43 and ran the upgrade.