"Sign Up" and "Renew" problem

Hi James

Unfortunately, it is currently not possible to handle this requirement by Membership Pro. At the moment, when someone subscribes for same plan for the second time, the system will treat it as a renewal (so that it won't lost any duration of the subscription)

I can see that use-case here and it is valid. Unfortunately, it is currently not supported in Membership Pro

So someone will have to register for a new account if they want to subscribe for the plan for second time. I will see if we can add support for it, however, I must be honest that it is not easy task, so I don't think we can have it supported in less than 2 (or even 3) months

Sorry if this is an unexpected answer

Tuan

Hi, thanks for the prompt rely, as always!

I have some Joomla developers from freelancer who are managing my site development. They are php developers, is there any immediate guidance you can offer? They say they have an idea they are currently attempting now, to which I have posted this enquiry in parallel.

Is the following possible as an intermediate workaround???
*Customer with existing VPS1 finds they can not subscribe, only renew.
*They obviously contact us, we create a new package called VPS1_a and keep this in the background.
*We somehow get them subscribed to this.
*Any subsequent requests for VPS1 would link to VPS1_b/c/d/ etc...

Thanks

Hi James

Honestly, I don't know how your developers could do that, but I think if they can do that, it will work. Just a question, in case someone subscribe for same plan multiple times, what information we could use to show the difference between these subscriptions to so it to end users so that they can renew for the correct subscriptions when they want

Regards,

Tuan

They say they are looking at it now... I have no idea what they will try...

But I have given this some thought - I'm selling VPS servers, so if a customer wants 2, then they subscribe to an offer with 2 servers, we can discount these also to attract more custom.

If it comes to it, I will create VPS1x1, VPS1x2.... x3 ... x4 etc...

If a customer already has 1 VPS and wants another then they could possibly cancel and then purchase VPS1x2, or we create a package for this situation, with a coded reference/name, that doesn't show on the public website....

Seems logical, and I would power this with a spreadsheet/database to track things a bit better.

OK James. Hope you will come up with a good solution

Tuan