Zurück zu Migrator Prov1.2.9 (26 Releases)

Changelog Migrator Pro

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

v1.2.9

Fixed (critical): off-site retention deleted the oldest archives of every kind in the destination, so another site's backups and manual uploads in a shared S3 bucket, Dropbox or Drive folder, WebDAV or SFTP directory were removed. Retention now counts and deletes only this site's scheduled archives, and deletes nothing when the destination reports no modification time. The S3 listing also ignores nested keys and objects that are not Migrator archives.
Fixed: incremental chain retention and the Scheduled Backups list matched every site's full and incremental archives in a shared workspace. Both now match only this site's.
Fixed: the deployment installer download could start with output that was already buffered.
Fixed: the Settings link on the Plugins screen pointed at a page that no longer exists; it now opens Scheduled Backups.
Requires Migrator 1.4.0 or newer.

v1.2.8

Security (medium): a server-to-server pull now requires an https:// source address. Over plain HTTP the pull key and the full site archive crossed the network unencrypted. Local development hosts (localhost, .localhost, .test) are exempt, and the migrator_pro/allow_http_pull filter allows others.

v1.2.7

Display name drops the "Plogins " prefix; the slug, text domain and option keys are unchanged.

v1.2.6

Fixed: a single dropped connection during a pull ended the whole transfer. The reads that make up a migration, the remote site's info and each downloaded chunk, are now repeated once after a timeout or a 5xx. Nothing that writes on the far end is repeated: preparing an archive and cleaning it up still happen exactly once.

v1.2.5

Fixed: compressing or encrypting a finished backup wrote the new file under the final name with ".part" added, and that name was still matched by the pattern the Scheduled Backups screen and the retention rule use to find the archives in a chain. A step killed part way through (execution time, memory) left that half-written file on the disk for good: the screen listed it as a backup, and because its name carried "-full-" the retention rule read it as the start of a chain of its own and deleted a whole real chain to stay within the number of chains you asked it to keep. Compression and encryption now write under a name neither the screen nor retention matches, and that the clean-up of abandoned builds removes.

v1.2.4

Fixed: an incremental backup worked out what had changed by building a complete second list of every file under wp-content beside the list left by the previous run, then comparing the two, all inside the one request that then had a whole archive to write. On a site with 100,000 files that pair and the comparison between them peaked at 43 MB, measured, which on a modest memory limit is how a scheduled backup dies without saying anything. The scan now writes the new list straight to disk and crosses each file off the old one as it goes, so what is left over is what was deleted. Measured on a 10,000 file tree: 2.7 MB of memory before, under 256 KB now.
Fixed: an incremental backup built the archive under its final name, so a run killed part way through (execution time, memory, the browser tab closing) left half an archive that the Scheduled Backups screen listed, that the retention rule counted as a member of the chain, and that a restore would have walked into. A run now builds under a name none of that matches and takes the real one only once the archive is finished. The same is true of compressing and encrypting it afterwards.
Changed: the file state that tells the next run what is already backed up is saved only after the archive is safely in place. A run killed before that point costs the next run the same files a second time, which is the right way round: the other order leaves the next backup believing files it never wrote are safe.

v1.2.3

Fixed: the same truncation as the free plugin's 1.3.4, in five more places that only this add-on has: incremental restore, Table Sync, subsite import and subsite export. Table Sync writes into a live shop, so a write cut short by a full disk was the worst of them. Every one now stops and says the disk is full.
Fixed: ticking "Encrypt this backup with a password" and then having encryption fail left the backup readable and offered it for download with no warning, as though the password had been applied. The archive is still kept, because losing a backup is worse, but the screen now says plainly that it is not encrypted and why.

v1.2.2

The translation template was regenerated. 13 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 87 strings the plugin no longer uses have been dropped. Nothing you see changes; what a translator can see does.

v1.2.1

Fixed: the plugin title label on Freemius notices rendered white on a background measuring 2.37:1, where WCAG AA wants 4.5:1 for text that size. The label now uses the same grey WordPress core uses, at 4.61:1.
Fixed: the public key constant was defined inside the guard for the product id constant, so it would have gone undefined if anything had defined the id first. Harmless today, wrong the moment it is not.

v1.2.0

Changed: scheduled backups, retention and the FTP/folder destinations now belong to the free Migrator plugin. Nothing is lost: your schedule, exclusions and off-site credentials carry across automatically, passwords included. This add-on now contributes the cloud destinations (S3, R2, Backblaze, Wasabi, SFTP, WebDAV, Dropbox, Google Drive), incremental backups and encryption on top of it.
Fixed: deactivating this add-on cleared the backup cron event, which stopped the site's scheduled backups. Scheduling belongs to the free plugin now, so it keeps running.
Fixed: a recovery point could be taken as an incremental link in a chain, or encrypted with the site's passphrase. A rollback taken before a risky operation has to be a plain, readable full archive; it now always is.
Fixed: three listeners (email notifications, the activity log and recovery points) were hooked to an action that no longer fires after the split, so none of them would have run.

