TOPIC: Who uses this for a business?

Hey Rich,

Can you point me in the direction of these Joomla 3.0 bugs that you say that you have documented?

Hi Jeff.

Here is an example of something in our readme file in the joomla 3.0 version of DT Register.

******************** PLEASE NOTE *********************************
AS of 1/15/2013 THERE IS A BUG IN THE CORE JOOMLA 3.0 FILES!!!!!
We submitted a bug tracker request for Joomla 3.0 but to be safe we recommend that you do the following:

Copy the file "folder.php" which is listed with the other DT Register installation folders into the path as follows:

\libraries\joomla\filesystem\folder.php

The bug in the joomla code will may prevent certain folders from being created during the DT Register installation. If you receive
errors during the installation verify the following folders exist and if they don't YOU MUST CREATE THEM AFTERWARDS:
../images/dtregister
../images/dtregister/barcode
../images/dtregister/eventpics
../images/dtregister/locations
../images/dtregister/uploads
************************************************************************

Rich

We use it extensively for 10 or so active events at a time. It's gotten so slow that I looked my name up today and it took about 6 minutes to bring it back. This is on a $800 a month firehost cloud server with a separate server for mysql. We've finally given up. DT Register is GREAT, but if you push it too hard the cracks start showing. The database structure is not good, which is part of the issue. We're actually paying to add to the core of CiviCRM to make the reg module a better system, and we're switching to that. If you don't mind flushing your records or you aren't running dozens of events, then this IS the system for you, but if you've got a big setup with thousands of records, be prepared for it to slow down. WAY down.

The other issue is, instead of fixing bugs, sometimes the bug fixes get rolled into a new release. With new releases come testing, changes to OTHER things and new bugs. That causes more work for me because I have to test it. When the new "click to add another" group function got added the fee fields with group limits broke because the system can't calculate it right. The fee fields appear UNTIL you hit the group limit and then go away, BUT THE EARLIER ONES STILL GET CALCULATED IN (This may have changed with the newest release, but we haven't upgraded). Same with group of 1. They can check our Married Couple discount box and get a discount for 1 person. Maybe that's changed. It should the group min for the fee field and DUMP the discount if the requirements aren't met at checkout. These things get fixed over time, but the database speed has not been, and that's just crippling us.

I've gotten more and more frustrated and have tickets that are 6 months old in the system that have gone unanswered. I stopped asking for help months ago and have just lived with the glitches.

Like I said, this is great for some people, but if you're pushing enterprise level stuff, you'll probably have to do what we did and move to something else long term. I wish it wasn't this way. I've got another ministry I know who LOVES DT and it works great for them. For us, not so much.