TOPIC: [SOLVED] Next Step Button *Not Working*

Hi there,

I am using Artio JoomSEF, and SEO handler. I had the same issue with the NEXT Button. I believe it had to do with my SEO handler messing up the original url. Therefore I did disable for DT Register component the JoomSef handler in teh backend of Artio JoomSEF and then everything works just fine.

I would suggest to DTH to consider a plugin that handles SEO for Artio JoomSEF or other popular SEO handlers.

Best regards,

Federico.

I am having the exact same issue. The NEXT STEP button doesn't work when attempting to register for any event.

The SH404 Skips, Donate, Register, and Jevents but it still doesn't work.
I have checked and rechecked all CUstom Fields and some of the events aren't using the Custom Fields. I am at the end of my rope on this. I have spent days, trying to get this to work.
This component shouldn't be this fragile. I'm really feeling disappointing that this issue has been better addressed by you guys because apparently, this is an ongoing issue.

DT Register is not this "fragile". If all is setup correctly, this will not happen... unless there is a java conflict coming from your template or something like that... which is rare, but can happen. If you can't figure it out by other posts on here, submit a ticket and we'll be happy to help. 90% of the time, this type of thing is due to improper setup. We can help sort it out though.

I have received a couple of emails today from people saying they have had problems with the "Next" button as well. They say they get "Error on page" and will not go further. Most of the registrations have gone on without incident. We are talking about 1-2% of our registrations are having problems.

I have not been able to reproduce this on IE8 and FireFox. We are running the latest DT Register and I have gone over all my custom fields.

I'm having the same issues!!! after next step it just displays the Event Text at the top left of the page....and that's it, nothing else.

Nothing is submitted at all. I believe that it broke after I changed the custom field registration "selection amounts" field.

This seems to be a common problem and looks to be a real bug!!

Has anyone else fixed this ??????

I had the same issue and to get to work I had to disable SH404SEF component and turn off SEF in Global Config. There is an apparent conflict and we haven't figured a work around yet.