|
tesscoadmin
|
January 22, 2016 at 11:22 am
OK, we’re seeing behavior that we can not explain. Summary: After completing a Pending Registration, an incomplete registration that has been attached to it.
EE 4.8.30.p
MER 2.0.7.p
Details:
1. Selected qty 2 and registered two attendees. Pri Reg was logged in.
2. Checked out using custom payment method which recorded an incomplete transaction, pending payment and registration in pending status.
Pending Email: https://drive.google.com/open?id=0B8ccouFZSgKwRmZZSzF4QUU0c0k
3. In the EE Admin, edited the payment to ‘Accepted’, set all regs to approved, and sent the pymt and reg detail emails.
4. Revisiting the Thank You page, an incomplete reg now shows up and the amount for that registration is now showing owed????? Thank You Page (2nd viewing): https://drive.google.com/open?id=0B8ccouFZSgKwYXE2eHlnX1dGUGs
5. Viewing in EE now shows the incomplete reg: https://drive.google.com/open?id=0B8ccouFZSgKwTXhYVHU2RWZvMFU
What the heck is going on? How could an incomplete reg get associated with a registration AFTER checkout?
HELP!
|
|
Lorenzo Orlando Caum
|
January 22, 2016 at 2:55 pm
Hi, you mentioned that a custom payment method is in use. Can you reproduce this issue with one of the other payment methods such as check or invoice?
—
Lorenzo
|
|
tesscoadmin
|
January 22, 2016 at 4:15 pm
I can not reproduce this with any of the other payment methods. We are testing and have multiple windows open when we’re testing so I don’t know if this might be related to the session management bug.
I know the registration is created before the payment is processed. Is it possible that going back during checkout or initiating another registration at the same time might cause this?
|
|
Tony
|
January 25, 2016 at 2:20 am
Is it possible that going back during checkout or initiating another registration at the same time might cause this?
Yes it would but we’d also expect that to also effect the default payment methods.
I’ve seen issues similar to this – https://drive.google.com/file/d/0B8ccouFZSgKwTXhYVHU2RWZvMFU/view
With session conflicts when opening multiple tabs to make registrations within the front end and the admin. Basically EE uses the session ID to keep track of the current active registration, if you start multiple registrations with the same session ID (multiple tabs) EE has no way of knowing which details entered onto which tab is tied to which registration and odd things start happening to the registration (like the screenshot).
Try running a registration in a Private/Incognito window whilst performing the admin actions in a standard window of the browser. Does the same happen?
|
