• Hello,

    Here’s the continuing saga of trying to install WordPress 2.1 on a Godaddy ad supported website. After 1 hour on the phone with tech support, and installing WordPress into a directory, to avoid the main site being down, the level 1 tech opened a trouble ticket on the 404 and 500 server errors. Escalated support wrote back that WordPress worked for them. Sure enough, the basic installation suddenly did work. All kinds of plugins could be activated and <a href=”http://tinyurl.com/3xfztf
    “>it still didn’t break.

    I just tried installing it in root and get this error at domainname/wp-admin/install.php . (Note: the filepath is obscured as a/b/c and domainname because it’s not my site and I don’t want to accidentally introduce any security or privacy issues.)

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/a/b/c/domainname/html/wp-config.php:1) in /home/content/a/b/c/domainname/html/wp-admin/install.php on line 15

    The installation was on a new MYSQL database with the WordPress files from the same zipped copy of WordPress 2.1 that’s installed and working in the subdoman. This other thread makes it sound like there’s a white space issue, but none of the files outside of the modified Kubric theme has been modified.

    Any ideas what’s going on? I’m an amateur, so, please be specific or step by step. Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • I’d make a copy of the Kubric theme files you modified. Then, delete all the wordpress files and reupload the complete 2.1 distribtution. Then fix your wp-config.php, do the install, and see if everything works okay. Then upload your theme modifications.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    GoDaddy’s ad supported pages will not work correctly with WordPress all the time, because of the way GoDaddy inserts those ads. There is no workaround. Pay them for hosting to turn off the ads.

    Thread Starter ciryaquen

    (@ciryaquen)

    Thanks for the replies.

    MichaelH, I did that 4 times. Otto42, it’s not my site, just trying to help someone update his site. I’ll try another install, since we got it working on a directory. Also will see if he wants to upgrade to the paid hosting.

    Next thing I’ll look into is 1. pointing and masking the domain to the directory. or 2. “moving” the working WordPress from the directory to root.

    Thread Starter ciryaquen

    (@ciryaquen)

    I tried installing at root one more time and despite the weird error, this time it did install. But! There’s 2 problems.

    1. There’s a diamond with a question mark directly over the center of the default header. (i.e. immediately after inastallation). See this screenshot
    2. Each time I click “login”, it goes to the login dialog box, and after clicking the there’s a bunch of weird errors instead of the dashboard.

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/a/b/c/domainname/html/wp-config.php:1) in /home/content/a/b/c/domainname/html/wp-login.php on line 12

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/a/b/c/domainname/html/wp-config.php:1) in /home/content/a/b/c/domainname/html/wp-includes/pluggable.php on line 313

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/a/b/c/domainname/html/wp-config.php:1) in /home/content/a/b/c/domainname/html/wp-includes/pluggable.php on line 314

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/a/b/c/domainname/html/wp-config.php:1) in /home/content/a/b/c/domainname/html/wp-includes/pluggable.php on line 275

    Anyone have any idea what this new wrinkle can mean or how to solve it? This is a basic 2.1 installation on a new MYSQL database with no modifications yet. Sorry, the WordPress site at root can’t be left up, so the old html will be restored within 30 mins.

    If it didn’t install I was going to try the codex’s instructions for moving the successful installation from its directory to root according to the codex, but will wait to see if this root install can be made to work.

    All advice will be appreciated.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    All those “headers already sent” messages are the direct result of GoDaddy’s ads.

    I do know what I’m talking about on this one. Really. You will not solve this problem short of removing the ads.

    Otto42 is 100% correct – the site will always have intermittent problems with the ad insertion.

    Also, it looks as if all plugins weren’t deactivated prior to install.

    Thread Starter ciryaquen

    (@ciryaquen)

    Thanks for the replies.

    Samboll, at root, the basic installation put up those errors after logging in. You know the step 1 click next step 2 “that’s all there is so login”. Then those errors. It was installed on a brand new database and the dashboard had never been accessed.

    Otto42, the funny thing is GD tells the site owner if he installs WordPress 2.0.5 through their “Metropolis” they will support his installation. But I doubt it.

    I’m also convinced at this point the ads are messing up his site.

    Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Installation not working on ad supported Godaddy site’ is closed to new replies.