Prime Mover 2.0 – Scheduled backup support/WP 6.7 compatibility/New Freemius checkout & Bug fixes

Overview

Welcome to Prime Mover 2.0. This is a big change after months of development and testing. Compared to previous versions, there are no changes to the old features or functionality. We keep what you already enjoy. We added new bug fixes, usability improvements, and new features to improve your backup and migration experience.

Changelog

= 2.0.0 =

• Feature: Support for automated and scheduled backups.
• Compatibility: Tested for WordPress 6.7 compatibility.
• Fixed: Updated Freemius SDK library to latest version 2.9.0.
• Fixed: Google Drive API session is not global when already connected.
• Fixed: Issues with parallel exports.
• Fixed: Runtime error when restoring database to unsupported collation type.
• Fixed: Helpful errors when Prime Mover has issues writing to an archive.
• Fixed: Runtime errors associated with database tables names containing allowed special characters.
• Fixed: Runtime error on export if site uses database names with allowed special characters on it.
• Fixed: Normalize paths for packages for Windows server.
• Fixed: Missing administrator capabilities when migrating from multisite to single-site.
• Fixed: Broken migration if site uses relative wp-content URLs.
• Fixed: Runtime error during migration if site enables WP_DEBUG_DISPLAY + WP_DEBUG mode to true.

New PRO feature: Scheduled backup support

In Prime Mover 2.0, automatic/scheduled backup support is added. The good news is that this works with both WordPress multisites and single-sites. It works like making backups manually, but now you can do it automatically.

It is as simple as setting schedules, and then you can let Prime Mover PRO take care of the rest of creating periodic backups. You can configure your automatic backup settings on a per-site basis on the new Toolbox page.

Monitor the progress and status of all your scheduled backup events in the Prime Mover PRO -> Event viewer.

For details – please check out this new documentation on setting up scheduled backups for your site.

WordPress 6.7 compatibility

WordPress version 6.7 will be released on November 12, 2024. Prime Mover 2.0 has been tested with this version. The last version tested is its release candidate version and the entire testing process has now used WordPress 6.7.

New SDK Update: Freemius 2.9.0

Freemius 2.9.0 SDK update brings many usability changes to managing your data and customer checkout experience. Please read the official release blog post.

Important bug fixes

Prime Mover 2.0 fixes a lot of bugs that were found in the previous versions. Here are the highlights:

• If you restore with WP_DEBUG and WP_DEBUG_DISPLAY on, there will be errors at runtime. Prime Mover 2.0 has fixed this issue. The issue is that WordPress outputs an HTML string when you turn on these errors. But, these HTML strings are unexpected and stop the restore process.
• If your site uses a relative WordPress content URL, then previous versions will always have broken migrations and backups. This issue has now been resolved with Prime Mover 2.0 and is now fully supported if your site uses relative content URLs.
• If you use previous versions to migrate from a multisite subsite to a single site, you will be missing administrator capabilities. For example, after restoring a single site, the administrator will no longer be able to delete plugins or install new themes. This is unexpected. This is now handled with Prime Mover 2.0, as well.
• Prime Mover 2.0 ensures that Windows server paths are normalized when stored to database. This avoids breaking URLs paths during migrations.
• Previous versions have encountered issues with exporting sites with database table names using special characters. Consequently, these tables are not imported into the intended website. Prime Mover 2.0 now supports standard table naming conventions.
• In older versions, it will not output helpful errors when the disk is full (such as exporting a large site) This issue is now resolved with Prime Mover 2.0. In the latest version, the user will know immediately from the runtime error itself that the export encountered an error due to insufficient disk space. Other terms utilized include inadequate disk quota or no remaining space on the device. This means that there will be no more free disk space left.
• In previous releases, it was not possible to restore a MySQL 8.0 default collation, such as utf8mb4_0900_ai_ci, to MariaDB because MariaDB doesn’t support this collation. Also, errors will also happen when you move the site to a lower MySQL version. This is because this type of collation is still not supported with this version. In Prime Mover version 2.0, we checked for these types of issues and made sure that they would be fixed when the site was moved to any database version or platform. No more runtime errors about this.

Feedback and support

If you have something to say about this release or any feedback, please contact us by contacting us here. Thanks!