login error

[vokez]

what would be the problem with this code immediately after i log in i get the following error message.
warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at C:\xampp\htdocs\mine\HRFunctions.php:1) in C:\xampp\htdocs\mine\HRFunctions.php on line 33

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at C:\xampp\htdocs\mine\HRFunctions.php:1) in C:\xampp\htdocs\mine\HRFunctions.php on line 33

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\mine\HRFunctions.php:1) in C:\xampp\htdocs\mine\HRFunctions.php on line 36

Warning: Unknown: Your script possibly relies on a session side-effect which existed until PHP 4.2.3. Please be advised that the session extension does not consider global variables as a source of data, unless register_globals is enabled. You can disable this functionality and this warning by setting session.bug_compat_42 or session.bug_compat_warn to off, respectively. in Unknown on line 0

 

[vacunita]

Without seeing any code its hard to say.

The first 3 errors are due to having any output before calling anything related to sessions. There cannot be any output before starting sessions otherwise they can't be set.


The last one is probably some side effect of the first 3.

However without looking at the code there's not much more that can be said.







----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

Web & Tech

 

[jpadie]

i'd guess that the fourth error hints at why there was early output, and the first three are errors caused by what vacunita said.

there will have been output before those error messages. probably an error notice saying that $something does not exist or the like.

I suspect that you are using code that you did not write and that it is not a properly maintained package or you are not using the most up to date version. Whenever you are using someone else's code, that you cannot debug yourself, the best first port of call is to talk with the developer. If the package was reasonably well known there are often community forums dedicated to self-help. If there is neither then it's a fair bet that the package was a dog and you should find something else.