ENPLDEES
← Zurück zu Migratorv1.3.0 (30 Releases)

Changelog Migrator

Changelog für das verfügbaren WooCommerce-Plugin Migrator: Updates, Korrekturen und Funktionsentwicklung.

v1.3.0
  • Added: **scheduled backups are now free.** Daily or weekly, with a retention rule, running unattended through WordPress cron and using the same engine as a manual backup.
  • Added: **off-site copies are now free.** Every backup can be copied to an FTP or FTPS server, or to a folder outside the web root such as a mounted drive or NAS. A backup that lives only on the machine it protects is not a backup.
  • Added: a destination registry, so an add-on contributes further destinations through the `migrator/backup_destinations` filter instead of the free plugin knowing about them.
  • Changed: the free plugin no longer stores settings it cannot act on. A backup strategy or an encryption passphrase belongs to whatever implements them.
  • Fixed: deactivating the paid add-on used to clear the backup cron event, which stopped the site's backups. Scheduling belongs to this plugin now, so it keeps running.
  • Note for existing Migrator PRO users: your schedule, retention, exclusions and off-site credentials carry over automatically, including the passwords. Nothing needs re-entering.
v1.2.18
  • Fixed: the package no longer ships its own translation files. WordPress.org builds language packs from translate.wordpress.org, and a bundled catalogue shadows that pack, so a translation corrected upstream could not reach you until the next release. Your language now comes from the language pack, which is the copy that stays current.
v1.2.17
  • Fixed: the safeguard that is supposed to stop a restore writing over Migrator's own plugin folder had never worked. It compared against the folder name the plugin used before it was renamed, so on every current installation nothing matched, and restoring an older backup could extract an older copy of the plugin over the code that was running the restore. The folder names are now taken from the installation itself, so a future rename cannot break it again.
  • Fixed: the same stale names were used to decide which plugin folders an export must never prune.
v1.2.16
  • Fixed: the plugin recorded 1.2.13 as its own version inside every archive it wrote, because the version constant had been left behind when the header was bumped. The number is stamped into the manifest of each backup and also busts the admin asset cache, so an archive said it came from an older plugin than the one that made it. The constant is now checked against the header when the package is built, so it cannot drift again.
v1.2.15
  • Fixed: the backup directory's .htaccess carried only the Apache 2.2 form of the deny rule. Apache 2.4 does not understand it without mod_access_compat, so on those servers the directory holding full database dumps had no server-level protection, leaving only the random token in the filename, which is a backstop for hosts that ignore .htaccess and not a replacement for the rule. Both forms are now written, each behind its own IfModule. An existing installation is corrected the next time the workspace is prepared.
  • Fixed: addresses stored without a scheme, in the "//host/wp-content/..." form, matched none of the replacement pairs and survived a restore still pointing at the site the backup came from. They are now rewritten with the rest.
v1.2.14
  • Fixed the PRO promo on the settings screen quoting a price in PLN. PRO is priced and charged in EUR, so an admin on a Polish site was shown a zloty amount and then billed in euro, and the zloty figure was a fixed conversion that drifted from the real charge as the rate moved. The promo now shows the euro price that is actually taken.
v1.2.13
  • Fixed: the PRO pricing line claimed a PLN price would appear during purchase. Purchases settle in EUR, so the line now says the price is billed in EUR.
v1.2.12
  • Fixed: ticking a database view under "Exclude specific database tables" now leaves it out of the backup. The list offers views alongside tables, but only tables were being skipped, so a ticked view still ended up in the archive.
v1.2.11
  • The PRO notice in the admin, and the PRO section of this readme, now list what Migrator Pro actually ships, including table sync, and say plainly that incremental backups cover files while every archive still carries the whole database. Multisite is described as network to network, which is what the admin does.
v1.2.10
  • Docs: the Multisite answer said the plugin is Multisite compatible without saying that a network restore is refused in the free edition. It now says so, and points at the Pro add-on for network migration.
v1.2.9
  • Fixed: restoring into a subdirectory doubled the new address (https://site.com/shop/shop). A site's home and site address are normally the same string, and it was rewritten twice.
v1.2.7
  • Translations: completed Polish, German and Spanish for the PRO upgrade panel.
v1.2.6
  • Readme: added a factual comparison with Duplicator and All-in-One WP Migration.
v1.2.5
  • Security: hardened backup workspace path handling against traversal (defense in depth).
v1.2.4
  • Translation quality pass: corrected Polish, German and Spanish (product names kept in English, legal withdrawal terminology, WooCommerce glossary and grammar fixes).
v1.2.3
  • Documentation: readme links are now labelled links.
v1.2.2
  • Shortened display name (dropped the Plogins prefix; slug unchanged).
v1.2.1
  • Added a contextual written migration-help link after a successful backup.
  • Fixed disk-space preflight formatting type handling.
v1.2.0
  • New: standalone serialization-safe search and replace (admin tool + dry run + `wp migrator replace`) to change a domain, URL or path without corrupting serialized data.
  • New: inspect a stored backup before restoring - shows the source URL, WordPress and PHP versions and table count, and runs pre-restore checks (table prefix, disk space, writable files).
v1.1.1
  • Added a Free vs PRO overview to the readme.
v1.1.0
  • New: in-plugin overview of Plogins Migrator PRO (incremental + scheduled backups, off-site storage, one-click cloud restore) on the admin screen.
v1.0.3
  • Clearer name: Plogins Migrator - Site Migration and Backup (it backs up and migrates the whole site, not only WooCommerce).
  • Hardened the export AJAX handler: the request payload is fully sanitized before any filter callback runs.
v1.0.2
  • Added bundled Polish, German and Spanish translations for the plugin interface.
v1.0.1
  • First stable release.
v0.3.3
  • Renamed to Plogins Migrator for a more distinctive plugin name.
v0.3.2
  • Tidier saved-backup rows: the date and size lead, the long file name is a muted single line that no longer wraps, and the row reflows neatly on narrow screens.
v0.3.1
  • Your saved backups now appear inside the "Restore a backup" card, so you can restore one in place without scrolling past it.
v0.3.0
  • New "Your backups" section: every backup stored on the site is listed with its date and size, so you can download, restore or delete it in one click without leaving the screen.
  • Restore straight from a stored backup (gzip backups are unpacked automatically). The backup file is kept, not consumed.
  • Added one-click presets to the backup screen: Full site, Database only and Media only set the right exclusions for you.
v0.2.0
  • Added a file-size explorer to the backup screen: scan wp-content, see each folder's size and file count, and tick folders or large files to leave out of the backup. Builds on the existing path exclusions.
v0.1.0
  • First release.
  • One-file backup of the database (tables, views, triggers and stored routines) and all of `wp-content`.
  • Restore to the same site, or migrate to a new host with serialization-safe URL and path rewriting.
  • Selective backup: leave out media, themes, plugins, cache, spam comments, post revisions, transients, WooCommerce sessions or Action Scheduler tables.
  • In-browser resumable export with a progress bar and a direct download, plus drag-and-drop restore.
  • WP-CLI `export` and `import` for sites too large for the browser.
  • Safety first: a pre-import database snapshot with automatic rollback if a restore fails, per-item checksums, and a refusal to import across a mismatched table prefix.
Zurück zu Migrator