Closed (works as designed)
Project:
Commerce Registration
Version:
7.x-2.x-dev
Component:
Checkout
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Nov 2012 at 21:54 UTC
Updated:
22 Feb 2013 at 17:46 UTC
I have determined that Registrations are not being saved at all in my system. I set the Rules to set the Registration as completed when Checkout was completed. Contrary to the Read me there is no Rule setting to mark the Registration as "Paid". Is there another way to get the Registrations to save? My client is anxious to get the Registrations live. Any help is appreciated.
Comments
Comment #1
jpontani commentedDownload the latest -dev snapshot. The issue is that in the previous versions of Registration, there was no Registration State entity, it was simply a flag on the registration itself. Once ER went to registration state entities, that rule no longer worked.
I will add a new release after I get some other patches in tonight that should also take care of this problem.
Comment #2
LizD commentedI installed 7.x-2.x-dev and I still have no Registrations saving. Am I missing a step?
Comment #3
jpontani commentedIf you have access to the database, can you check the registrations table to see if there is anything in there?
Comment #4
LizD commentedI updated to 7.x-2.0-beta3+15-dev and it solved the problem BUT I then updated to 7.x-2.0-beta3+18-dev because of the problem with the who the registration is for select list and the registrations are no longer saving. I am rolling back to 7.x-2.0-beta3+15-dev as I don't have anything in between. Thought you should know. See my other post under the Who registration is for question for problems in 7.x-2.0-beta3+18-dev with the select list.
Comment #5
LizD commentedI am using 7.x-2.0-beta3+15-dev
I am updating this to critical because I have determined that registrations do not save when connected to the real PayPal site. They save fine when using PayPal sandbox or the Commerce testing payment. This is critical because it will work fine in a development environment and fail totally in a live environment leaving you with a paid registration and no way to connect them to the people who registered.
I also determined that the registrations do not save at all until PayPal payment is completed. If the registrations could save BEFORE going to the payment gateway that could solve a lot of problems.
Comment #6
jpontani commentedThis is fixed in the latest dev. They should be saved on submitting the registration info form.
Comment #8
caktux commentedThis fix now causes the registrations to be saved prematurely. I don't think we want to save the registrations during the checkout process since they're kept even if the user clears his cart or leaves before paying and it changes the available slots.
I ended up reverting commit 4c8f917 and registrations are saved after checkout as expected.
Maybe this should be an option?
Comment #9
jpontani commentedRegardless of when they are saved, there will be an issue with someone's setup. In the Registration States config you can select which states go towards overall count of slots filled. Currently CR uses the 'pending' state for initial registrations and then switches that to 'complete' when the order has been completed. Make sure you have this config set, and then 'pending' registrations will no longer change the available slots.
There is a rule action to delete all registrations on an order. You could create a rule that deletes all registrations for your active order upon clearing cart, or create a cron rule that prunes order registrations for orders that haven't been completed/paid etc.