|
Philip Wall
|
March 11, 2017 at 11:51 am
We have a few customers who paid via mirjeh, received a confirmation email with the event date but they are not associated or registered for that event in the back end. Customers then showed up to cancelled events. We have the latest version of EE and WordPress. We use would super cache and autoptimize and have followed EE guidelines on making cache exceptions. Can anyone help?
|
|
Tony
|
March 13, 2017 at 6:15 am
Hi there,
Are you sure they are not shown as a registration within EE but the registration is not ‘Approved’?
How are you viewing the registrations for the event to see if they are assigned to it?
The reason I ask is registrations are created very early within Event Espresso and then updated as the user goes through the registration steps, if they are receiving an email from EE the registration must exist within EE or it wouldn’t generate.
Or is the email from Mijireh/the payment provider?
|
|
Philip Wall
|
March 13, 2017 at 10:38 am
Hi Tony, they paid on the 8th Feb in Mijireh, they sent us the confirmation email they received with the event name and date and yet they are not in the system (Check the regs for the event/searched by email/by name etc) for that date or anywhere in the database (I checked via phpmyadmin). This happened with at least 7 customers over the weekend. The email is via the Messages and even had a transaction id. Yet I can’t find that email in our system. Bizare.
|
|
Josh
|
March 13, 2017 at 6:09 pm
May I ask is there a row in the esp_transactions table that matches the transaction ID from their email?
|
|
Philip Wall
|
March 14, 2017 at 7:45 am
Hi Josh, there is a row that matches the transaction id from there email in phpmyadmin. Looking at the info in the txn session data field, however, it shows registration details pertaining to a different future event. To be certain I checked that event and they are not registered for it. Is there anything else I can check?
|
|
Josh
|
March 14, 2017 at 8:57 pm
If you have a database backup that was made on or shortly after Feb. 8 you could check there.
|
