Releases: Freemius/edd-migration
Bug fix (minor)
Merge pull request #22 from Freemius/develop [network-migration] [bug-fix] Was returning 'true' even when there ar…
Bug Fixes
-
Freemius::get_opt_in_params()
is usingwp_get_current_user()
to fetch the user's information. This function requires a set of cookie constants which are only defined after the inclusion of the network activated plugins. Therefore, manually define the constants when they are not set. -
Added protection for cases when more than one product is installed with the migration client-side script.
Multisite Network Migration, Manual Data Mapping, and EDD Renewals Sync
This is a major release of the migration plugin, covering the following:
Multisite Network Migration
The migration plugin and client code can now support bulk data migration from a multisite network. A multisite migration will only execute when a plugin is network-wide activated, and the plugin's license is active across all sub-sites in the network.
Manual Data Mapping
While the automated data sync with Freemius is great, as it's an automated process, there's no space for customization. Therefore, we enriched the settings page with the ability for custom data mapping.
EDD Renewals Data Sync
This is a super-important feature when migrating a product from EDD that already set for automatic-renewals, and there are active subscriptions. Basically, you can keep the subscriptions active, and when renewals hit EDD, they will be automatically synced to Freemius, logging all the required data and extending the license correspondingly.
Migration from EDD Bundle to a Single Product on Freemius with Plans
The feature was developed for sellers that are interested to stop selling add-ons and start selling plans instead. The migration plugin was enriched to support that use-case for a smooth transition from an EDD all-addons bundle to a single product on Freemius.
Client Migration Naming Conventions and PHP-Doc [minor]
Merge pull request #11 from Freemius/develop Develop
OOP + Client module non-blocking migration fix on WP Admin pages
- Turned the client migration code to object oriented which makes it more structured and extensible for other platforms. It also makes the code modification for developers way easier.
- After further investigation, the non-blocking migration code was still working inconsistently. We found that it was failing to process the migration when the triggering request was started from WP Admin, while it was migrating successfully if it was a public site-front request. The reason it was failing is permissions; we were not passing the auth cookies with the spawned request. After passing the cookies the migration started to work consistently for all requests.
Client module non-blocking migration fix
- Changed the calculation of the current request URL to only be based on PHP since
global $wp
not always available. - Added expiration to the migration unique ID transient, otherwise, if the non-blocking request fails, it will never migrate.
- Added setting option to clear all entity mapping.
Client module migration fix
Handled the use case when a module was purchased via EDD but the license was never activated on the context site.
The solution connects to the new after_install_failure
filter, tries to activate the license on the EDD store, and if succeed, migrate the license to Freemius.
Initial release
Merge pull request #2 from Freemius/develop Develop