Jun 3rd, 2011, 1:27 AM
Hey gpdesigner,
Hmm! At a quick glance, your code looks okay. So when you say your thank you page is blank, do you mean totally while (no HTML at all), or just that the results aren't being output into the page?
If the latter, you could try adding this to the PHP at the top of the page (after the ft_api_init_form_page() function call):
That will output everything that it found in sessions at that point.
However, I looked at your form page and things look a little wonky. The form doesn't submit on Firefox. Since I don't see any offending JS, my hunch is that the markup is a little wrong.
One thing I noticed (and this may well be unrelated), but I don't think comments of this form are valid: <!----- ------> They should only be <!-- --> (only two dashes either side). When I view source in Firefox, it shows a great deal of your page to be commented out. Also, I ran into a problem one time with XHTML strict when my javascript had lines of ----- in it. That also threw errors in Safari or something... Generally best to stick to the standard comment tags to ensure all weird & wonderful browsers won't break.
Let me know how it goes.
- Ben
Hmm! At a quick glance, your code looks okay. So when you say your thank you page is blank, do you mean totally while (no HTML at all), or just that the results aren't being output into the page?
If the latter, you could try adding this to the PHP at the top of the page (after the ft_api_init_form_page() function call):
Code:
print_r($fields);
That will output everything that it found in sessions at that point.
However, I looked at your form page and things look a little wonky. The form doesn't submit on Firefox. Since I don't see any offending JS, my hunch is that the markup is a little wrong.
One thing I noticed (and this may well be unrelated), but I don't think comments of this form are valid: <!----- ------> They should only be <!-- --> (only two dashes either side). When I view source in Firefox, it shows a great deal of your page to be commented out. Also, I ran into a problem one time with XHTML strict when my javascript had lines of ----- in it. That also threw errors in Safari or something... Generally best to stick to the standard comment tags to ensure all weird & wonderful browsers won't break.
Let me know how it goes.
- Ben