ENPLDEES
Zurück zu Migratorv1.5.1 (41 Releases)

Changelog Migrator

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

v1.5.1
  • Fixed: the PRO card on the settings screen no longer presents moving a site between servers as PRO-only; the free plugin does it with `wp migrator pull`, PRO adds the wp-admin screen.
v1.5.0
  • Added: Pull and Push. Copy a live site to another server over HTTP with `wp migrator pull`, resume an interrupted pull, fetch only the changes on the next run, and send file changes back with `wp migrator push`. Off until you switch it on.
  • Added: `wp migrator remote` runs the low-level transfer commands, such as keygen, files-stats or db-push.
  • Added: a pull checks the disk space it needs before it starts, leaves the old host's platform plugins and server-bound drop-ins (object cache, page cache, database driver) behind, and keeps the database password out of the process list.
  • Changed: server-to-server transfer is now part of the free edition.
v1.4.0
  • Fixed: backups no longer alter `%` characters in the database. In 1.3.8, permalink structures, text such as "50%" and serialized values containing `%` were damaged on restore.
  • Fixed: scheduled backups, retention, and the FTP and folder copies now run in the free edition. They were not wired up from 1.3.0 to 1.3.8.
  • Fixed: database dumps are charset-safe on latin1 and utf8mb3 databases.
  • Fixed: collations from MySQL 8 and MariaDB 11 sources are normalised.
  • Fixed: a file that changes during a backup no longer corrupts the archive, and the archive is verified before a restore touches the database.
  • Fixed: off-site retention deletes only this site's backups.
  • Fixed: home and siteurl are correct after a restore of WordPress installed in a subdirectory.
  • Fixed: JSON values are preserved during the URL rewrite.
  • Fixed: the object cache is flushed after every kind of restore.
  • Fixed: unreadable files are skipped.
  • Fixed: interrupted scheduled backups are now visible.
  • Fixed: downloading a large archive no longer runs out of memory.
  • Fixed: the Download buttons in the stored backups list no longer return an error.
  • Changed: wp-content/debug.log is left out of backups, and an uploads folder outside wp-content is reported before export.
  • Fixed: import error messages are readable and translatable.
  • Fixed: `wp migrator import` reports errors cleanly.
  • Fixed: the encryption password is passed to Migrator PRO intact.
  • Changed: on Multisite, Migrator is limited to super admins.
  • Changed: uninstalling removes all of Migrator's settings and its scheduled event.
  • Readme: corrected the rollback, nginx and off-site wording and the competitor comparison, and added FAQ entries.
v1.3.8
  • The sidebar upgrade promo now follows the same dismissal as the banner. Dismissing the banner used to leave a full-height advert on the settings screen for good, which is not what the WordPress.org guideline on upgrade prompts means by used with moderation.
v1.3.7
  • Fixed: a restore only found out that an archive had been cut short part way through reading it, by which time the database had already been replaced. An archive is now checked for the end marker a finished backup carries before the restore touches anything, so an unfinished one is refused with the site left as it was.
  • Fixed: the copy of the database taken before a restore was deleted the moment the import of the database finished, so anything that failed after that point left the site part restored with nothing to go back to. That copy is now kept until the whole restore is through, and if a restore does stop after the database was replaced the error says what state the site is in, where the copy of the previous database is, and what to do with it.
v1.3.6
  • Fixed: a backup could quietly leave rows out of the database dump. Every table was read in pages counted from the start of the table, so when anything deleted a row behind the reader (an expiring transient, a WooCommerce session, an abandoned cart), every later row moved up one place and the row sitting on the next page boundary was never read. It was missing from the backup and nothing reported it. Tables are now read in primary key order, each page starting after the last key already read, which no concurrent delete can move.
  • Fixed: a table with no primary key cannot be read that way, so it is still paged by position. Its row count is now taken before and after the read: if the table shrank while it was being dumped, the backup stops with an error naming the table instead of finishing and handing you an archive that quietly lacks rows.
  • Fixed: a backup that was killed part way through (execution time, memory, closing the browser tab on Run now) left half an archive behind under the final backup name. The backups screen listed it, the retention rule counted it as one of the copies to keep, and the good backup it pushed off the end was the one deleted. A run now builds under a temporary name and takes the real one only once the archive is finished, and the leavings of runs that died are cleared out.
  • Fixed: an archive that had been cut short was read as if it were simply a smaller archive. A complete archive ends with an end marker, but running out of file instead was treated as the same thing, so a backup killed while it was being written could be restored with everything after the cut silently absent. Reading one now stops and says the archive is incomplete.
  • Changed: a scheduled backup no longer runs under the host's default execution time limit. Building a whole site archive and copying it off-site takes longer than that on any site large enough to need backups.
v1.3.5
  • Fixed: the PRO upgrade promo kept selling to people who had already bought the paid edition. Only the banner could be dismissed, so the sidebar promo and the locked feature cards followed a paying customer around for good. The promo now checks whether the paid edition is active and steps aside when it is.
  • Fixed: arrow glyphs in the admin menu paths, and in the strings handed to translators. An arrow inside a translatable string makes the glyph every translator's problem and changes the layout in any locale that drops it.
v1.3.4
  • Fixed: a restore could stop part way through and still report success. When the disk filled up while the backup was being unpacked, the write stopped where it ran out of room and nothing said so, so the database was restored up to that point and the rest was silently missing. The same applied to every file taken out of the archive, and to the list of files written into a new backup. All three now stop and tell you the disk is full instead of finishing quietly.
  • Fixed: when an import failed and the attempt to put the previous database back ALSO failed, the message still said the database had been rolled back. It now says the site is in a partly imported state and gives the path of the dump that has to be restored by hand.
v1.3.3
  • Fixed: deleting the plugin left the per-user "dismiss" flag from the PRO notice in the database. Uninstall now removes it for every user, not just the one who dismissed it.
v1.3.2
  • Changed: the message shown when a restore crosses a multisite boundary now states the limitation instead of naming the paid add-on. The restore is still refused, because rewriting the network tables to the destination domain is genuinely not part of this plugin, but a free plugin's own error text should not read as an upsell.
  • "Tested up to" was declared in the plugin header as well as in this readme. WordPress.org reads the readme; declaring it in two places is how a listing ends up advertising a compatibility claim nobody wrote. The header line is gone, the readme is unchanged.
v1.3.1
  • The translation template was regenerated. 57 strings added to the plugin since the template was last built were missing from it, so no translator could reach them in any language, and 2 strings the plugin no longer uses have been dropped. Nothing you see changes; what a translator can see does.
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: it 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