Changelog do WP Staging Pro

Correção

• A scheduled backup no longer stays queued for hours when the cron run that tries to restart it has no memory or time left to take it.
• Copy every row of tables with gaps in their IDs when creating, updating, resetting or pushing a staging site with the Next-Gen engine.
• Keep staging site creation, push and backups fast on large tables with a composite primary key, and stop locking them while they are backed up.
• Keep the search and replace of staging, push and backup restore jobs from stalling or running out of memory.
• Retry a background backup step once when its worker dies, and tell the owner when the retry dies too, so a backup never finishes without the file it was on.
• A background backup no longer re-adds the same file again and again in one request once its time to add files has run out.
• Show an error instead of hanging when the staging process gets a server response it cannot act on.
• When neither the WordPress root nor wp-content is writable, say how to fix it instead of asking Free and unlicensed Pro users for a custom path they cannot set, and show that error on the Classic engine instead of a stalled progress screen.
• Preserve existing plugins, themes, mu-plugins, and other files by default during subsite restore. (Pro)
• Retry a Dropbox backup upload whose last step failed, instead of reporting it as uploaded. (Pro)