Background
Prime Mover 1.6.5 is part of a two-week maintenance cycle release. It covers essential bug and compatibility fixes.
Change log
- Fixed: Compatibility issues with Bitnami WordPress virtual machine.
- Fixed: Canonical upload directory path issues during restore.
- Fixed: Incomplete migration logs.
- Fixed: Incorrect plugin paths for adding plugin headers to cache.
- Fixed: Prime Mover created the wrong export directories during the restore.
- Fixed: Disable heartbeat API only on locked Prime Mover processes.
- Fixed: The foreign constraint key exceeded the 64-character limit.
Bitnami WordPress compatibility
Older versions of Prime Mover (before version 1.6.5) have issues when used with Bitnami WordPress. If your server uses this platform, update to the latest version, 1.6.5, and use it to export/restore.
Upload directory path issue during restore.
When restoring a site, the migrated database overwrites the dB data. Since these are saved in the database, this can cause incorrect upload directory path values.
The side effects include missing logs, creating folders in wrong paths, etc. This is now fully fixed with version 1.6.5.
Disable Heartbeat API during any locked processes
Heartbeat API is enabled by default in WordPress. It is not used when running any Prime Mover processes (e.g., export, restore, etc.) because third-party plugins or hooks are also disabled. When enabled, it will run a WordPress AJAX event that can interfere with the ongoing processes.
This also improves performance and reduce side-effect issues.
MySQL dB foreign critical constraint error
MySQL implemented a 64-character limit on constraint identifiers. When restoring a dB, Prime Mover uses a unique identifier to prevent conflicts. Starting with Prime Mover 1.6.5, it now enforces a 64-character limit.
This will prevent database errors when restoring a site.
Release feedback
If you have some comments – please let us know.
Last updated: November 30, 2024