Support Central

gslitt91 I assume you're speaking to me. Yes, both events are closed now - the event was today.

I'm not going to update another site and cause them the same problems that messed up this client's event.

If my clients are experiencing this, and I'm easily able to replicate it virtually every time I test it, then either the settings are so confusing that I can't figure out where the "global" setting is that the "event" level option is changing, or this is legitimately a bug.

So I think we can step back a few paces and first identify EVERY LOCATION of any setting affecting the new feature.

If you'd like to continue testing - since it's the weekend - the client had created a test event: "GOLF OUTING PAYMENT (Aug 21, 2019)" which you might want to test with. He was testing a different issue that was causing problems with group registrations in DT Register 4.2.3 - which seems to have been resolved with the installation of 4.2.4, but I suspect the same issue will appear if you test that event. Feel free to make changes as needed to be able to test.

One last point that might relate to this issue: The client created their events by copying the prior year golf events. These events were not created from scratch. Is there a possibility that might have carried forward an incompatibility?

Either way, the client likely will not have many visitors over the weekend, and likely not overnight (they are in USA Central Time), so you should be able to test that test event they created without interfering with their website.

Thank you,
Ernie

saguaros So the settings should be as follows:

Configuration - General tab - "Duplicate Registration Prevention" = No
Event - General tab - "Duplication Prevention Override" = No

I believe that's how I had everything set up.

I will wait until this client has a new event and then I'll test it with that before causing any trouble for other clients.

swampscrapper The issue you describe has been the case for quite a while. I don't remember when it started, but my clients often have an administrative assistant register all the people in their departments - sometimes a dozen people - in a group registration and was routinely entering the assistant's email for all the registrants because they didn't want to add all their individual email addresses, or wanted the confirmation email to go to the assistant and not the registrants. That apparently no longer works.

I haven't received any complaints other than one or two mentions that it was an inconvenience, but I saw it right away because I test events I create for clients and had the habit of using my own email address for each member of a group registration. I can no longer do that.

Thank you,
Ernie

gslitt91 Which issue does this resolve? The ability to use the same email address for each member in a Detailed Group Registration, or the "Invalid field: A user account already exists..." error message?

Thank you,
Ernie

gslitt91 I upgraded another website to 4.2.4 and installed the components\com_dtregister\controllers\validate.php file that you had installed on the other site.

No luck. A person who had registered last year, but never activated his account, tried to register this year, but kept getting the error that a user account already exists. The customer didn't know his credentials, and I guess it wouldn't matter because he hadn't activated the account last year when he created it.

I've completely disabled the "optional" setting for user registration for this event, but it messes up this particular client because they're signing up as vendors and need to have an account to be able to log in to make payments, etc.

You've really got to streamline this whole process and the logic - too many settings in too many places creates so much confusion and upsets so many people! There should be a completely "passive" process so that if an email address exists, it does not demand a login or password reset, it does not prevent completing the registration, and simply links the event registration to the existing user account.

Thank you,
Ernie

gslitt91 So we have a total of three patches to DT Register 4.2.4? Are there others out there in other posts/threads that your clients should know about?

I have a suggestion: When you release each new version of DT Register and the inevitable bug reports begin streaming in, when you fix these bugs, update the distribution with an "a", "b", "c", etc. For example:

4.2.4a
4.2.4b
etc.

and notify the client what fixes the "a", "b", etc. version contain. Since you have taken over DT Register from the original developer, the new bugs introduced in each new version have been pretty much guaranteed and are now expected by experienced users.

I appreciate your quick attention to every issue that arises, but I've lost at least one client over the continual new and unexpected bugs. One has told me they will be using Eventbrite from now on. I fear that at least two additional clients are considering "firing" me altogether because of problems with DT Register, based on their expressed frustration.

Thank you,
Ernie