Digipacket Backup Toolkit

Changelog

2.0.1

• Security now owns every superglobal read in the plugin, and hands back
  nothing until the request has proved its nonce and its capability. Handlers
  used to verify once and then read $_POST from a dozen small private helpers:
  the check did run first, but nothing in the code said so, and a reader called
  from a new path tomorrow would have read unproved input without anything
  failing. Reading input and proving the request are now the same act.
• Covered that rule with a suite, after finding that the WordPress stand-in used
  by the tests had no wp_verify_nonce at all — so every authorisation check in
  the suite had been passing on a function that did not exist.
• Removed the Nginx sample file. It protected wp-content/plugins/…/storage/,
  which has not been where the archives live since 1.6.6, so its rules guarded an
  empty directory. The correct rule is in the FAQ, pointing at the real path.
• Text domain aligned with the directory slug.

2.0.0

• Renamed to Digipacket Backup Toolkit. The plugin directory does not allow a
  standalone “WP” in a plugin’s public naming, so the display name, the slug,
  the text domain and the sidebar entry all changed. Nothing about how the
  plugin works changed with them: the storage path, the settings, the filters
  and the archives already on disk are untouched.

1.9.10

• Dropped the empty storage skeleton the package still carried from the layout
  used before 1.6.6. The storage has lived in wp-content/digipacket-backups/
  since then, where activation creates every directory and writes its own
  .htaccess and index.php; the copies inside the plugin were byte-identical
  dead weight, and one stray index.json had no business shipping at all.
• Declared compatibility with WordPress 7.0.

1.9.9

• Statistic tiles no longer cut their value short. “August 3, 2026 17:37” is what
  the default WordPress date format produces, and it does not fit a quarter of
  the screen: every date tile ended in an ellipsis. The value wraps instead.
• Refreshed the screenshots of the listing.

1.9.8

• The dashboard card no longer outlines itself in amber when it has a warning to
  give — “Backups are not encrypted” and its siblings. The dot beside the title
  already says it.

1.9.7

• The ⋮ menu of a row is no longer cut off by the table. It was positioned
  inside the wrapper that scrolls the table sideways, and anything positioned
  inside a box with overflow set is clipped by it: everything past the third
  entry disappeared at the edge. It now floats above the screen, opens upward
  when the row sits near the bottom of the window, and closes when the page
  scrolls under it.

1.9.6

• Scheduled backups now run. Every one of them was dying on the same line:
  WP-Cron runs with nobody logged in, WordPress answers that with a user whose
  login is false rather than an empty string, and five copies of the same
  three-line method returned it from a function declared to return a string. The
  resulting TypeError killed the request before the backup had recorded
  anything, so the task kept its lock, wrote no failure, and did nothing —
  silently, every five minutes.
• There is now one place that answers “who triggered this”, it answers “system”
  when nobody did, and a test runs a whole scheduled backup as nobody.

1.9.5

• A scheduled run now writes down what killed it. A backup that runs at three in
  the morning has no witness: when the request carrying it dies — memory
  exhausted, execution time exceeded, a fatal error in another plugin — every
  line it would have written dies with it, and the journal shows a start
  followed by silence. The plugin now arms a witness before touching the engine
  and records the fatal, with its message, its file and its line.
• Anything thrown out of the engine is caught and recorded as a failure of the
  task, instead of ending the request without a word.

1.9.4

• A run whose request is killed before it can record what it started no longer
  jams its task. The lock it left behind was held for its full fifteen minutes,
  the task started again, died in the same place and waited again — a loop that
  produced nothing and reported nothing, while the journal read
  “skipped: locked” every five minutes.
• A lock with no run behind it is now taken back after two minutes, and the
  journal says so as a warning, with what to look at next.

1.9.3

• The Scheduled Backups screen now says when WP-Cron is not firing at all, and
  when the scheduler was last woken up. A site whose loopback request is blocked
  — a local install, a firewall, an HTTP password — ran nothing and said nothing,
  which is indistinguishable from a plugin that does not work.

1.9.2

• A paused scheduled backup now says so at the top of the screen, and says how
  to resume it. It used to sit in a column with a “Next run” that had already
  gone by, which reads exactly like a backup that failed silently.
• A paused task no longer advertises a next run it will never honour.
• The Status column says “Active” rather than “Running”: “Running” also meant a
  backup being written at that moment, and one word could not carry both.
