Prime Mover 2.1.2 – Bug fix release

Change log

• Fixed: Stray core multisite tables inside the subsite database could corrupt restoration.
• Fixed: Runtime errors associated with WP_FileSystem not being initialized.
• Fixed: Insufficient memory error during the user import process when processing non-existing post authors.
• Fixed: Handle remaining incorrect permissions that can cause export and import errors.
• Fixed: Handle PHP notices when the open_basedir directive is enabled.
• Fixed: Handle PHP notices caused by legacy code with new dependency checks added in WP 6.9.1.

Important new changes

• Now checks the permission of the inner prime-mover-export-files and other Prime Mover directories. If these are not writable, you cannot perform export and import. Previously, these were not checked properly, creating confusion that the plugin is usable when it’s not. This also creates export and import hangs due to permission issues. With Prime Mover 2.1.2, the plugin won’t run or be usable unless these permission issues are fixed. If you are seeing these issues, make sure to assign correct writable permissions to your folders – you can let your hosting tech support assist with it. Some popular hosting providers, such as Hostinger, have built ina tool called “Fix file ownership” that enables you to fix these issues easily:

• There is a rare edge case where a post author does not exist in the users table. But the post author ID is a huge user ID (e.g., 12345678912345678). This causes memory runtime errors because, by default, Prime Mover uses SPLFixedArrays. When it instantiates this number, it can cause insufficient memory errors. The solution is to count the number of imported users, including those with a nonexistent post author ID. Then the algorithm can decide whether to use SPLFixedArrays (for a large number of users) or native PHP arrays for small sets.

• All instances of WP_FileSystem usage are checked; if any are not set, WP_FileSystem will be reinitialized. This resolves issues in specific edge-case applications where this object is not set at runtime due to the order in which hooks are initialized.

• Handle edge case where a global multisite table exists on subsite-prefixed tables – this is clearly a misconfiguration on the multisite. Prime Mover 2.1.2 now handles this automatically. This is automatically excluded during export and import since a global multisite table (e.g. wp_sitemeta or wp_blogs) can result in database corruption issues.

• When a shared hosting server has open_basedir directive enabled – it causes PHP notices in older versions. This notice is harmless and does not cause export/import functionality errors. However, this is now handled with Prime Mover 2.1.2.

• The recent WordPress 6.9.1 release causes PHP notices when used with older versions of Prime Mover because the plugin turns off heartbeat functionality on its own pages (which is critical for import/export to work). This PHP notice is also harmless and does not cause any import and export functionality errors. This only happens if the site is using WordPress 6.9.1 and when WP_DEBUG it is enabled. This PHP notice is now handled with the latest version of Prime Mover.

Let us hear your thoughts!

If you have some feedback on this release, please let us know by commenting on this post or sending us a message via our contact form.