|
Natalie Parisi
|
March 24, 2015 at 12:46 am
In EE4, two separate transactions for two separate attendees share the same Line Item ID. The Transaction #, Reg Code, and Registration # all seem to be unique.
As a result of the shared ID, one attendee sees information of the other attendee on the post-registration details page, and the e-mail link to change registration details allows one attendee to change the other’s details.
I have at least 5 separate instances of shared Line Item IDs for transactions between different users for one event. How can I change these IDs so that the users can only access their own information, and prevent this from happening again?
|
|
Lorenzo Orlando Caum
|
March 24, 2015 at 8:09 am
Hi, I saw your note about the PayPal IPN not running. That is needed to update the registration and payment information in Event Espresso. I shared information on how to set it up here with the new PayPal.com design:
https://eventespresso.com/topic/default-registration-status-not-working-payments-not-going-through/
Thanks
—
Lorenzo
|
|
Natalie Parisi
|
March 24, 2015 at 11:32 am
Thank you, we’ve enabled IPN and resent IPN messages for the previous transactions. That should fix any future transaction issues.
Now is there a way to generate new, unique IDs for the transactions that have the same ID?
|
|
Natalie Parisi
|
March 24, 2015 at 3:22 pm
It seems like what I need to do is edit the REG_URL_LINK in wp_esp_registration and the LIN_code in wp_esp_line_item with a new code for each of the affected transactions. Is this correct? If so, how can I generate the right type of code for this, and is there anything else I need to watch out for?
|
|
Josh
|
March 27, 2015 at 12:59 pm
Hi Natalie,
I can advise taking the information from those transactions, then remove them from the system. Then you can go to the Registrations list view for the event and add the attendees via the Event Espresso admin. This way you can ensure that the correct relationships are made between the tables that handle line items, registrations, tickets, and transactions.
|