• The next run is printed on the clock of the site, like the tile above it. The
  two disagreed by the offset of whoever was looking at the screen.

1.9.1

• A scheduled backup can now be given the hour it starts at, and a weekly one
  the days it runs on. The hour is read in the timezone of the site and follows
  it through daylight saving; a hand written cron expression is still read in
  UTC, as it always was.
• Fixed the ⋮ menu of the task table and of the Backup Manager. It opened and
  closed on the same click, which made every row action unreachable.

1.9.0

• Backups are named after the day they were taken — “Backup Aug 01, 2026” —
  in the library, the restore wizard and the Security screen. The identifier
  stays what it always was: it names the file on disk, it is still what every
  action uses, and it is shown in the detail card.
• A backup you renamed keeps the name you gave it.
• Searching matches what the row reads, and still matches the identifier.

1.8.2

• A scheduled backup that could not start because another backup was already
  running is no longer reported as a failure. It kept its failure count, and it
  pushed the next run to the following day — so one abandoned manual backup cost
  a whole night. The task now waits and starts on its own at the next tick.
• Failure notices say why. “Scheduled backup X failed.” carried no cause, and
  the reason sat in the journal where nobody was told to look.

1.8.1

• The administration canvas is now a pale wash instead of white, so the cards
  read as surfaces sitting on top of it. The cards themselves stay white.
• The footer credit reads “Built by dynetwork”.

1.8.0

• Rebuilt the interface on a single design system: one file now holds every
  colour, radius, shadow, spacing step and duration, and every screen paints
  from it. A test refuses any value written anywhere else.
• White canvas, white surfaces separated by hairline borders, one blue for
  anything actionable, and more room between things.
• Icons throughout: the statistic tiles, the card headings and the main actions
  now carry an inline Lucide icon. Nothing is fetched from a third party.
• Motion is uniform: every transition now runs between 150 and 200ms, and the
  whole interface stops moving when the system asks for reduced motion.
• Fixed the labels of the Settings and Security checkboxes, which were printed
  bold and broken onto two lines.
• Fixed the Security screen’s own styles, which had never applied: the rule that
  carried them could not match the element it was written for.

1.7.3

• The plugin now signs its own screens: “Built by dynetwork.net” replaces the
  WordPress footer sentence on its pages, and nowhere else.

1.7.2

• Added a support link, on the plugins list and on the Logs screen.

1.7.1

• Fixed the “Delete this journal” button on the Logs screen: red text on a red
  block, which is to say no button at all.

1.7.0

• Added the Logs screen: read any journal by severity or by search, delete one, or
  clear the ones older than the retention rule.
• Dates now read as dates. The dashboard, the Security screen and the schedule
  table were printing raw ISO timestamps, which overflowed their tiles.
• Schedule states read as words instead of machine values.
• “Last archive” on the New Backup screen showed 0 B instead of the real size.
• Added the Settings screen. The uninstall preference existed since the first release
  and no screen offered it: you could never turn it on, nor be sure it was off.
• Encrypting or decrypting an archive is now written to the security journal.
• The Security dashboard repaints after every action instead of showing stale figures.
• Added skeleton loading and icons to the Security screen.

1.6.7

• The Type, Status and Integrity badges now read as words instead of machine values.

1.6.6

• Backups are no longer stored inside the plugin directory. Updating the plugin
  used to delete them. They now live in wp-content/digipacket-backups/, and anything
  left by an older layout is carried over on activation.

1.6.5

• Added a download button on every row of the Backup Manager.

1.6.4

• Added a delete button on every row of the Backup Manager.

1.6.3

• Fixed the Restore screen hanging forever on “Analyse this backup”.

1.6.2

• Fixed the Restore screen listing no backup at all.

1.6.1

• Fixed unreadable panels on machines using a dark system theme.
• The dashboard now reports the real state of the site instead of a placeholder.
• Plugin updates now run the installation routine again.

1.6.0

• Added encryption: AES-256-GCM, keyring, master password, key rotation, migration of
  existing backups, and transparent decryption on import and restore.

1.5.0

• Added scheduled backups, retention rules, run history and notifications.

1.4.0

• Added the Backup Manager: search, filters, sorting, integrity checks and downloads.

1.3.0

• Added the restore engine, with preflight checks, safety snapshot and rollback.

1.2.0

• Added the import of archives produced on another site.

1.1.0

• Added the backup engine.

1.0.0

• First release.