The version 2.6 will not work! Dont install!

https://www.ads-software.com/download/release-archive/

I’d suggest making your .htaccess writable by the server (777), then re-set your permalink settings.

I upgraded all 17 sites I manage that use WordPress, to 2.6 this morning, without issue on any one of them.

The new features are awesome. I love the “nagging – update your plugins!” number. Pretty cool stuff.

OTTO, this is NOT a windows specific issue. I’m running linux, it’s happening across all my wordpress sites with custom permalinks: /index.php/%postname%.html

It works fine if I go to default…but once I move to the above structure it doesn’t.

I’ve tried deleting .htaccess, I’ve tried setting to default then going back to custom…nothing seems to work. Hope this helps.

-Greg

My .htaccess is writable and I can’t login. When I rename it to a.htaccess I can login in my blog. I read some about Windows servers, but my ISP using Linuxservers.

When I change permalinks to default it works like it should, but I can’t try that when my .htacess is not disabled, because I can′t login. If I try I will get the “Internal Server Error”.

So: My 5800 blog posts in not reachable because the address is: https://Jinge.se/index.php/mynewpost.htm (example). That is Googles index of it, and I have some thousand hits via Google every day. No other link will work either, they will receive the 404-page.

Off course my .htaccess is 777.

My custom permalink is /index.php/%category%/%postname%.htm but now I have disabled it.

@gregrickaby: Why are you using /index.php/whatever permalinks if you’re running on linux/apache?

The whole index.php thing in the permalink thing is specifically for IIS servers, which don’t support mod_rewrite.

In other words, I’m amazed that /index.php/%postname%.html ever actually worked for you in the first place on a Linux/Apache setup. It shouldn’t.

@otto

I’m running a shared server @ Hostgator.com:

Linux: 2.6.24.7-grsec
Apache: 1.3.41 (Unix)
PHP: 5.2.6
MySQL: 5.0.51a-community

I’ve used /index.php/%postname%.html for well over a year now and I’ve never had a permalink issue.

I’ve also tried setting .htaccess permissions to 777 and setting to default permalink, then going to custom. Still no luck.

The reason why: I’ve tried several different variations of the permalink structure to create SEO friendly URLS… that was the way I could get it to work is by putting /index.php in front.

Website: gregrickaby.com

What is in your .htaccess file?

Also, have you tried using the non-default permalinks *without* the “index.php” in them?

It simply doesn’t make any sense to have index.php in your permalinks on a linux/apache setup. Why do you have that? There’s no reason for it.

Could you explain Otto why the /index.php/postname would not be working now after this minor upgrade? I’ve been using this permalink structure for close to four years on my windows server with wordpress and this is actually the first time I’ve experienced this issue.

Could you explain Otto why the /index.php/postname would not be working now after this minor upgrade?

If I knew that, then I’d tell you how to fix it. ??

I’m just reporting what I’m seeing people complaining about.

@ otto

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Thanks Otto. Please keep us Window Users posted! I’ll lay in wait!!

UPDATE!

By removing the /index.php from the custom structure…permalinks now work. That is fine, except the hundreds of indexed pages on Google/Yahoo/MSN ??

@jinge: the problem lies in the apache config / .htaccess if removing the .htaccess file solves the problem. Apache gives this error of you’re trying to make it do something it doesn’t want to do (apache config) or doesn’t understand (error in your file).

Putting back an old version of wordpress won’t help either: once you ran update.php the changes to the database are there to stay. Unless you restore a backup. I don’t think running WP 2.5.1 files in combination with a WP 2.6 database will improve things.

Try creating an empty .htaccess with the right permissions. Update your permalink structure and check if the file is updated correctly.
(remove old .htaccess, type touch .htaccess and then chmod 777 .htaccess).

I remember now I’ve had this error too: a lethal combination of customized WordPress permalinks and no .htaccess file to match.

@gregrickaby: Those links to hundreds of indexed pages should work fine I’d guess. That’s why they’re called “permalinks”.

I don’t get it… was the new release not tested before releasing it to the public?

Where can I find a list of the changes to see if it is worth upgrading or waiting a month or two till the kinks and plugins are fixed?