chore(template): tie the version to our tag counter #20

Merged
fabrice.kirchner merged 1 commit from chore/template-version-cache-buster into main 2026-11-21 20:11:33 +01:00
Owner

NOVA appends <Version> to every CSS and JS file as ?v=<version>, and
the shop serves those files with Cache-Control: max-age=31536000. Tag
v5-8-0-4 changed js/custom.js, but custom.js?v=5.8.0 stayed the
same, so a browser holding the old file would not fetch the new one for
up to a year and the mail delay notice of #19 would not reach returning
customers. Measured on 21.11.2026 against the production shop.

The first three digits follow the NOVAChild version of JTL, the fourth
is the counter of our own tags, so v5-8-0-5 carries 5.8.0.5.

  • template.xml: version 5.8.0 to 5.8.0.5
  • README.md: new section on the version and the cache buster

Effects: the next init run reactivates the template and writes the new
version into ttemplate. Every CSS and JS URL of both production shops
changes once, so those files are fetched again; the pages themselves are
unaffected. No change for anyone who switches the notice off later.

Tests: verified in cdp-testshop with this template.xml in place.
reactivate_template.php check read version 5.8.0.5 and found the
parent, apply wrote NOVAChild | standard | 5.8.0.5 into ttemplate
and left the template active. The registration page renders with HTTP
200, 281 KB and the usual title, now with js/custom.js?v=5.8.0.5 and
my-nova.css?v=5.8.0.5, and the notice element of #19 is still in place,
so the settings in ttemplateeinstellungen survived the reactivation.

Side note: the pre-commit hook no-infra-leaks reads the four-digit
version as an IPv4 address. The line carries an infra-leak-ok marker;
the hook could skip version numbers in backticks instead.

Nach dem Merge: Tag v5-8-0-5 und TEMPLATE_REF in
fabrice.kirchner/k3s-prod nachziehen, dann je Shop den Hinweis
einschalten.

NOVA appends `<Version>` to every CSS and JS file as `?v=<version>`, and the shop serves those files with `Cache-Control: max-age=31536000`. Tag `v5-8-0-4` changed `js/custom.js`, but `custom.js?v=5.8.0` stayed the same, so a browser holding the old file would not fetch the new one for up to a year and the mail delay notice of #19 would not reach returning customers. Measured on 21.11.2026 against the production shop. The first three digits follow the NOVAChild version of JTL, the fourth is the counter of our own tags, so `v5-8-0-5` carries `5.8.0.5`. - template.xml: version 5.8.0 to 5.8.0.5 - README.md: new section on the version and the cache buster Effects: the next init run reactivates the template and writes the new version into `ttemplate`. Every CSS and JS URL of both production shops changes once, so those files are fetched again; the pages themselves are unaffected. No change for anyone who switches the notice off later. Tests: verified in cdp-testshop with this template.xml in place. `reactivate_template.php check` read version 5.8.0.5 and found the parent, `apply` wrote `NOVAChild | standard | 5.8.0.5` into `ttemplate` and left the template active. The registration page renders with HTTP 200, 281 KB and the usual title, now with `js/custom.js?v=5.8.0.5` and `my-nova.css?v=5.8.0.5`, and the notice element of #19 is still in place, so the settings in ttemplateeinstellungen survived the reactivation. Side note: the pre-commit hook no-infra-leaks reads the four-digit version as an IPv4 address. The line carries an infra-leak-ok marker; the hook could skip version numbers in backticks instead. Nach dem Merge: Tag `v5-8-0-5` und `TEMPLATE_REF` in fabrice.kirchner/k3s-prod nachziehen, dann je Shop den Hinweis einschalten.
chore(template): tie the version to our tag counter
All checks were successful
Freeze Gate / freeze-gate (pull_request) Successful in 13s
43e88fdf16
NOVA appends <Version> to every CSS and JS file as ?v=<version>, and the
shop serves those files with Cache-Control: max-age=31536000. Tag
v5-8-0-4 changed js/custom.js, but custom.js?v=5.8.0 stayed the same, so
a browser holding the old file would not fetch the new one for up to a
year, and the mail delay notice would not reach returning customers.

The first three digits follow the NOVAChild version of JTL, the fourth
is the counter of our own tags, so v5-8-0-5 carries 5.8.0.5.

- template.xml: version 5.8.0 to 5.8.0.5
- README.md: section on the version and the cache buster
fabrice.kirchner deleted branch chore/template-version-cache-buster 2026-11-21 20:11:33 +01:00
Sign in to join this conversation.
No description provided.