Change log
= 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.