• 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.

The post Prime Mover 2.1.2 – Bug fix release appeared first on Codexonics.

Welcome to Black Friday Cyber Monday offer! We are offering a 30% discount on our Unlimited Lifetime plans.

So, to complete the purchase, please use the coupon:

FSBFCM2025

Please let me know if this coupon does not work, and we will check again or create a different coupon for you. Please take note that this will expire on December 2, 2025. Thank you again!

The post Black Friday / Cyber Monday deals – 2025 appeared first on Codexonics.

= 2.1.1 =

• Fixed: Incompatibility issues with third-party salt implementation.
• Fixed: Runtime error when activating plugins during import.
• Fixed: Insufficient memory errors during the search and replace process.
• Fixed: Improved restore performance by reducing the search-and-replace batch size.
• Fixed: Database export timeouts on servers with minimal resources.
• Fixed: Updated the Freemius SDK to version 2.13.0.
• Fixed: Updated the Freemius pricing page library to the latest version 1.3.0.
• Compatibility: Tested with WordPress 6.9 release.

Background

A lot of things are happening in this release – it’s action-packed!, So update to the latest version to join the ride and chill with the most stable version of the plugin.

Performance and bug fix improvements

BEFORE: Runtime error during search and replace, typically when processing super-large database tables.

NOW: Latest release lowers the default batch size for search-and-replace from a very high value (25000) to a super low value of 250. This will ensure that, no matter your database size, it stays mostly within your server’s RAM specifications!

BEFORE: Third-party plugins block export and restore because they have their own SALT implementation.

NOW: For compatibility, this is overridden to ensure that no third-party plugins can block the export and import process.

BEFORE: Export timeouts when processing super-large database tables.

NOW: The default export batch size is reduced from 5000 to 250. This will ensure it has sufficient time to process large data sets. This will work even on a very slow, underpowered server.

BEFORE: Outdated Freemius SDK and pricing library.

NOW: This is updated to the latest version, which includes the most stable version of the Freemius SDK. For details, read their dedicated release notes.

BEFORE: Not tested compatible with the WordPress 6.9 release.

NOW: The latest release is now tested to be compatible with WordPress 6.9.

Comments? Suggestions?

Please drop us a comment or contact us here. Thank you!

The post Prime Mover 2.1.1 – WP 6.9 compatibility, new Freemius SDK, bug fix, and performance improvements appeared first on Codexonics.

= 2.1.0 =

• Fixed: Deprecated notices in the PHP 8.4 latest version.
• Fixed: Outdated libraries to work in PHP 8.4.
• Fixed: Updated all third-party libraries to work from PHP 5.6 to PHP 8.4.
• Fixed: Updated the Freemius SDK to version 2.12.2.

Complete list of updated libraries

The Prime Mover plugin utilizes third-party open-source libraries to implement various features. In this release, all components are updated for compatibility from PHP 5.6 to the latest stable PHP 8.4 release.

These are as follows:

• WP-Config Transformer – version 1.4..2.
• PHP scoper – version 0.17.5
• WP Mock – version 1.1.0
• PHP Unit – version 9.6
• Google Drive API – version 2.16.1
• Freemius SDK – version 2.12.2

Improvements in this release

This release permanently resolves all deprecated notices found in PHP 8.4 due to outdated libraries. There is also an added security improvement as it uses updated libraries. Additionally, utilizing the latest Freemius SDK offers performance benefits in multisite environments. You can read more about its detailed release notes.

Feedback?

If you have comments or feedback on this release, please get in touch with us through the comment section or send us a message via this form. Thank you!

The post Prime Mover 2.1.0 – Major third party library update appeared first on Codexonics.

Change log

= 2.0.9 =

• Fixed: Added support for page builders using base64 encoded data.
• Fixed: Compatibility issues with the preview domains setup.

Under the hood

• Previous versions of Prime mover are incompatible with preview domain setups, such as those found in Hostinger. The reason is that the preview domain paths are set up virtually, and physical paths exist only for the real site. The previous workaround involved migrating using the real site (live site) domain or changing the backup directory to a physically existing path. This is no longer necessary with Prime Mover 2.0.9. This is supported in both free and PRO versions.

• Page builders that store data in base64 encoded format make it impossible to do a search and replace (because the data is encoded). With Prime Mover 2.0.9, we added support for this. This makes it fully compatible if you are migrating a site that is using page builders such as Brizy (which stores data in base64 format).

