TOPIC: Just Purchased... Several Bugs

Just purchased DT Register after careful consideration, my config is as follows:

Joomla 1.5.9
JEvents 1.4.3 RC2
DT Register 2.4.1

Critical Error, I add the DT Register Eventlink hack version 1.6 to the content of my event using the following code:
{dtregister}78{/dtregister}

It creates the \"Click Here to Register for this Event\" link, however, they all link to the first event added in DT Register, no matter what number I put in. For example, Item ID 78 is my first event, so if I put {dtregister}82{/dtregister} in the content, it still links to 78 instead of 82. ???

Another strange thing I\'ve noticed is that when listing the events under Event Management in DT Register, my pagination doesn\'t work. I can go to \"Show All\" near the filter menu, but if I display a list of 5 and then hit next page I get a javascript error.

I can live with the pagination error, but I really need that little hack to work.

Charles

First of all, you made the right choice in your purchase

Second, for the plugin, please modify the file:

/plugins/content/mosdtregister.php

Around line 49 you\'ll see code starting with:

$sql=\"select ...

Change it to:

$sql=\"select distinct(a.id),a.publish_up,if(CURDATE()>b.cut_off_date,\'y\',\'n\') as cut_off,a.*,b.cut_off_date, b.waiting_list from #__events a ,#__dtregister_group_event b where a.id=$eventId And a.id = b.eventId AND a.publish_up >= NOW() AND a.state=1 ORDER by a.publish_up\";

See if that does the trick for you.

Regarding the pagination, that is an issue in 1.5 legacy... works in 1.0. Since our 1.5 native version is just around the corner, we\'re not wasting time on things like that to get the native version out the door. Thanks!

Thanks! That definitely solved the issue! Are you going to make this fix part of the next version of the plugin, or did I download an old version?

Charles

P.S. So far very impressed with DT Register, although I\'m going to have to do a lot of hacking around with the source code. There are a few things I wish it did, but I understand that these may be custom options most users may not want.