Prime Mover 1.2.4 – PHP 8.0 Compatibility and Maintenance updates

Prime Mover 1.2.4 is now available for both WordPress.org (free versions) and Freemius (PRO versions). Change log = 1.2.4 = Fixed: Fatal runtime errors with PHP 8.0. Fixed: Usability issues with security configuration. Fixed: Outdated automated tests. Fixed: Compatibility with PHP 8.0. PHP 8.0 is the latest PHP version that will be supported by Prime…

Read more

Prime Mover 1.2.3 – Important bug fixes and maintenance update

As part of the 2-weeks maintenance release cycle, Prime Mover 1.2.3 is released today both in WordPress.org (free versions) and Freemius (PRO versions). This release covers some pretty important but critical bug fixes. Change log = 1.2.3 = Fixed: Legacy main site search replace issues. Fixed: Runtime error during plugin restore in multisite for some…

Read more

Prime Mover 1.2.2 – Main site support and Freemius library update

Prime Mover 1.2.2 is now released. This includes one of the most requested features – multisite main site support. This is only available for PRO version users. The following is the change log. Change log = 1.2.2 = Fixed: Outdated Freemius SDK Library. Fixed: Performance issues on plugin activation for some servers. Fixed: Support for…

Read more

Prime Mover 1.2.1 released!

Today we released Prime Mover 1.2.1 which is an important bug-fix release. This is also part of our two-weeks maintenance update cycle. Change log = 1.2.1 = Fixed: Runtime fatal errors during restore caused by corrupted files inside WPRIME package. Fixed: Search and replace URL issues in legacy multisites. Fixed: Refreshed Elementor cache when migrating…

Read more

Prime Mover version 1.2.0 – Maintenance Update

Today, Prime Mover 1.2.0 is released. This is a bug-fix / maintenance release. Change log = 1.2.0 = Fixed: Incompatibility with changing process IDs due to forwarded proxy server addresses. Fixed: Large readme.txt and splitted changelog to changelog.txt. Fixed: Marketing improvement for the plugin. We would like to thank @parabaditya7 for reporting this issue. The…

Read more