Get in touch

If you have any comments, reactions, or concerns about this release, we’d love to hear them! Have a great day.

The post Prime Mover 2.0.9 – Preview domains support and maintenance update appeared first on Codexonics.

= 2.0.8 =

• Usability: Block activation on WordPress sites using SQLite databases.
• Fixed: Excluding Windows thumbs.db from export/import to prevent file permission issues.
• Fixed: Multisite core global tables exported in single-site export.
• Fixed: Exclude other site database tables in shared database export situation for single sites.
• Fixed: Overwriting of database tables in WordPress sites sharing the same database.
• Fixed: Updated the Freemius SDK to the latest version 2.12.1.
• Fixed: Unidentified packages due to spaces in file names.
• Fixed: Auto-exclude the Advanced WordPress reset plugin from multisite import.

Windows thumbs.db exclusion fix

In Windows legacy servers, thumbs.db can cause restore and export issues due to its permissive nature. The good news is that thumbs.db is no longer relevant to your WordPress installation, so it is entirely removed from the export and restore.

This allows Prime Mover packages to be restored to a Windows environment without causing any thumbs.db permission issues.

Reverted multisite installations to single-site

Reverted multisite means that a single-site was once converted to multisite and then, at some point, reverted again to single-site. This causes WordPress to retain its multisite core tables (e.g., blogs, sitemeta table, etc) in a single-site database environment.

This causes restore issues when this type of site is migrated to a multisite environment. It is because the blogs table from this source site will overwrite the target site’s multisite core tables. This is now permanently fixed in this release, so problematic tables are auto-excluded during export.

Auto-deactivate on sites using SQLite database

Prime Mover plugin does not yet support SQLite database. There are now WordPress sites using SQLite, although this is not yet widely supported among hosting servers (as production environments). Examples of this are WordPress playground environments and Studio App, which are usually used as development environments.

When Prime Mover is used in these sites, it will auto-deactivate since it is not yet supported.

Full support for shared WordPress database

A shared WordPress database means that several WordPress sites use the same database. This is not commonly used today since WordPress hosting servers allow you to make a dedicated database for each site.

WordPress supports a shared database, but this practice is discouraged due to security and compatibility risks associated with database sharing. This is mainly implemented only in development environments or in hosting environments that only allow the use of one database (e.g., free hosting, etc).

The latest version fully supports exporting and importing sites in a shared database structure. This means:

• If a site using a shared database is restored with a package from a different site, it won’t delete and overwrite other tables (from other sites) in the shared database structure.
• If a site using a shared database is exported and migrated to another site, it will only export tables belonging to that specific site.

Auto-remove spaces in package file names

Suppose the package file name contains spaces, e.g., instead of “mypackage.wprime” – it becomes “mypackage.wprime ” (see the extra space at the end of file extension). Prime Mover cannot detect this package inside the package manager. If this package is also restored via uploads, it can cause runtime errors.

This extra space can be caused intentionally by renaming the files or could be caused by a server misconfiguration. Prime Mover 2.0.8 automatically detects this type of issue and automatically renames the file to remove the extra space. As a result – as long as the package is valid and not corrupted, it will always appear in the package manager.

Auto-exclude Advanced WP Reset

Prime Mover recommends resetting the site in some instances via an Advanced WP Reset plugin. However, this plugin is not compatible in a multisite environment and causes a white screen (when activated via database – e.g., during migration).

Since Prime Mover 2.0.8, this is automatically excluded from all exports. This prevents all possibilities that this plugin can be activated in a multisite environment.

Freemius SDK 2.12.1

The latest release includes the latest version of Freemius SDK as of July 2025. For details on this version (2.12.1), please check out their release notes.

Share your thoughts

If you have something to share about the new release (e.g., a new issue, etc.) that you would like us to know, please get in touch with our technical support.

The post Prime Mover 2.0.8 – Major bug fix update and new Freemius SDK library appeared first on Codexonics.

= 2.0.7 =

• Fixed: Malformed domain name due to edge case double search replace.
• Feature: Added user difference check when migrating site to multisite main site.
• Fixed: Removed cron jobs when the plugin is uninstalled.

Fixed: Double search and replace issue on some domains

This release addresses an edge case issue. This only happens on multisite with the following configuration:

• The main site is using a TLD like test.co.
• The target subsite is using a TLD like test.co.uk
• The source site is using a TLD like test.co.za

