That's really strange as it was confirmed to us that this bug was fixed in 4.6. But it isn't. See the conversation of the ticket below. I'm quite shocked that this billing bug is not addressed yet.
I'm lucky tech savvy enough to run a SQL query from time to time to clear things up but this is quite an issue since this bug was implemented in 4.5
Anyhow, I wish to thank you for the quick response 🙂
---------------------------
Here is the conversation of the e-mail in question:
Hi,
unfortunately I can't share any date, but as you see in our news section ( https://invisioncommunity.com/news/ ) , we've already started posting about 4.6 futures which means that it's not that far away:)
--
Daniel Fatkic support@invisionpower.com
{#HS:1407357784-43049#}
On Mon, Feb 1, 2021 at 1:42 PM EST, Sjors Krebbeks wrote:
A quick clarification for my mail above: I try to determine if it's worth to wait or that I have to implement a fix/work around myself (That is of course unsupported by IPS). To prevent lost revenue.
On Mon, Feb 1, 2021 at 1:33 PM EST, Sjors Krebbeks wrote:
Hi there,
So if I understand correctly 4.6 will be a minor update (4.5 was quite large if you ask me, so I'm quite hesitant with updates where either the first or second number changes). Well, glad to hear that it will be a minor update.
Any estimation when the fix will be rolled out?
Kind regards,
Sjors Krebbeks
Lowepost
On Mon, Feb 1, 2021 at 3:07 AM EST, Daniel Fatkic <support@invisionpower.com> wrote:
Hi,
yes, this should be possible in 4.6
--
Daniel Fatkic support@invisionpower.com
On Thu, Jan 28, 2021 at 1:00 PM EST, Sjors Krebbeks wrote:
Hi Daniel,
Thanks for your response! Glad to see that it will be improved in the future. Will there be a way for current subscribers to re-subscribe in a minor version update in the nearby future? If not, do you know a work around so I can get people to re-subscribe (Without admin intervention for every transaction)?
Kind regards,
Sjors Krebbeks
On Thu, Jan 28, 2021 at 7:25 AM EST, Daniel Fatkic <support@invisionpower.com> wrote:
Hi,
we have implemented few subscription improvements to 4.6 and I can confirm that this will also be improved.
--
Daniel Fatkic support@invisionpower.com
On Tue, Jan 26, 2021 at 4:28 PM EST, Sjors Krebbeks wrote:
Hi there,
Here is one of them: test1@lowepost.com
And indeed, we don't have to option to renew enabled by default (We prefer it if people re-purchase the subscription 🙂 ).
I put a subscription on it we don't offer anymore and set the expiry date in the past to make it expire.
This issue is there since we upgraded to 4.5 (Last weekend).
On Tue, Jan 26, 2021 at 4:09 PM EST, Jim Morrissey <support@invisionpower.com> wrote:
Hello,
Do you have an example user's display name which we can investigate? While this is true in some cases, such as a cancelled purchase without the option to renew, I want to be sure it is not one of those.
--
Jim Morrissey support@invisionpower.com
On Tue, Jan 26, 2021 at 3:58 PM EST, Sjors Krebbeks wrote:
We upgraded to IPS4.5 and since the upgrade it's not possible for clients to purchase a subscription if they have an expired subscription in the past.
They are getting this error:
Hi!
You already have a subscription, and cannot purchase another.
Error code: 2X379/6