Have no idea what i’ve done …

  • I think this may be a combination of user error and bad host. Here’s the beginning of the problem. My host doesn’t allow for direct MySQL control. The only thing you can do is create or delete a database, and you’re only allowed one db per account — I know I know, but it was a free account. So, here’s the problem … I was having all kinds of php error on any other install other than 1.0. I attempted 1.0.1, I tried a couple of night’lies, etc… SO I figured I would go back to my ole 1.0 (after many sessions of trying other versions, and having to delete and recreate multiple dbs). I also deciced it would probably be best to start from scratch, so I deleted everything off my server, except for a log folder which the host provider (once again) does not allow me access to …
    But when I reinstalled on a fresh db, and tried my admin and password (several times), all I would get was the following code:

    Warning: Cannot add header information - headers already sent in /homepages/17/d90053662/htdocs/wp-login.php on line 122
    Warning: Cannot add header information - headers already sent by (output started at /homepages/17/d90053662/htdocs/wp-login.php:122) in /homepages/17/d90053662/htdocs/wp-login.php on line 126
    Warning: Cannot add header information - headers already sent by (output started at /homepages/17/d90053662/htdocs/wp-login.php:122) in /homepages/17/d90053662/htdocs/wp-login.php on line 129
    Warning: Cannot add header information - headers already sent by (output started at /homepages/17/d90053662/htdocs/wp-login.php:122) in /homepages/17/d90053662/htdocs/wp-login.php on line 131
    Warning: Cannot add header information - headers already sent by (output started at /homepages/17/d90053662/htdocs/wp-login.php:122) in /homepages/17/d90053662/htdocs/wp-login.php on line 132
    Warning: Cannot add header information - headers already sent by (output started at /homepages/17/d90053662/htdocs/wp-login.php:122) in /homepages/17/d90053662/htdocs/wp-login.php on line 133
    Warning: Cannot add header information - headers already sent by (output started at /homepages/17/d90053662/htdocs/wp-login.php:122) in /homepages/17/d90053662/htdocs/wp-login.php on line 134
    Warning: Cannot add header information - headers already sent by (output started at /homepages/17/d90053662/htdocs/wp-login.php:122) in /homepages/17/d90053662/htdocs/wp-login.php on line 154

    My thought is perhaps there’s still a session somehow going on, and I can not stop it?!?!
    I’m really in a bind … any assistance would be of help at this stage …

Viewing 6 replies - 1 through 6 (of 6 total)

  • Things to check:
    Did you add your DB information to the wp-config.php file?
    Ensure that there are no extra spaces or returns in the wp-config.php file.
    Did you run /wp-admin/install.php before trying to login?
    These are just a few things off of the top of my head. Hope it helps.

    Thread Starter azurewolf

    (@azurewolf)

    Thanks for asking and helping NuclearMoose. Sadly, yes, I did both. I put the proper DB info in my config file and did upload it. I ran through the install, with NO errors.

    open the wp-config.php file and check to make sure there is no spaces or extra lines outside the <?php ?> tags…. That is the #1 reason for the headers errors.
    TG

    PHP is clear when sending debug codes… if you read well, it’s not the installer the problem, it’s the login file…
    open wp-login.php and check for extra spaces and lines after the last ?> …
    >> output started at /homepages/17/d90053662/htdocs/wp-login.php:122
    this error means that the source is at that level, the file is wp-login.php, and the error tag is at line 122 … (usual text edition)

    nexia… that might be where the errors happen, but it’s not necissarily the reason. By the time it runs wp-login.php, the “blank” has already been sent, which means it’s before then. That’s what is leading me to suspect the config file. 9 times out of 10 that’s been the culprit. Once that file has been checked, and the error still happens, then I would look to see what is before the <?php of wp-login.
    I agree that php is pretty good a describing where an error happend, and why, but all it can do is report the symptom., and not the disease.
    TG

    hum.. you’re right TechGnome.. i see why also… ob_start()… always cached, the process is differed… anyway, you are right… i processed the error manually and that is… in some servers… (ok, old PHP)…

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Have no idea what i’ve done …’ is closed to new replies.