Suppose the source site is migrated to the target subsite. The resulting domain is double replace, so it became test.co.uk.uk instead of test.co.uk

This is thoroughly tested and now fixed with the latest version 2.0.7

Feature: Added main site import user difference check

In previous versions, the user difference check only applies to single-site. Now, with Prime Mover 2.0.7, this feature is extended to multisite main site import for fresh multisites. Fresh multisite is defined as a site with only one site (main site only) and one user (super administrator). This fresh multisite state only happens on a newly created multisite.

Fixed: Removed cron jobs on uninstall

The Prime Mover plugin will add cron jobs to WordPress on both the free and pro versions. On PRO versions, and if you enable the automatic backup feature, this will add more cron jobs.

In previous versions, this was not removed during uninstallation and could only be removed using third-party tools, such as the WP Crontrol plugin.

This is now handled with Prime Mover 2.0.7, so no need to use any third-party tools.

Comments?

If you have some thoughts and comments on this release, feel free to comment or ping us via our contact form. Thank you!

The post Prime Mover 2.0.7 – Maintenance and bug fix release appeared first on Codexonics.

• Feature: Support was added to exclude database tables from export.
• Usability: Added missing features tutorials.
• Fixed: The white-labelled license upgrade page goes to a non-existent page.
• Fixed: The user was presented with an upgrade instead of activating the license buttons.
• Usability: Improved labeling of subsite action buttons based on plan subscription status.
• Usability: Improved handling of upgrade buttons.
• Updated Freemius SDK to the latest version.

New PRO feature: The Exclude tables feature

With Prime Mover PRO 2.0.6, it’s now possible to exclude specific database tables when you export a site. This is useful if you have gigantic database tables that you don’t need to migrate. And if these tables are created by third-party plugins that your site is no longer using.

This can speed up the export and restore process in general because the Prime Mover plugin does not export and restore these tables. Another use of this feature is to create a lighter or cleaner version of your site. Say your site feels heavy and sluggish because of these database tables – you can clean up or create a lighter version of your site as follows:

• Deactivate plugins that are heavy and you no longer need. Or using the Prime Mover PRO feature – exclude these plugins from the export.
• Identify all database tables that are no longer used by your site (leftover from previous plugins or deactivated plugins).
• Using the new Prime Mover PRO exclude table feature – exclude these tables from the export.
• Generate an updated export of the site.
• Create a fresh WordPress install on your site.
• Finally, restore the package. Your site now runs faster because of reduced overhead by removing all the unnecessary tables and plugins.

Latest SDK library: Freemius 2.12.0

Freemius released its latest SDK library, which is now integrated with the latest Prime Mover release version 2.0.6. This update includes numerous bug fixes and new features designed to enhance the user experience with Freemius.

For details, please check out the latest release notes.

Usability fixes

Prime Mover 2.0.6 includes several updates that address the following usability issues with previous versions:

• If the site already has a license enabled but not yet activated, all PRO buttons should display as “Activate PRO” instead of showing “Upgrade PRO”. This will immediately inform the user that a license is available and can be used.
• If the site does not have a license enabled, it should show “Upgrade to PRO” buttons.
• If the site runs out of license activation quotas, it should show “Upgrade to PRO,” highlighting the current plan so the user can upgrade to a higher plan if needed.
• If the license is white-labeled, don’t display the upgrade page, as it does not exist. Instead, provide instructions on how to upgrade correctly. Your developer activates white-labeled licenses, and the client does not have complete control over these license accounts and the upgrade process.
• If the site has a deactivated license, the upgrade page should direct the user to their Freemius account so they can correctly upgrade, which includes prorated upgrades.
• All PRO features now have a tutorial linked to the official documentation.

Share your feedback!

If you are experiencing some issues with this specific version or want to share some feedback, we are happy to hear it! Thank you.

The post Prime Mover 2.0.6 – Exclude table feature, Usability fixes, and updated Freemius library appeared first on Codexonics.

• Fixed: Controls were added for the outdated Prime Mover plugin manager script in the mu-plugins directory.
• Fixed: Unable to download package in Docker-based WordPress installations.
• Fixed: Search and replace issues with similar subdirectory path installations.
• Fixed: Freemius safe mode after import.
• Fixed: After import, search and replace issues with broken external WordPress URLs.
• Compatibility: Tested for WordPress 6.8 release.
• Usability: Added tutorial to download packages in different ways.

