|
Posted by mcserret on 09/04/07 20:53
On Sep 4, 3:44 pm, mcser...@yahoo.com wrote:
> I know this is a recurring problem that has been addressed here
> before, but even after reading all that has gone before, I am still
> stumped.
OK- here's a followup, and it STILL does not make any sense!
This part of the site is to be secured by a login, so both files would
eventually be headed by "session_start()".
Just for the hell of it, I stuck session_start() at the head of
processStuff.php (the file that was gving me all the errors) along
with code that redirects (via header()... exit() ) to the login page
or back to the originating page if it was a valid SESSION.
And waddya know! At first run, I was not logged in, so it sent me
(via the cursed header() instruction!) to my login page!!!
So I dutifully logged in and went to the cursed page and..... damn
thing works!!!!
Now- why, when I was debugging and did not _want_ any of the SESSION
stuff in the code, did it stubbornly return all those $#$&*#!
Warnings? Other than the "session_start()", it was the Same Damn
Code!
I need another cup of coffee!
Just to answer one question, this originally was done in Dreamweaver,
but I switched to Notepad after an hour of frustration.
MC
Navigation:
[Reply to this message]
|