PhP header error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Jim
    Member
    • Mar 2004
    • 44

    #1

    PhP header error

    Can anyone give a clue as to what would possibly cause and error like this,

    "Warning: Cannot modify header information - headers already sent"

    Followed by a line number in the script. The puzzling thing is, as far as I know, the script has not been modified, it just statred occuring for some reason.

    Any suggestions are greatly apprecited
    -J
  • Buddha
    Senior Member
    • Mar 2004
    • 825

    #2
    Is this an included script? Did you update or change a related script? Cound just be some stray whitespace outside the PHP open/close tags.
    "Whatcha mean I shouldn't be rude to my clients?! If you want polite then there will be a substantial fee increase." - Buddha

    Comment

    • Jim
      Member
      • Mar 2004
      • 44

      #3
      Thanks for the reply.

      I thought it was probably a whitespace problem as well, but I'm certain the script itself has not been touched in months.

      There is a possibility that php.ini has been changed, but as I was unable to see the original, I don't know what changes may have been made.

      Is there anything else besides whitespace or script changes that could cause this error?

      Comment

      • Buddha
        Senior Member
        • Mar 2004
        • 825

        #4
        You say php.ini might have changed? If "output_buffering" was on and then turned off that might reveal the problem.
        "Whatcha mean I shouldn't be rude to my clients?! If you want polite then there will be a substantial fee increase." - Buddha

        Comment

        • Jim
          Member
          • Mar 2004
          • 44

          #5
          Many Thanks Buddah,

          There is no value for output buffering, so I can't tell if it was on originally, but I will check it out.

          Hope I'm not pestering you, but is there anything else I should look for?

          Thanks again

          Jim

          Comment

          • Buddha
            Senior Member
            • Mar 2004
            • 825

            #6
            Only long shots like an appended script or something. Check you servers php.ini with phpinfo(). (Sincerely doubt Andrew is screwing with the php.ini file though. You wouldn't be the only one here with a problem.) One corruptted byte is all it would take...
            "Whatcha mean I shouldn't be rude to my clients?! If you want polite then there will be a substantial fee increase." - Buddha

            Comment

            • Jim
              Member
              • Mar 2004
              • 44

              #7
              You're right, I'm sure its a local copy problem, not the master. It probably is something in the script that I'm not seeing.

              Many thanks for taking the time.

              Best Regards
              Jim

              Comment

              • Ian
                Member
                • Mar 2004
                • 64

                #8
                What about using ?

                ob_start();
                ob_end_flush();
                www.ianhoar.com - A place to geek out

                Comment

                • sdjl
                  Senior Member
                  • Mar 2004
                  • 502

                  #9
                  How about posting some code?
                  We could have a look and see if anything obvious is appearing

                  David
                  -----
                  Do you fear the obsolescence of the metanarrative apparatus of legitimation?

                  Comment

                  • keylope
                    Junior Member
                    • Jun 2004
                    • 23

                    #10
                    don't know if this problem was solved already, but I have occasionally run into that problem... That usually happens when I try to delete, create, or edit cookies on a .php file after the page has already started to render.

                    The php file will start the rendering when <html> starts. Anything before that, should work out okay.

                    Well I hope that made some sense.

                    Comment

                    Working...