TOPIC: Frontend CSS and bad Cancel button

Hello,

The frontend CSS from DT Register's manage-event page uses a.register_button, .button with a background of their traditional green number 58B436. Which is in fact a lovely shade of green, but on the Chrome browser ends up making the buttons look like they have a dirty diaper. Should I simply edit the manage-event page and remove that rule, or it just layering wrong and I should actually modify a different rule? Are these rules set somewhere else?

The other problem comes in after I have recovered from the garbled button css and move on to actually editing the event (frontend). Once I get to the point that I either save my changes or cancel them, I would expect the module/component to drop me back at the main manage-event editing menu, but what it actually does is load up all the modules that are assigned to the home page, then squeeze itself in the main area between the left and right column data. I've double checked that all the other modules are set not to show when the manage-event menu item is selected, but the navigation from within the frontend manage-event component is all javascript run and I am having a hard time figuring out exactly where cancel/save&close redirect to.

Also, the menu items from my main menu stop working after hitting cancel/save&close on manage-event. I have to navigate back to the home page in order for things to set themselves straight and become usable again.

Any help would be appreciated!

Ok... I fixed the bad CSS, but I am still having trouble figuring out how to get the cancel button to do something a little more reasonable. I wonder if it has to do with a call made to mainframe->redirect("index.php?opt....")... either that or it is the way JToolBarHelper::cancel('cancel') works/doesn't work.

Anyone who can help me understand how to correctly redirect from a cancel/save/close operation effected from the frontend will have my deepest gratitude.

I have the same issue with the redirect to the home page when performing front end management actions. For example, I set the page class for the page to float so that my administrator will not be confined by my template's default parameters. However, if I perform any action or function in the manage records page, I get rerouted to the home page and the records page is crammed into the the mainbody of the home page unless I turn it off which means that any hint of the DT Register Front End Management page is gone.

This unfortunately makes the Front End Management functions unusable until I figure out how to set it up properly or is fixed if broken.

I will keep searching the forum for a solution. Unfortunately, the original poster's message had a little too much vinegar and not enough honey which is probably why no one responded. That said, I would very much like to know what the solution is to this issue.

Thanks,