TOPIC: Front End Bugs

get similar errors on backend. these are the different errors and the pages i receive them on

Events menu
Warning: Invalid argument supplied for foreach() in /home/xxx/public_html/administrator/components/com_dtregister/lib/dtview.php on line 570

Warning: implode() [function.implode]: Invalid arguments passed in /home/xxx/public_html/administrator/components/com_dtregister/views/event/tmpl/list.php on line 73

Warning: Invalid argument supplied for foreach() in /home/xxx/public_html/administrator/components/com_dtregister/lib/dtview.php on line 489



Locations menu
Warning: implode() [function.implode]: Invalid arguments passed in /home/xxx/public_html/administrator/components/com_dtregister/views/location/tmpl/list.php on line 29

Pay Options menu
Warning: implode() [function.implode]: Invalid arguments passed in /home/xxx/public_html/administrator/components/com_dtregister/views/payoption/tmpl/list.php on line 28



CSV Export menu
Warning: implode() [function.implode]: Invalid arguments passed in /home/xxx/public_html/administrator/components/com_dtregister/controllers/export.php on line 105

disregard, this post. i synced my groups in permission menu, reset my permissions for the groups and it now works

Hello all,

I wanted to revisit the original posting here regarding the front end location bug. I submitted a ticket quite some time ago, but haven't heard anything back (granted, I initially forgot to provide the front end login to them).

The problem is that any location entered on the front end always renders a lat/long that is near Coffeyville, Kansas, regardless of the address that is entered (37.09024 -95.712891).

This occurs on both our development server and live server regardless of template with/without other extensions disabled.

Anyone having a similar issue?

I find that the all the member's confirmation numbers dissappears when the data is edited from the front end by the user himself,(not the Control Panel) - seems to work when CB integration is turned off.
But now, when I add a new member as the user, the confirm number defaults to the confirm number of the user and does not generate a new one.

FIX
No Confirmation number for Simple group registration:

if(DT_Session::get('Setting.User.type')=='G' && $member_confirmnum){

$members = DT_Session::get('Setting.User.members');
$i = 1;
if($members){

foreach($members as $key => $member){
$confirmnum = $tableUser->generateconfirmNum($event);

DT_Session::set('Setting.User.members.'.$key.'.confirmnum',$confirmnum );
if($i == 1) {
DT_Session::set('Setting.User.confirmNum',$confirmnum);
}
$i++;
}

}else{
$confirmnum = $tableUser->generateconfirmNum($event);
DT_Session::set('Setting.User.confirmNum',$confirmnum);
}

} else {

DT_Session::set('Setting.User.confirmNum',$tableUser->generateconfirmNum($event));
}

Hello all and especially you the fine crew of DTH Dev,
as everyone certainly notices, this forum is mainly crowded with bug reports for different versions of the component. You in the DT crew are very efficient with removing bugs, and in many ways, the component is really outstanding with all its functionalities!

There is unfortunately one major concern though with the component, or rather with the develompent strategy for it - that is the constant implementation of new great functionalities without ever stopping and seeing to that there exists at lease ONE STABILE VERSION! Many of us using DT Register administer very big events. I have been using this great component for six years for complex registrations and DT Register is the only component I have found really managing multi-language, selection limit enabled, visually easy-to-understand registrations, but each year, I have spent days and days trying to cope with disasters that different bugs in the code have caused. Please I beg you - STOP! The one thing that really would make this component perfect is taking a break from including new stuff and instead for a while putting all effort into producing something very stable.

Please do not remove this post as you have done with my same suggestion the previous years. This is the biggest thing on all my DT Reg using acquintance's "Feature wish list", i.e. not adding more features for a while .

Keep on the good work!

Cheers Ben

Thank you Ben - I agree. My project is now non-profitable, since I have to go throught lines of code to find out why things are not working like they are expected too, and since I have never received a response from the development team, I do not event bother to submit the problems I run into. I have paid twice for this component - the first time I ended up never using the component, the second time, a disaster with CB intergration and group registrations.