|
John Ballment
|
April 7, 2015 at 11:22 pm
Hi guys,
We’ve currently got a reunion booking site running, http://sydney.anglo-indian-reunion.com/bookings/reunion-booking/, were one person can register for multiple events (event date-times) over the reunion week. At the checkout we’ve disable the changing of attendee details and therefore the attendee 1 details is automatically used for all the event date-times (as per EE4’s built in functionality).
I’ve come across one instance where a transaction with 3 event date-times has had the attendee successfully assigned to only 2 of the events the other event seems to have no attendee details. Please see screenshot attached.
I’m hoping the simple fix for this issue maybe just an sql update to point the transaction to the attendee as I couldn’t see anything that I could do via the front-end.
|
|
John Ballment
|
April 7, 2015 at 11:24 pm
Sorry the link to the screenshot is https://drive.google.com/file/d/0B41AmJGuwcvRRTFGeUJDZnNGN2c/view?usp=sharing
Regards
John.
|
|
Tony
|
April 8, 2015 at 4:49 am
Hi John,
The screenshot provided links to a ‘Visits from Organic Search’ graph, can you recheck that please?
What is the registration’s status?
|
|
John Ballment
|
April 8, 2015 at 4:54 am
Sorry, here is the correct link – removed (Tony W).
-
This reply was modified 9 years, 7 months ago by
 Tony. Reason: Remove image
|
|
Tony
|
April 8, 2015 at 8:24 am
Thank you for the updated link, I have remove it from view but support can still access it.
I’m wondering if you site is running out of memory and on that occasion did so on the 3rd registration, causing the error shown.
Can you go to Event Espresso -> Maintanence -> System Information
Check what the wp_memory limit is currently set to.
I have requested some feedback from our developers, but it is likely the best way to fix this is to re-create the registration through the admin, you can use the same details as the current registration, applying any payments to the new transaction that may have already been applied and then the cancelled the ‘broken’ registrations.
However please first check the memory limit using the instructions above.
|
|
John Ballment
|
April 8, 2015 at 7:54 pm
Hi Tony,
WP_MEMORY = 40M. I’ve upped it to 96M and the WP_MAX_MEMORY_LIMIT to 720M.
As for the booking, I was hoping to just to use something like:
UPDATE wp_esp_registration
SET ATT_ID = 939
WHERE TXN_ID = 3792
AND EVT_ID = 397
AND REG_ID = 1615
AND ATT_ID = 940
in the backend. BTW I know that I only really need the REG_ID in the where clause but everything else is there to ensure I don’t accidentally update the wrong record.
Regards
John.
|
|
John Ballment
|
April 8, 2015 at 8:07 pm
Hi Tony,
I’ve taken your suggestion on board about recreating the registration and I’ve opened registration 1615 via the front-end and from there I’ve been able to cut and paste the details from Attendee 939 to Attendee 940 and now everything looks correct. (No SQL required)
Unless anyone sees a problem with this for resolving the issue hopefully I’ve kill both birds, updated the broken record and upped the memory limits.
Let me know if there is anything else I should look out for.
Regards
John.
|
|
Tony
|
April 9, 2015 at 8:33 am
Hi John,
That should work fine and is a perfectly valid work around (I didn’t think of doing that before so thank you 🙂 ) to double check look within the transaction, if all of the details are correctly displayed then this should be fine.
You can also confirm by downloading the Invoice/Receipt for that transaction, again if all information is correct then all is well.
With a Memory limit of 40MB this sounds like the most likely cause of this, (hitting the WP memory limit as EE was updating the 3 registration) but I would recommend monitoring the next few registrations just to confirm all the details are saved correctly.
However can you tell me if those registrations were the last 3 spaces on the event?
|
