July 7, 2011 at 2:40 pm #3743ZainParticipant
Sorry for all these messages. I tend to test quite extensively and I’ve just found quite a major issue:
When an existing user upgrades to a Premium account, they are brought back to the registration form. The fields are pre-populated but they can’t use the same Username or Email address to register as a Premium member.
This leads to either:
- Users needing to be manually upgraded (time consuming for the Admin)
- Or registering a second Username (redundancy in the system)
- Or even worse, needing another Email address.
Is there a way for the User to be able to continue using their existing login information when upgrading?
ZainJuly 8, 2011 at 12:30 am #34076amin007Participant
“When an existing user upgrades to a Premium account, they are brought back to the registration form” – Thats not correct… When an existing user upgrades they don’t have to go through the registration process anymore. It simply upgrades their existing account and notifies them via an email telling them that their account has been upgraded. This page will explain more:
The plugin can handle upgrades if the user is logged in as a user while making the payment for the upgrade. It can also detect account upgrade payment based on the email address used to make the payment. If the user is not doing any of the above then the plugin has no way of knowing that this user already has an account and treats him as a new member and sends the registration completion email.July 9, 2011 at 7:59 pm #34077ZainParticipant
Thanks for the clarification. The issue here is more to do with the problem that arises from when the user isn’t logged in. Some users like to log out of a system and so, if those ones try to upgrade, they’ll be presented with this scenario where they get 2 accounts.
The solution for this is simple enough (and I discovered it while using the WishList plugin) – they add a “Existing users, please click here to log in” box just above the registration form.
The registration variables are passed from the page to the login page so the Users account makes a seamless transition and this situation is avoided. Obviously, new users use the registration form.
Is it possible to implement this? This is the only thing feature that actually stops me using Your plugin over WishList’s right now.
Yeah, I’ve got other feature requests but they’re not that important. Now you’ve got the “Hidden Text” issue working, if you can implement this, then I’d rather use eMember and recommend it on my site.
This issue, however, is one that I feel is crucial to the registration flow and would benefit other users. The Aweber List field in the Level settings would be useful too, although, right now I could achieve that through the eStore settings, I think…
Thanks for all your help Amin. I’ll be doing a review of eMember shortly – your customer service is excellent!
ZainJuly 19, 2011 at 1:50 pm #34078trockMember
+1September 20, 2011 at 4:38 am #34079ayelaParticipant
I’m having somewhat the same problem. When my free members upgrades it’s creating a second account for them at the “gold” level. However, they can only access the free content. The gold level just sits in limbo until I manually upgrade it. Usually by deleting the free account. If I understand the documentation correctly, the system should recognize their account if they are logged in. If not, it should be ok if they use the same email address in Paypal. Correct?
I do have your Estore and the main “buy” button is on the free download page. Is this a conflict? Should I create a separate buy just for upgrades? I do have the “use secondary membership” checked.
Thanks for your help.
KimSeptember 20, 2011 at 11:49 pm #34080adminKeymaster
Please do the following:
1. Deactivate and delete the currently installed version of the plugin(s).
2. Download a fresh build of the plugin(s) from here:
3. Upload and activate this version of the plugin(s).
Then enable debug on eStore and do a test transaction so we can find out what is going on. This post will explain how to enable debug:
- You must be logged in to reply to this topic.