Shygirl wrote:I already got the user id from a cookie though!
Yes, and if you are confident that that part of the code is correct because you already tested it then perhaps you can just go ahead. However, I find it easier to test when I can more directly control the input values by setting them in the script itself.
Shygirl wrote:btw have you seen my code... for the most part.. the code is already doing what im telling it to....
However, there is one obvious big problem: your code does not properly escape incoming variables for use in SQL statements. You should be using [man]mysql_real_escape_string/man on $last.
Two less severe problems would be the failure to check that incoming variables exist with say, [man]isset[/man], before using them and executing so many SQL statements when one will do (you can update multiple fields with one SQL statement).
Shygirl wrote:i just got to get it to stop white screening........... thats where you experts come in
The problem is that it is impossible to tell what this "white screening" actually means. It is often symptomatic of a case where the display_errors configuration setting in php.ini is set to off, and there is an error of some kind. However, if you are not actually printing anything in arming.php, then perhaps it is perfectly fine 🙂
A quick way to check is to replace:
header("Location: arming.php");
with:
echo 'Hello world!';
Now, when you run that script and get 'Hello world!', it is clear that the problem lies with "arming.php". If you still get a "white screen of death", it means that you have to change your PHP configuration settings to set display_errors to on (and check that error_reporting is at E_ALL while you are at it so you don't have to place calls to error_reporting() all over the place). Then, when you restart your server and run the script again, post the error messages that you get.
EDIT:
djjjozsi actually repeated what Weedpacket stated, and although it is clear to me that they are right, I would not apply the fix just yet. The point is, you have to learn how to view error messages and interpret them. In the long run, you simply cannot rely on others to debug your "white screens of death" for you.