Skip to content

v2026.10.07.8 – v2026.10.08.01 — 2026-10-08

  • merge: schedule hours name the panel server's zone, and the retention text is one key per language
  • merge: a restored customer config is checked by directive and path, not by bytes
  • merge: the stall watchdog judges progress by restic's own counters
  • fix(backup): a customer config restore refuses vhost and include files that leave the customer's area, naming file, line and directive
  • fix(backup): the stall watchdog judges a run by restic's own progress counters instead of the bytes it moves
  • fix(i18n): the retention of a schedule is one key with the number as a parameter in every language
  • docs(backup): the customer documentation and the schema say the schedule hour is read in the panel server's time zone, not UTC
  • docs(audit): investigate and decide what a forged restore snapshot can set inside the customer path
  • merge: the audit log names the acting person and reports schedule times in the schedule's zone
  • merge: backup quick view, log ordering and pool rendering from the panel
  • feat(audit): the log sorts on the server by the columns the endpoint allows, and the user column names a person, a system process or only an id
  • docs(notes): measure what customer vhosts contain beyond the template and propose a content check for restored configs
  • docs(notes): record the audit log baseline of the test box before the user-name fix
  • fix(audit): the audit log names the acting person
  • docs(notes): the interface fixture on the test box is removed
  • feat(backup): the count of older snapshots names its source and time, and deleting history entries says the backups stay
  • fix(backup): a restore report counts databases, not problems, and a config-only restore no longer claims files and databases came back
  • docs(notes): fixture cases for the backup interface on the test box and the cancel chain from the button to the audit entry
  • fix(backup): the quick view of the snapshots no longer reports zero legacy snapshots where the repository holds them, and says where its count comes from
  • fix(logs): the audit log and the notification log list the newest entries first unless an order is asked for
  • fix(prestashop): a direct link to one installation opens it instead of saying there are none
  • fix(a11y): ten of seventeen settings sections had unnamed switches, inputs or a low-contrast tag, and the gate only ever scanned the default section
  • docs(notes): re-measure the full and mail restore of the testing build, with the foreign-path snapshot and the server restore
  • docs(changelog): add the testing pill for v2026.10.07.07
  • fix(backup): after a config restore the customer's PHP pool is rendered from the panel instead of being read from the snapshot