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