TOPIC: Empty and Missing Registration Records

I just checked the database and in the user table the records are created, but the amount is 0, not sure why, since when I registered it clearly said that the event amount was $1.

So if the user records are being created, but I can't see the registration records through the component, something else must be going on...

please help!

thanks,
Laura

li_gordon - I responded to your support ticket but wanted to reply for the sake of others.

I looked on your site and saw that you are using 2.2.2 of DT Register. Do you realize how old that is??? That was released over a year ago. We have fixed and improved TONS of things since then therefore there is absolutely no reason for us to support that old of a release. You need to upgrade. Your issue will no longer exist after you upgrade. When we release new versions, they often are for added features, they almost every release also includes bug fixes and improvements to resolve issues like what you are having. You should receive our email newsletter and be notified of updates. Also you can subscribe to our news via RSS, Twitter or Facebook. There is no reason to not stay informed or to keep your extension updated.

I have a ticket open too right now (#2898) and it seems, from my lengthy investigation from yesterday, that what is happening in my case with the completely empty records is that in dtregister.php, in the displayPaymentForm() function, there is a call to serialize the data from the session (what the user submits in the registration form) and store it into the database in the #__dtregister_paypal_session table, specifically in the "data" column.

However, in my case nothing is getting added into this column at all, and I'm not sure why that is just yet, but it is no wonder that when the user returns from making their payment at Paypal that nothing is displayed and no emails are sent because on the return the paypal_payreturn() function gets called, but it really cannot do anything when it unserializes the data because there is nothing in there, so nothing works as expected.

Still haven't upgraded completely to DT 2.5. I will do the upgrade, then see if I am still having the same problem with authorize.net registrations appearing in the database but not appearing in the Registration Records. I did notice one thing. For the majority of the missing records, the registration type variable is blank. All records that do show up in Registration Records have registration type = | in the database. Maybe this information is useful.

PROGRESS:
I've downloaded a copy of the site to my local PC so I could do some real debugging to figure out what the heck is going on and now that I've done so I've figured out that for Paypal, the reason why my system is not storing anything in the data column of the paypal_session table is because the call to mysql_real_escape_string results in an error since it expects a resource of the mysql type, but I am using mysqli so an error is thrown and nothing is returned and that's what gets stored in the database.

The developer should be using the built in methods for the JDatabase object of Quote(), nameQuote() to escape the strings in an independent way that doesn't matter which driver is being used.

Quote() should be used to escape the data about to be input into the database, while nameQuote() makes sure that field name has the proper quotations placed around it (for MySQL these are backticks ` `).

I'll continue my testing and see what I can put on here for others to use.

Starting at line 1640 of dtregister.php you will need to uncomment the $userId variable line and then make some changes to the $sql variable line, but the end result looks like this:
The above will make sure that the session data is serialized correctly when using the MySQLi Driver.

Then on line 1694 (where the $punct variable is defined) you can pretty much get rid of it and then replace the line after it (the one for $billing_info) with the following:
Then on line 6523-6525 you can replace those lines, which look like this:
With just one line:
Some of these changes might also be applicable to authorize.net but since I don't use it I can't really test it.

Now I need to make sure that emails get sent out correctly via this method...

Hope the above is helpful and I hope the developer gets these fixes in, because it's been a big pain to work through.