ciryaquen

Thank you moshu.

FYI, in case anyone reads this who has the same problem, I seemed to have fixed the problem by editing the 1st user who comes alphabetically after “admin”. I changed the nickname and saved it. Afterwards the “admin” became an option in the Post Author dropdown.

No clue why. It just worked.

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!

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.

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.

It apparently got stuck somewhere because it’s posted.

As for what it discussed, it was about problems getting a site installed on one of those free Godaddy sites. There was only one link back to a different thread in www.ads-software.com support boards with a similar problem.

Thanks for the info.

Thankyou HandySolo! Once again you’re fast with an answer.

I will download that plugin.

hi HandySolo,

There’s 3 other test installations in subdomains installed on the same webspace all with permalinks activated. All of those worked. That pointed to something other than the mod_rewrite and AllowOverride IMHO but I called the host, Godaddy, anyway.

The problem may be solved. The MYSQL and PHP specs were supposed to be as listed in the top post but weren’t! It appears Godaddy webhosting has a default configuration with lower versions than what their tech people think is the current version (above). It’s still not clear what version of MYSQL was installed but it was either 4.0.24 or 3.something.

If anyone else needs to update their database with Godaddy it requires going into the hosting control panel and updating to Hosting Configuration: 2.0!

So far permalinks are working now. This test installation was to try to isolate repeated failed attempts to install 2.1 on webspace with ad support. Now I’ll see if the modified version will work on the other webspace. If it does I’ll come back and toggle this to resolved.

It’s operational again after I renamed the htaccess and set permalinks back to default.

This is interesting because the previous 2.1 installations never recovered after the 500 errors started.

Update. Now the home page which previously worked is returning 500 Internal Server Error.

Wow. Fast. You replied before my RSS reader finished processing the feed for this thread.

Sure do have a link. This test is on a live server still.

I don’t get what’s going wrong.

Thanks for reading this thread.

Something is definitely wrong here.

I’ve now done clean installations of WP 2.1 four times!!!
* deleted and setup a new MYSQL database each time.
* uploaded a freshly unzipped copy of WP 2.1 each time
* deleted all .htaccess files and loaded a blank text file as .htaccess

Using the default installation doing any one of the following things causes a blank page with a square and a ? to be displayed below the Godaddy ads.
* turning on permalinks
* changing the timezone
* turning off “Attempt to notify any Weblogs linked to from the article (slows down posting.)”
* turning on “WordPress should correct invalidly nested XHTML automatically”

In other words trying to select anything other than the default options kills the blog. No plugins were even activated.

I confirmed with Godaddy that the site has MYSQL 4.0.27 and PHP 4.3.11.

Help please! Or give up on WP 2.1 and go back to WP 2.0.7?

Godaddy is one of the hosts that you do need to put in the specific server for. Localhost won’t work. Look in your admin panel for the database for something like mysql123.secureserver.net.

I’ve been playing with 2.0.6 to set up a new site for someone and went ahead and set up a 2.1 site.

Something messed up the 2.1 site, but I’m determined to get a 2.1 site up for him. Why? Because he’s not going to tinker with the site too much once it’s up and he won’t know the difference between 2.0 and 2.1.

What are your goals for your blog? If you have made many customizations for your site or rely on a log of plugins that aren’t tested yet can you go with less customization or plugins on 2.1 for a while?

For me, the biggest problem in setting up the demo site locally and moving to the 2.1 live site was figuring out all the tag changes which no one mentioned in the “hey 2.1 is out go update now” rush. Now that I’ve spent oh about 5 hours fixing the sidebar, I know the 2.1 site will be “future proof”.

In particular 2.1’s new way for handling links in the blogroll is a major issue: you may want to consider the hassle of eventually having to change your mysql data over.

OTOH, the 2.1 site I did set up just self-destructed when 2 plugins were activated and changed the htaccess file. So the moral seems to be “pick your poison”. Good luck what ever you decide to do.

I’ve been playing with 2.0.6 to set up a new site for someone and went ahead and set up a 2.1 site.

Something messed up the 2.1 site, but I’m determined to get a 2.1 site up for him. Why? Because he’s not going to tinker with the site too much once it’s up and he won’t know the difference between 2.0 and 2.1.

What are your goals for your blog? If you have made many customizations for your site or rely on a log of plugins that aren’t tested yet can you go with less customization or plugins on 2.1 for a while?

For me, the biggest problem in setting up the demo site locally and moving to the 2.1 live site was figuring out all the tag changes which no one mentioned in the “hey 2.1 is out go update now” rush. Now that I’ve spent oh about 5 hours fixing the sidebar, I know the 2.1 site will be “future proof”.

In particular 2.1’s new way for handling links in the blogroll is a major issue: you may want to consider the hassle of eventually having to change your mysql data over.

OTOH, the 2.1 site I did set up just self-destructed when 2 plugins were activated and changed the htaccess file. So the moral seems to be “pick your poison”. Good luck what ever you decide to do.

I’ve stumbled on the answer via Lorelle’s blog.

There’s all kinds of tag changes from 2.0.6 to 2.1

For one thing the blogroll/links have been totally changed.

The WP 2.0.6 tags <?php get_links_list(); ?> used to default to showing the description.

show_description?
(boolean) Should the description be displayed (TRUE) or not (FALSE). Valid when show_images is FALSE, or an image is not defined. Defaults to TRUE.

The new WP 2.1 tags <?php wp_list_bookmarks(); ?> don’t show the descriptions by default.

show_description?
(boolean) Should the description be displayed (TRUE) or not (FALSE). Valid when show_images is FALSE, or an image is not defined. Defaults to FALSE.

Go figure!