May 18th, 2010, 7:13 AM
Good thinking on disabling the emails - that's the usual culprit. (I MUST finish that email template validation code for the next beta.... argh).
Since the data's getting into the database, we now that the ft_api_process_form is doing it's job at least THAT far.
Couple of things to check first:
1. Double check that that block of PHP you quoted above appears before anything that's actually outputted into the page. In other words the opening <?php should be the very first 5 characters in the page - not even a space before it.
2. Try loading your registrationconfirmation.php page in your browser. Is it in the same folder as the previous page? Does it load up properly?
Failing that... what happens, exactly? The page just reloads? You should also double check that the form submit button on that page has name="Register" (the case is important).
Let me know how it goes! I'm sure it's just some little thing like the above.
- Ben
Since the data's getting into the database, we now that the ft_api_process_form is doing it's job at least THAT far.
Couple of things to check first:
1. Double check that that block of PHP you quoted above appears before anything that's actually outputted into the page. In other words the opening <?php should be the very first 5 characters in the page - not even a space before it.
2. Try loading your registrationconfirmation.php page in your browser. Is it in the same folder as the previous page? Does it load up properly?
Failing that... what happens, exactly? The page just reloads? You should also double check that the form submit button on that page has name="Register" (the case is important).
Let me know how it goes! I'm sure it's just some little thing like the above.
- Ben