Has anyone stumbled upon this problem. If so, please tell me how you solved it. After upgrading my customer's site from J1.5 to J2.5.9, including DT Register, following all the manuals and directions on how to upgrade and migrate, the site is working fine. The problem is that DT Register does not check the fields for validity and the final Next-button on the confirmation page is simply dead. Nothing happens when you press it (looking at the source shows that is has no action defined). The DT reg version is now 2.8.5b.
I am very, very disappointed at the DTH support. I opened a ticket on this problem 10 days ago. I raised the level to urgent three days later as there was no response. One week after the ticket was opened they logged in and updated the component from 2.8.5a to 2.8.5b but did not test it. I performed a test the same day and told them about the negative result. Still no reaction, no answer after that, almost four days now...
I am experiencing the same trouble for group registrations. Individual registrations seem to be working fine. Two things that I have noticed with the group registration is that when coming to the summary page after completing the group, there are no member names listed (fields for name are blank) and pressing the "next step" button, seems to validate the security code, however it doesn't move on to the next step.
I have submitted my ticket this evening, I am hopeful that I hear a response soon.
My experience did not go though a Joomla upgrade, only an upgrade to DTRegister to the latest version from one that was about 8 months or so old. Running Joomla 2.5.9 and DTRegister 2.8.5b.
My problem was finally solved after my message here in the forum... The DTH suport disabled the jQueryEasy plugin, which made the DT Reg work. But they didn't notice that the change killed the entire dropdown menu.
That pointed me inthe right direction, though. I found that jQuery was loaded also in the template. Disabling it in the template and disabling jQueryEasy and loading Mootools for the dropdown menu solved the case. I do not know which of these components was behaving badly, but it was evidently a jQuery or jQuery/Mootools conflict...