TOPIC: [SOLVED] Receiving Empty Registrations!

Yeah, I even checked with my hosting provider (GoDaddy) and had them analyze the hosting account and server and they said everything server side is good to go. They said that the component sends a lot of server / database requests and the issue is component related, not the hosting account or server.

I am really bummed out because a lot older versions of DT Register worked fine. Latest versions do not and are not reliable.

We need a fix to this serious issue.

Yes I really hope DT team can get to provide an updated comment on this soon - especially as it's a multi-user experienced issue and not just me. I fear other users who don't check their 'Records' listing at the back-end might not even be aware of looming disaster until the complaints start coming in from their customers....

Vostokoved - Answering your Q's above - Yes my events are still public - My audience aren't yet 'ready' to commit to signing up pre or during registration and I need to keep them that way for the time being....

I do use PayPal for some of my events.... Of all the many, many instances of 'blank registrations' I've been getting none have been for the events where I take PayPal... yet.... Trouble is my PayPal events are very low volume compared to some of my other events - and so this might not mean that the PayPal route is safe from this issue.... As I say it affects around 1 in every 10 of my registrations right now.... Although having said that, 1 poor lady signed up 22 people yesterday for an event (I have it set to Individual Reg only - so she did the process 22 times) - In her case 17 failed and recorded only the name and e-mail - no other details, and only 5 succeeded! I have e-mailed her to explain and apologise but no response from her yet - I suspect she's furious at the time she spent being wasted

Andy

POST EDIT: DTH just suggested that 2.7.2c may have solved the issue... Yippee!!! Upgrading now to try it out - Will report back here

DTH - Just an idea - As this big problem is a tricky one to track down and eliminate, is to possible to 'toughen up' DT Reg and at least stop these 'ghost' registrations getting through...

Is it possible to check whether or not the Event name has been captured prior to writing the registration to the database - in cases where it hasn't can the system throw a 'Sorry something has gone wrong - Please try again' type message?

Not ideal as it's still hassle and dissapointment for the end user BUT it's better than having them thinking registration has worked when really it hasn't..... as is our current situation in some cases....

POST EDIT: DTH just suggested that 2.7.2c may have solved the issue... Yippee!!! Upgrading now to try it out - Will report back here

I am not so much concerned with "ghost registrations" as I am users not being able to register because the component fails during the registration process (see my previous above in this thread)... which, tends to create these mostly blank or "ghost" registrations.

Is there another update that addresses this?

Just upgraded to 2.7.2c....still getting blank admin emails.
Registrants get all the information, but the admins NOTHING.

bubberz - if your admin email is blank, it's probably not configured. Go to Configuration -> Emails. You have to setup the content and subject of the admin email.