Change log
- Performance: Improve overall export and restore log performance by reducing file sizes.
- Deprecated: Remove PRIME_MOVER_PLUGIN_MANAGER_LOG constant and primeMoverMaybeEnablePluginManagerLog() for better security/performance.
- Compatibility: Fixed high-severity issues reported by Plugin Check.
- Fixed: translation mechanism errors in some files.
- Fixed: Outdated clipboard JS library.
- Fixed: Issues with fonts and resources rendering in CORS.
- Fixed: Refactored restore query handling for better performance and security.
- Fixed: Updated Freemius SDK library to the latest version.
- Compatibility: Moved the Freemius library to the vendors directory for better compliance with guidelines.
- Usability: Reduce the plugin’s total zip file size to make it easier to use in limited shared environments.
- Security: Fixed remaining unescaped outputs in direct plugin HTML.
- Compatibility: Bump the minimum supported WordPress version to 5.2.
- Compatibility: Tested for compatibility with the WordPress 7.1 release.
Performance: Reduce log sizes
Prime Mover 2.2.0 now uses JSON-formatted strings instead of raw print_r() output. This results in dramatic speed, performance, and size improvements in the migration/backup logs.
Log file size is typically a concern for big sites, particularly multisites, when optimizing the logging method. This is a big performance help.
Performance: Robust clipboard and font libraries
Prime Moer 2.2.0 now uses the clipboard library shipped with WordPress. This eliminates the need to ship and maintain its own clipboard libraries. Since WordPress has loaded it, the performance and compatibility are optimal.
This also automatically fixes the outdated clipboard library used by the plugin. In addition, fixing these font libraries also fixes issues with CORS (Cross-origin resource sharing).
Deprecation: Removal of unused constants and print_r() calls
PRIME_MOVER_PLUGIN_MANAGER_LOG was used in earlier days, but it is no longer used in modern WordPress implementations. This has been deprecated as well, including all calls to print_r(), which is restricted only to development environments and not production environments.
Compatibility: Freemius SDK update
Prime Mover 2.2.0 now uses the latest Freemius SDK library, 2.13.4. For details on this release, please check out their change log.
Localization: 100% translatable strings
Prime Mover 2.2.0 fixes issues that prevent translators from properly translating strings. In accordance with WordPress plugin translations, all visible and translation issues are fixed, paving the way for an easier translation experience on the part of translators.
Performance: Reduce plugin overall size
Efforts have been made to reduce plugin size in version 2.2. So far, the biggest improvements are as follows:
- Remove font files and transfer them to CSS for universality and portability.
- Remove all unneeded clipboard JS libraries.
Compatibility: Move Freemius SDK library to /vendor/
For compliance and compatibility with WordPress plugin guidelines, the Freemius SDK library is moved to its own /vendor/ directory. This ensures clear isolation between the actual plugin code and third-party plugin code libraries (e.g., Freemius)
Compatibility: Plugin name revision on WordPress.org
To comply with WordPress plugin guidelines, the plugin name must not contain other trademarks if listed in the official plugins repository. To satisfy this requirement, the plugin name was revised from “Prime Mover – Migrate WordPress Website & Backups” to simply “Prime Mover – Backup and Migration“.
Security: Escaping outputs in HTML
As per the Plugin Check code review, all possible HTML outputs in PHP are escaped. This ensures a secure way of outputting text and markup.
Compatibility: WordPress 7.1 Release
The Prime Mover 2.2.0 is tested using the latest WordPress 7.1 copy (beta4) in all phases of the testing process (including multisite testing). There are no visible issues, so the compatibility tested up to version was updated.
Compatibility: Bump minimum WordPress to 5.2
Since Prime Mover 2.2.0 now uses default WordPress clipboard JavaScript libraries, the minimum WordPress version is bumped to 5.2 instead of 4.9.8. WordPress 5.2 is where the clipboard JS library was first added to support the clipboard functions in the core Site Health feature.
If you happen to use versions of WordPress 4.9.8 up to and before WordPress 5.2, please check out these compatibility guidelines.
That’s it. Since this is a major update, there are so many changes. We tested this in all possible environments (shared host, dedicated host, VPS hosting environments, Windows, Linux, Docker, etc.) no issues. But please let us know if you think this update causes some issues on your site that you cannot resolve. We are happy to hear. Thank you!