Outdated & non-writable mu-plugin script detection

Prime Mover 2.0.5 detects non-writable mu-plugin scripts to ensure this can be updated. The handling is as follows:

• Check if the mu-plugin script manager is writable. If not writable – check if it’s the same with the latest version.
• If already the same with the installed version – the Prime Mover plugin can be used and remain activated.
• Otherwise, if the mu-plugin script is outdated and cannot be updated (due to permissions) – the Prime Mover plugin will auto-deactivate. The user must fix this issue before the plugin can be fully activated.

The control is added because it can introduce serious errors if the plugin is updated, but the mu-plugin script remains outdated.

Better compatibility with Docker-based install

The latest version is much better and friendlier to Docker-based installations than previous versions. There are several issues found with WordPress Docker that were fixed in the newest version:

• Unable to download packages in Docker.
• Bedrock WordPress migrations in and out of Docker will result in incorrect URLs.

The platforms tested with WordPress Docker are DevKinsta and DDEV development platforms.

Search replace issues with WordPress external URLs

This update fixes an edge issues with WordPress external URLs. For example, if you migrate a site – it will also change the WordPress external URLs, particularly those linked to external media files such as yourexternal.tld/wp-content/uploads/test.jpg

This happens when you migrate URLs with relative replacements (e.g. if you migrate from the root directory to the subdirectory), or it can happen if you migrate the main site to the subdirectory subsite.

Supposing these relative replacements will tell the processor to search for /wp-content/uploads/ and replace it with /wp-content/uploads/sites/5 (like when you migrate a main site to blog ID 5 subsite).

These relative replacements will affect external WordPress URLs so that it will change: yourexternal.tld/wp-content/uploads/test.jpg TO: yourexternal.tld/wp-content/uploads/sites/5/test.jpg

This will result in broken external WordPress. These are fixed with Prime Mover 2.0.5.

Freemius safe mode warning after import

In the previous version, there was a bug after the restore that would result in a “Freemius safe mode” warning. This happens mostly in multisites where clone subsites are from other subsites. The clone resolution offered by Freemius will not work in this case – because the URLs are also messed up.

The solution added in the latest version, 2.0.5, excludes Freemius settings and options from search and replace. This is unnecessary and can only corrupt the Freemius installation after restoration. This has already been done with previous versions, but this update is more of a refinement to ensure this is excluded.

Usability update: The download package column includes a tutorial link

With so many WordPress configurations and hosting, your host sometimes blocks any file download from your WordPress admin. This includes blocking the download of your exported Prime Mover packages (WPRIME package). This is beyond Prime Mover plugin control, but luckily, there is a way you can download them.

Almost all hosting solutions have access to their file manager or SFTP/FTP. You can use these tools to download your WPRIME packages if they are blocked within WordPress. With Prime Mover 2.0.5 – the download package heading column now has a link to the tutorial such as shown below:

WordPress 6.8 compatibility

There is a major update coming to WordPress this April 15, 2025. It’s the release of WordPress 6.8. Prime Mover 2.0.5 has been thoroughly tested with this newest version in all aspects of plugin functionality. This also includes testing the plugin in both single-site and multisite scenarios.

No issues were found during the testing, so we marked the release as compatible.

Share your thoughts

If you have something to add or feedback regarding this release – feel free to share it with us. Thank you!

The post Prime Mover 2.0.5 – Bug fixing update and WordPress 6.8 compatibility appeared first on Codexonics.

Prime Mover 2.0.4 is the latest release focusing on the maintenance/bug fix update and new Freemius SDK.

Change log

= 2.0.4 =

• Fixed: Data was missing on import due to a large extended insert in the database restore.
• Updated Freemius SDK to the latest version.

Fix missing data on restore

There are confirmed reports that some data will be missing on restoration. Non-ASCII, non-English characters are affected. When these are gone, the database tables will be entirely missing data because they are dumped with the EXTENDED INSERT setting.

Prime Mover 2.0.4 fixes these issues, so it can now support any valid data (as long as it can be restored to the database via the native MySQL restore command).

New Freemius SDK update

The latest version of Freemius SDK (version 2.11.0 ) is added to this plugin.

Questions?

Please let us know, and we will be happy to hear it.

The post Prime Mover 2.0.4 – Maintenance and bug fix update appeared first on Codexonics.