v1.1.6

Fixed: the safeguard meant to stop an incremental restore touching the plugin folders themselves compared against the names these plugins had before they were renamed, so it never matched anything on a real installation. It gates the deletion replay as well as the file write, which means restoring a chain that spans a plugin update could delete files inside the running plugin mid-restore. The folder names now come from the installation itself.

v1.1.5

Fixed: in incremental mode the Scheduled Backups screen showed no backups at all, however many had been taken. The list looked for the scheduled marker in the filename, but an incremental run writes full or incr instead, so it matched nothing. The screen now lists all three. Retention is deliberately left looking at the narrower set, because it keeps the newest N and deletes the rest, and a full-mode prune over the wider list could delete the base backup out from under a live incremental chain.
Fixed: the compatibility check against the free plugin could never fire. It required Migrator 0.1.0 or higher, a floor from an era when that was the current version, so a genuinely too-old free plugin would have caused a fatal error rather than the notice this check exists to show. The floor is now 1.2.0, which is where SearchReplace gained the second argument this add-on passes it.

v1.1.4

Fixed: resetting a site left both Migrator and Migrator Pro deactivated. The reset reactivates the two plugins by path so the safety backup it takes first can be restored, but the paths were still the ones the plugins had before they were renamed, so neither matched and both stayed off. They are now derived rather than written out.
Copy: the feature list named six things and the plugin ships eleven. Recovery points, deploying to an empty server, resetting a site, white label, notifications and the activity log were all shipping unlisted. Multisite is described as network to network, which is what the admin screen does.

v1.1.3

Fix: deleting the plugin now removes its options and transients instead of leaving them in the database, on every site of a network. The free plugin's own settings are untouched.

v1.1.2

Copy: the plugin description sold "no size limit" as a PRO feature. The free edition has no size cap to lift, so the description now lists what PRO actually adds. Multisite is described as network to network, which is what the admin does; pulling a single subsite out of a network stays a WP-CLI job.

v1.1.1

Polish, German and Spanish translations for the table sync screen and for the installer's fetch-by-link help text.

v1.1.0

Table sync: import chosen database tables from a backup into a live site and leave the rest of the database alone. Push content from staging to production without rolling back the orders, customers and comments that arrived since the backup was made. Preview what would change first, and the chosen tables are dumped before anything is written, so a failed sync puts them back as they were.
The standalone deploy installer can now fetch the backup itself from a link, including a presigned Amazon S3, Cloudflare R2 or Dropbox URL. A large archive no longer has to come down to your computer and go back up to the new server.

v1.0.2

Added bundled Polish, German and Spanish translations for the plugin interface.

v1.0.1

First stable release.

v0.5.2

Plugin Check: escaping/sanitisation/i18n/hygiene fixes.

v0.5.1

Maintenance: renamed the plugin slug and text domain to plogins-migrator-pro. No feature changes.

v0.5.0

New off-site destination: SFTP (SSH). Uploads stream straight from disk; authenticate with a password or a private key. No PHP SSH extension required.

v0.4.0

Deploy to a new server: a standalone installer rebuilds the site from a backup on an empty server with no WordPress. It can download WordPress core, extract your files, import the database, rewrite the old URLs and paths (serialization-safe), and write a fresh wp-config.php. New "Deploy" screen hands out the installer with step-by-step instructions.

v0.3.0

New off-site destinations: FTP/FTPS and WebDAV (Nextcloud, ownCloud). Uploads stream straight from disk, and retention prunes the destination like any other.
S3 provider presets: pick Amazon S3, Cloudflare R2, Backblaze B2, Wasabi or DigitalOcean Spaces to fill the endpoint template in one click (all use the proven S3-compatible transport).
The FTP screen warns up front when the server is missing the PHP FTP extension.

v0.2.0

Recovery points: a rolling set of known-good backups you can roll the whole site back to in one click. One is captured automatically after every successful backup, and you can capture one on demand. Each point remembers the site address and database prefix it saved.
Email notifications: get an email when a scheduled backup completes or fails, so a silent failure never slips by. Choose the recipient and which outcomes to send.
Activity log: a newest-first record of backups, restores, off-site copies and recovery points, with a one-click clear.

v0.1.0

Initial PRO scaffold: licensing, bootstrap and Freemius integration.

Zurück zu Migrator Pro Preise