Summary
Prime Mover 2.0.1 is a quick maintenance release with the latest bug fixes and improvements.
Change log
= 2.0.1 =
- Fixed: Unable to restore tables due to duplicate foreign key index.
- Fixed: Show upgrade prices in annual for clarity.
- Fixed: Broken logo icon on the upgrade page.
- Fixed: Support for auto-adjusting user ID columns primary keys on restore.
New pricing plans and page
Prime Mover 2.0.1 makes it much easier to upgrade to any plan of your choice, depending on your usage scenario and purpose.
We now offer three types of plans:
- Monthly plan—if you want to use the plugin and pay the subscription monthly. This is useful if you want to use the plugin only for a limited time—for example, to do a special migration project for two months. Pay only two months to activate PRO features, not the entire year.
- Annual plan (discounted): This plan requires a subscription to be paid annually. It is useful if you plan to use the plugin for a long time and re-assess its usage annually. You can save more (38%) if you upgrade to an annual plan than monthly.
- Lifetime plan – if you are a big fan of the plugin and want to use it for your life (thanks!). Several long-term customers request this. They don’t want to pay on a subscription but only once for a lifetime plan. So here it is now 😉
The pricing page is updated to show all the plans:
Multi-currency support
Originally, only US Dollars were accepted when upgrading plans. Now, we accept Euros and GBP (Pound Sterling), which makes it easier for European countries (including the UK) to upgrade and pay in their currencies!
Choose your desired currency and upgrade in minutes. That’s it.
Bug fix – duplicate foreign key index SQL issue
This release fixes a bug in some restores of SQL tables using foreign key indexes. The restore will return a duplicate error on foreign keys, preventing the table from being created on restore and resulting in missing data after import.
This is now fixed and tested to work with Prime Mover 2.0.1.
Improvement – support for auto-adjusting users’ IDs on a primary index column
An improvement is added to this release to support auto-adjusting user IDs if these are used as the primary column itself. This is now possible with previous releases due to complexities. But with the latest release – it should work as long as that column ID is also named “user_id” to be automatically adjusted.
Drop us a message
Let us know your thoughts, comments, reactions, or issues with the Prime Mover plugin. We are always happy to hear your feedback, good or bad. Thank you!
Last updated: November 11, 2024