A user registers, goes to the confirmation page, then hits next. The user then gets dumped back to the events list page. After MUCH testing this is what I've found...
happens in both IE and FF
happens with cookies enabled or disabled
happens with popup blocker enabled or disabled
happens with antivirus disabled
happens with windows firewall disabled
This happens for a user who is sitting in front of their computer and registering. If a user is remoted into another users computer (we used Go To Meeting) then it works.
I was working on my clients computer via Go To Meeting and it worked for me EVERY time. When I had the client do it locally while i watched it never worked.
I had another user do the same thing. On his computer it never works then I had him use Go To Meeting and connect to the same test computer. It worked for him every time using Go To Meeting. Then he also had the local user try it and it never worked.
Any ideas anyone???
By the way, when I register on my computer it works with IE8 and FF.
Is it some setting on the computer, firewall, browser??? Help!
Based on the fact that your license is nearly a year old... the first question I have to ask is what version are you running? The logical first step is to update to the current version (if needed) to see if that resolves any odd type of behavior.
Start there. If you have this issue with the latest version, submit a ticket and we'll check a few things on your site to see if anything else jumps out. Otherwise, this could be a guessing game really... as there are no other reports of this and as it is clearly just affecting one particular user, that is just about impossible for us to test and troubleshoot their local system.
We've been having this same problem since we first loaded version 2.7. Did not experience before the 2.7 version. It effects about 10% of our registrants and does not occur everytime they attempt to register. Usually if they return a few hours later, they are able to register.
mpaush, this type of problem is NOT a general, global bug. We hear of an issue like this very rarely, and it's always been due to something specific in the site. For something like this, you should submit a support ticket with access to your site, how to replicate the issue, and we'll check it out.