Migration to 3.1 thread.

[F1shSticks]

Hi all, I am about to start the migration and have already asked Glen some questions about the best approach.

Here is some useful information about the migration process:

1. First, upgrade the package to version 3.1, then update your code.
2. Publish your extension and make sure everything is working.
3. After that, I will be able to create the new plan and test it in the development environment without breaking anything.

We also discussed the possibility of flagging plans as "test" plans that only appear during development but can be activated once extensions are released. However, this has not been implemented yet.

Please share your migration progress in this thread as well.

Good luck !

[limbuscode]

Tried to migrate and this happens when I call openPaymentPage()

[limbuscode]

I figured out what caused the error:

I was doing this:
document.querySelector('#btnUpgrade').addEventListener('click', extpay.openPaymentPage);
instead of this:
document.querySelector('#btnUpgrade').addEventListener('click', () => extpay.openPaymentPage());

Now it works!

[F1shSticks]

I have finished the migration. The only issue I encountered was an error after the customer selected a plan and was redirected to the Stripe checkout page. It turns out you have to activate the portal first on this page: https://dashboard.stripe.com/settings/billing/portal. After that, everything worked fine.

[Glench]

Yeah, there's a note to do that on the home page for new developers before the extension goes live.