TOPIC: 2.3.1 Bugs...

As an owner of 2 licenses, I don\'t feel like my purchases are buying me anything more than a clear conscience.

I just installed 2.3.1 thinking that 2 prior bugs would have been fixed in this release but they weren\'t. The first bug was for the [email protected] connect error (ticket #859 on 10/ which you sent a patch for on 2.2.6 (thx). That bug is in this release again for those of us running MySQL on a separate box.

The second bug is that we still can\'t view registration records when running individual and group registrations. I submitted a ticket on 11/2/08 (ticket #881) along with a screenshot of of our server info (Joomla version) with the SQL we think is the culprit and still have not heard back.

I guess our only solution is to go back to 2.2.6 apply the patch you sent me and hope we hear back?

Regards,
Eric

Well, 2.3 was a complete rewrite, not just an update to the previous version. Despite tons of testing, we have found a number of bugs that did not show in our tests. Regarding your issues, please submit fresh tickets. As you should know, a serious issue warrants a ticket... not just a forum post.

And what do you mean you can\'t view records??

We ended up with a ton of tickets... mostly duplicate requests for the same issues. We\'ve been fixing them as quickly as possible and updating the download package frequently. Know that we are aware of the issues and taking care of them. Thanks for your patience.

Fair enough..

The ODBC error message is because the editGroups() function in the admin.dtregister.php had variables added to it but it still had the old MySQL query syntax in it.

problem:
$query=mysql_query($aqry) or die(\"Invalid Query Select : <br>\".mysql_error());

fix:
$database->setQuery($aqry);
$query = $database->query();

I got the fix from the patch file you sent and it\'s only 2 lines of code that were changed in admin.dtregister.php. I can handle that (I don\'t know why I didn\'t think to do this before to re-fix this).

As for the not seeing the registration records, I\'ll re-post the bug I found and wait for a fix.

We are starting to move into corporate accounts and DT register works very well for in combination with JEvents for an event registration product/company calendar for corporate events.

That\'s why I\'m so anxious to get this working properly in that style environment vs the typical hosted environment where MySQL is on the same box.

Regards....

New ticket #953 submitted for not being able to view event registrants.