-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrating subscriptions #341
Comments
Internal Help Scout ticket: https://secure.helpscout.net/conversation/2071791287/24814 |
From customer in a support ticket:
We now advise to update the theme and leave the database intact — which holds the subscriptions for Pronamic Pay and e-commerce plugin (e.g. Gravity Forms, MemberPress, WooCommerce Subscriptions). But this is not always an option:
Migrating the
pronamic_gateway
,pronamic_payment
andpronamic_pay_subscr
post types and associated post meta will continue the recurring payments for subscriptions in most cases (as the reference to the Mollie customer and mandate is nowadays stored in the subscription post content JSON). However, if the gateway configuration post ID has changed during migration, updating the_pronamic_subscription_config_id
meta of the subscriptions to the new configuration post ID is also necessary.Although the recurring payments are possibly starting fine after manual migration, some references (such as WordPress users, source IDs, etc.) are possibly broken after migration. This might result in loss of functionality (for instance, it is not possible to use the Gravity Forms form subscription notifications anymore if the form entries are not migrated or have changed IDs).
Can we improve the process of migrating subscriptions to a new website? Maybe with a separate import/export add-on plugin? Implementing custom tables in #234 might also help to ease migration.
Internal Help Scout tickets:
The text was updated successfully, but these errors were encountered: