Registration page failure

Hi, I have created pages via security assists wizard, and most of the pages that have resulted are fine, and I have even added my template to them once created to bring them into style and most of it still works fine apart from the registration page.

My template has a log in area on all pages that then hides once a user is signed in, and there is some sort of conflict going on after I apply my template to the registration page because the page fails to load anything to the database and it bungs me off to my password reminder page

I have attached the page in a zip file for you can see.

I can't see the wood for the trees now, but I think it's either something to do with the ordering of the PHP code above the header, or my forms are clashing

Any advice will be welcomed

Just to add to what I have been doing to try and get the registration page to work, I have changed the security assist authenticate user from any button pressed to 'log in' button pressed as this relates to the log in panel on every page.

I am now getting this error:


Warning: Cannot modify header information - headers already sent by (output started at /Users/uname/Sites/sitename/tbl_users_Registration1.php:26) in /Users/uname/Sites/sitename/tbl_users_Registration1.php on line 118

Line 118 is:


header(sprintf("Location: %s", $insertGoTo));

Just thought this might help in a diagnosis

Is it possible that I am unable to have two forms on the same page where there is the registration form?

Thanks.

the error is being caused by the blank line at line 23:

22- ?>
23-
24- <?php

delete the blank space between the two php tags.


whwen you have more than one form on a page, you need to make sure that that the triggers used for the behaviors are set to use the specific submit buttons for each form.

WOW! That worked!

Why is that then? I have often used blank lines between php tags to visually give me guidance of the end of one function and the start of another!

If you look down the page, there are more blank lines, and yet they don't seem to be causing an issue. Why is that? These blank lines have been created by WA extensions, I haven't touched any of the code further down the page.

I would've never got that, so thanks for spotting that Jason.

see this page for details:
148/