CiviCRM Community Forums (archive)

When test-driving event online registration on the registration page the e-mail address is initially set to the email of the logged in user.
You proceed the registration to the end and, if everything is set as it should be, you finish the registration ok.

Now proceed to the second online registration in the same way. As you enter the reistration page there is an error:

Oops. It looks like you are already registered for this event. If you want to change your registration, or you feel that you have got this message in error, please contact the site administrator.

You cannot create a second test registration.
The solution: Never use the e-mail of the user logged in. Always change the proposed email address in the registration page.

To me, a first time user will doubtless be blocked by this; I consider this an annoying bug.
The registration page should check for e-mail already registered in the post process and not in the pre process.

Your suggested change would certainly make things easier for an administrator who is testing their event setup. However, I'm wondering if this is the correct use case to optimize for ??

Thinking about a "regular user" who has already registered for an event, and inadvertently tries to register again - it seems friendlier to tell them up-front that they're already registered, rather than waiting until they fill in the form (potentially with billing info) and submit it.

Also, I think we detect the "already registered" state based on the logged in user's contact ID, rather than any specific email address used during registration. The best way to run repeated test-drive tests is to do it without being logged in.

My understanding of test-driving is the use to test the configured procedure, which is normally done by some sort of administrator.
On top, why make things difficult. The test drive Button is there, why just not make it work as normally expected?

If the same process drives also the live registration, testing the already registered status post instead of pre  is a small penalty for the advantage of unobstructed testing.
I would really like to see this change. I has cost me many hours extra work of initial testing until I came by chance accross the above mentioned solution

It does not worry me anymore. I know the solution to circumvent the problem. My post had just the intention to help those that like me start afresh and bang their head against this problem.

I had thought that making the civicrm user friendly was everyones concern. Never mind...

I will add a FAQ, this is a good Idea

My remark was to signal that I do not understand or can't agree with the logic that has been put forward to justify the rejection of the proposed   change. I have no difficulty to accept certain limitations as long as I can see a reasonable argument.