Duplicate eMember Records w/eStore Purchase

[spotlope]

This is a curious problem that I’ve only started having today, after several days of flawless testing. I’m using WordPress 3.1.4 with the Thesis 1.8.1 theme, eMember 6.7.9, and eStore 5.7.1. The site sells online video-based training. There’s no free account option, and all class products use eStore for their listing, and PayPal Express to process transactions.

I’ve had three users in a row try purchasing a class. The transaction went as expected through PayPal, and they were taken back to our my site after purchase. I’ve been watching the database activity via HeidiSQL, and the user record is created as expected after the purchase. The users are getting their email prompting them to complete their registration, and the member_id listed in the URL arguments matches those in the database.

However, when the user fills out their username and password in the pre-filled reg form then submits, it seems the form is creating a new duplicate user with their reg info, but with no class attached (the membership_level in the db for this duplicate entry is set to “0”). Now there are two entries with the same email address, but since the user has no valid membership level assigned, they are effectively locked out of the content they thought they were paying for.

Any thoughts as to how this is happening and what I can do to get it back on the rails again?

For testing purposes, the site is http://www.womackworkshops.com/

thanks,

Bill Womack

[amin007]

If you run a test transaction with debug option enabled it will reveal the issue:

https://support.tipsandtricks-hq.com/forums/topic/how-and-when-to-enable-debug-and-what-does-it-do

To fix the accounts for the user who already paid simply edit their profile from your eMember member dashboard and correct their “Membership Level”.

[spotlope]

I tried a new transaction with a fresh debug log and registration seemed to work fine from a user perspective except I was redirected to the page for free membership, not paid membership. When I checked the logs all were successful except the one below.

Log says failure happens in the eStore_post_payment_debug.log.

[08/11/2011 6:28 PM] – FAILURE :Handling refund request…

[08/11/2011 6:28 PM] – FAILURE :Updating sales database talble with the refund amount: -39.00

[08/11/2011 6:30 PM] – FAILURE :Handling refund request…

[08/11/2011 6:30 PM] – FAILURE :Updating sales database talble with the refund amount: -39.00

I haven’t refunded this transaction so I’m not sure who this is referring to.

eMember – The database again created duplicate entries with part of the registration in each entry

eStore – had only one entry

WP User – had only one entry

Do you have any suggestions?

[spotlope]

I also wrote PayPal to see if there was any problem with my acount but there is not.

Any ideas here?

[amin007]

To me that looks remaining debug from previous transactions. So for the new transactions you are not getting any debug at all. Few obvious reasons are

– You may have turned off IPN in your PayPal profile

– You may have added a plugin to your site which is blocking PayPal IPN (bad behavior plugin is known to do this)

– ect.

This post will help you:

https://support.tipsandtricks-hq.com/forums/topic/what-to-do-if-the-debug-file-is-empty

So go through that checklist to find out the problem. Once you fix that up you will start to get new debug info when you do a transaction (the time and date stamp on each debug line will help you understand if you are looking at new debug info that resulted from the transaction you just did).

[spotlope]

I’ll look at your suggestion, but I’m not sure how that can be an old file. The previous debug files were wiped out on 8/10 and the new debug files are dated 8/11. Any other possibilities?

[spotlope]

OK, I went through the steps on the link above and information is indeed being written to the debug file. I’m at step 4 where I’m setting up the sandbox. I’m in the settings in eStore but I don’t see anywhere to “Enter your sandbox seller’s email in the ‘Paypal Email Address’ field.” Can you help me find that? Thanks.

[amin007]

WP eStore settings -> Payment Gateway Settings -> PayPal Payment Gateway Settings -> PayPal email address

This post might come in handy:

https://support.tipsandtricks-hq.com/forums/topic/quick-guide-to-paypal-sandbox-setup

[spotlope]

Thanks, I’ll try it right now!

[spotlope]

Okay, I’ve got some more detail for you. Via our logs and the results both in email and on the site, I’ve narrowed down exactly what’s happening. The transaction is going perfectly through the PayPal phase. The user is charged, their entry recorded in the eStore sales table, and the new member record is created in the eMember table (these tests have all been done as new members, not membership upgrades).

The disconnect is happening when the user clicks the link sent to them to complete their registration. The registration screen we’re seeing seems to be pre-filled with all the correct info per the sale. However, when they click submit to update their record with a newly-created username and password. eMember is creating a new record for them instead of updating the one created by eStore. The result is that we’ve got on record that was started by eStore with all their info except username and password, and one subsequent record created when they submit that has everything except the ID of the membership level they purchased.

So the question is this: what happens at the junction when the record is supposed to be updated that causes a new one to be inserted instead? If we can resolve that, this will all be working as expected.

[amin007]

It shouldn’t create a new record anymore. When the customer clicks on the “unique registration completion” link it just lets them choose the username and password then it is suppose to update that member’s record. I will send you an email to get site access so I can check this out.

[spotlope]

I’ve just filled out the form you sent me to so you can gain access to the site.

[amin007]

Found the issue. The PHP Session on your site is not working so the secret authentication code is getting lost when you hit the “Submit” button. This is why it is failing to find the corresponding member record.

You need to get your hosting provider to fix the PHP Session first. Who is your hosting provider? I hate it when hosting providers sell hosting without setting everything up on the server properly.

This post will explain more:

https://support.tipsandtricks-hq.com/forums/topic/php-session-not-working-correctly

[Author]

Posts