Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
The Old Man Posted June 18, 2023 Posted June 18, 2023 I was looking at the Subscriptions options in Commerce and noticed they seem to be incorrectly calculating renewals. E.g. Set up a subscription of $10 for 6 months with renewal the same price equating to $20 for a year… So that should be $20 per year, but if you save and then click on the +Add Member option… it shows renewals as going to be either free forever or free for the first 6 months and $10 the next 6 months ($10 a year). Also there is a typo, the number of months is displayed twice, but only if you select months, not years… Whether it’s messed up if you went live, I don’t know.
Solution Stuart Silvester Posted June 18, 2023 Solution Posted June 18, 2023 This is a feature for 'gifting' a subscription, which is why it's always free for the first term (at least), so this looks like it's working as intended. If you want someone to pay for a Subscription, create an invoice for them instead, adding the subscription product. We can fix that double month though.
The Old Man Posted June 18, 2023 Author Posted June 18, 2023 Ah, right, thanks I didn’t realise that + button was for that, on my iPad at the moment. Where is the option to show a subscription when registering? (So a new member must purchase a subscription). I thought it was on the registration/log in AdminCP settings page. I saw the option for setting a product of a certain value must be purchased, but it says configure up via the products page, not subscriptions. Thanks.
Stuart Silvester Posted June 18, 2023 Posted June 18, 2023 On the Subscription Plans page, there's a settings button in the top right (or it may be under a 'more options' menu depending on the size/orientation of your iPad). The Old Man 1
The Old Man Posted June 18, 2023 Author Posted June 18, 2023 Got it, thanks Stuart. Sorry they got you working on Gravy Day!
Marc Posted November 3, 2023 Posted November 3, 2023 This issue has been resolved in our recent 4.7.14 release of the platform. Please upgrade to resolve the issue, and if you see any further problems at that point, please let us know.
Recommended Posts