Members Expiring Even Though Payments Are Made

Hi Tuan,

For some reason new members on my site are expiring even though they are making recurring payments via Paypal. I've had 2 this week who suddenly could not access the "members only" content on the site. When I checked their accounts they were both expired and had been removed from the Joomla user group that grants them access.

Here's a quick screen capture that explains the problem in detail.

Why would users be "expired" when they are still paying via Paypal?
How can I make sure that this doesn't continue?

Thanks!

I was just taking a closer look and I see that the duplicate accounts are there because a new account is created each month for the recurring payments (is that correct?)

For example...

-User signs up March 1st (for a 1-month, recurring membership)
-This account expires after 1 month
-A new account is created for that user starting April 1st
-Etc

This explains the duplicate accounts, BUT...it seems like people are losing their Joomla user account status when their account is created the second time.
-When the register they are assigned to a "members" Joomla user group.
-When a membership expires I have set Membership Pro to remove that member from the "members" Joomla group
-However, they should NOT be removed if their membership is recurring

It looks like they are being removed after 1 month (when this duplicate account is created). Why are they being removed from the Joomla group and how do I fix this?

Thanks again

Hi Dave

Infact, each time payment happens, the system will create a new subscription record (not a new account). To be honest, I don't know how can the user loose his Joomla groups in this case.

I will check the code carefully again on tomorrow morning and then I will update you ! Are you using latest version (1.6.2) of Membership Pro ?

Tuan

Hey Tuan,

Sorry, I'm using the wrong terms I guess. Yes, the system creates a new subscription record and at that time my users are losing access to their Joomla user level.

Yes, I am using the most recent version of the component. Thanks for looking into this - I'm interested to hear why this is happening.
Thanks!