vwoning2

OK, I’ll fess up.

I carefully removed my .htaccess files from the server, and examined my local .htaccess files. I had NOT uploaded the correct .htaccess file into the /wordpress/ folder on the borked site…

Yeah, I know.

Did you upload a config file?

If you backed up your database first, then simply delete all of the WP 2.5 files on your server and re-upload WP 2.3.3 as a fresh install. Remember to upload your old WP config file.

Once you have a fresh install, restore the database on the server from your backup.

When you login to WP again, all should be well.

OK, it’s NOT a WP bug, at least not that I can tell from my upgrade test.

I have a single VPS account and I have two identically configured websites on it. WP2.5 is on both. Both blogs are in subfolders. On the one that works, it is in a subfolder called /notes/. On the one that’s broken, it is in a /wordpress/ subfolder. The .htaccess files are correctly configured for each.

I’m stumped. There’s no reason why one should be different than the other. There are no plugins other than Akismet 1.4 active on either, these are fresh installs.

To be fair, there may be some hidden problem with the account that is borked. I previously tried installing WP 2.3.3 on that account and got array appearing all over the site. I’ve never been able to get WP working on that account in 5 minutes.

I’ve got better things to do with a Sunday afternoon. And yes, for each install I’ve nuked the database AND the db-user and started from a clean slate. Far from ideal, but so is a URL hack.

Anyone else have this experience and find a fix that doesn’t involve a URL hack?

I’ve encountered the same problem. When installing WP 2.5 all posts/pages except the index return a server default error 404. Only when adding /index.php into the Custom Structure do I see my pages.

/index.php/%year%/%monthnum%/%day%/%postname%/

I am not hosted on IIS, I am hosted on Apache. I have WordPress installed in a /wordpress/ folder. I have a mod rewrite .htaccess in my root folder to force a www extension and to protect indexless directories and I have pasted the WP .htaccess file into the /wordpress/ folder to enable my settings.

While troubleshooting this I removed my root level .htaccess and (after dumping cache) tried to view pages without success. So I am reasonably confident I haven’t got a .htaccess conflict.

I have 2.5 RC1 installed and working successfully on another site on the same server. That account has an even more heavily configured .htaccess file in root and there are no problems. I am going to upgrade it to 2.5 and see if it breaks. I’ll let you know.