Trilobita

DocVault Migrator Changelog

DocVault Migrator version history

Version 1.12.0

Released: 10 November 2026

  • New: Download Monitor as a source, with its download links and shortcodes kept working ([downloads] needs Trilobita DocVault 1.6.1).
  • Security: when migrating from another install, the source site’s custom uploads folder setting is used only if it lies inside that site’s WordPress folder.

Version 1.11.2

Released: 5 November 2026

  • Change: the notices shown when Trilobita DocVault is missing or too old now appear only on the Plugins screen, and the one-time access-repair notice can be dismissed.

Version 1.11.1

  • Change: “Tested up to” is declared in the readme only, as WordPress.org requires.

Version 1.11.0

  • New: a notice on the migrator page when Trilobita DocVault is older than 1.6.0, explaining that old links start working once DocVault is updated.
  • Security: source file paths can no longer point outside the WordPress Download Manager upload folder.
  • Security: the table prefix read from another site’s wp-config.php is validated before use.
  • Fix: malformed data in the source database can no longer stop a preview or migration.
  • New: records the rules Trilobita DocVault 1.6.0 needs to keep old WordPress Download Manager shortcodes and URLs working. Sites migrated with 1.10.0 to 1.10.2 get them automatically on update.
  • New: asks for confirmation before migrating from a second site of the same plugin, because old links from two sites can collide.
  • New: WordPress Download Manager tags are migrated, and old tag shortcodes and tag pages keep working.
  • New: test run. Migrate only the first few files that are ready to migrate, check the result, roll it back, then migrate everything.
  • New: rollback also removes the categories the migration created (if empty) and the information DocVault used to keep the old links working, so the site is back to how it was before the migration.
  • Change: batches end early when a package has very large files, so a migration no longer risks a PHP timeout on shared hosting.
  • Change: documents are no longer added to an existing category that holds other content, such as blog posts. A separate “(documents)” category is created instead, and the preview tells you which.
  • Change: requires WordPress 6.5 or later.
  • Removed: WP Filebase support and the Filebase References page. WP Filebase has not been maintained for years.
  • Change: code tidy-ups for WordPress.org.
  • Fix: all admin messages can now be translated.

Version 1.10.2

  • Security: package data read from the source database can no longer create PHP objects.

Version 1.10.1

  • New: categories record their original slug, so DocVault can redirect old category URLs.

Version 1.10.0

  • New: every migrated document and category records its source, so Trilobita DocVault can keep old links, shortcodes and URLs working.
  • Fix: categories were not migrated on sites where DocVault uses the standard post categories.
  • Fix: “first file only” migrations recorded incomplete log entries.
  • Fix: Filebase References could match documents migrated from WordPress Download Manager.
  • Change: DocVault Pro is no longer required. The dry run shows which skipped file types Pro can add.

Version 1.9.11

  • Fix: role restrictions from WordPress Download Manager are now saved correctly. Documents migrated with earlier versions are repaired automatically.