Permalinks in 2.6.1 still not working

Okay I think my problem is that mod_rewrite isn’t activated…

Same problem here, Linux with Apache. Tried activating mod_rewrite as well, didnt help a bit, same as the other fixes…

Do you have the LiveSig plugin?
I have and updated it to the last version 0.4
That couses the problem with the not showing posts!and/or not showing the permalinks.

I have reinstalled (LiveSig) the previous version and all works fine.

Now I am running wordpress the latest version 6.1 and every plugin I have is updated to the latest version accept the Livesig.

Hope that this helps for you too.

I am still not sure of the situation under 2.6.1

Under 2.6.0, it is impossible to get rid of the index.php prefix on the permalink, even with an Apache Linux server (I tried it in every way possible), making it different from all the posts before the upgrading.

If this is the same with 2.6.1, I won’t upgrade yet. But I would very like to know if this is considered a problem by the code writers (poets ?) ?
In between, waiting for a fix on this permalink thing, I think it is preferable to keep on the default (the numerical posts) because when I eventually come back to the URL I had before (year/month/day/name-of-post), the numerical links would automatically (on the fly) be transformed into the new ones but not if I use temporarily the index.php/year/month… form of permalink.

Am I clear, and right ? If so, I think it could be nice to give this advice to those, like me, that have years of posts on their blog.

Anyway, thanks for your work, guys (and gals), WordPress is still a very good “poem”.

i have the same problem https://wordpress4dummies.info

Under 2.6.0, it is impossible to get rid of the index.php prefix on the permalink, even with an Apache Linux server (I tried it in every way possible), making it different from all the posts before the upgrading.

Now, you surely must know that’s incorrect, right? For instance, look at 99% of the WordPress blogs out there.

If you can’t get your Permalinks to work, be sure to check the troubleshooting tips on the Permalinks page.

If you’re attempting to manage your own Apache server, be aware that there’s more to it than just turning on mod_rewrite. In particular, check your AllowOverride value in your conf file.

look at 99% of the WordPress blogs out there.

99% of the wordpress blogs are under 2.6.1 ?

How is it that my wordpress permalinks were OK (i.e. without index.php) before upgrading (I was, and should have stayed, under 2.1), and now I am stuck with this prefix ? I didn’t change any configuration, and I am not running my own Apache server.

By the way, you did not answer my question : waiting the fix for this (temporary) problem, am I better to stick with the numeric default URL ?

Same problem:
* IIS
* Clean and new WP 2.6.1 installation
* 404 on all pages with permalink /index.php/%category%/%postname%/
* tried all solutions above to no avail

Time sensitive so I’m hoping for a solution soon…

I am glad to announce that my blog has recovered the permalinks it has had for years : /year/month/day/post-name without the (infame) index.php !

How did I do that ? Even if I still wasn’t sure (reading the posts on the forum) I finally decided to upgrade from 2.6.0 to 2.6.1, and had to manually re-write the content of my .htaccess file. And it worked !

I wish you all the same !

I *was* going to upgrade one of my sites to 2.6.1 (tested it locally today and had the permalinks issue – thought it was just me being stupid actually, since 2.6.1 was said to have fixed some issue) but now I think I’ll go straight to 2.5.1 instead.

I use the default (ugly) permalinks and they simply won’t work. They were working fine when I first switched over to the 2.6 version, then a couple of weeks after the upgrade they stopped working. I upgraded to the 2.6.1 version in hopes that it will correct my problem and it didn’t.

Just for those who are considering updating – my upgrade went just fine.

I use a custom permalink structure:

/%year%/%monthnum%/%postname%.html

because I originally migrated over from Blogger to a WP 1.X release.

To offer a different perspective than a lot of folks on this thread, I have never had a problem with upgrading WP versions and loosing my permalinks. I use VPS servers from Dreamhost, who provide excellent one-click installs and upgrades for WordPress. Their shared servers are slow, but they get all of the WordPress settings right, and it has worked flawlessly for many, many versions. Their VPS servers are as fast as you want to pay for.

I hope you realize that I don’t say this to denigrate anyone having a problem, or even to trivialize the problem that they are having. Rather, I hope to provide some counter-balance to the notion that permalinks don’t work in 2.6.1. The DO work in 2.6.1, if everything is properly configured.

So, the good news is that fixing this issue is likely in your own hands, and you don’t have to wait for the WP folks to release a new version. That’s the bad news though as well – fixing it is likely in fixing your own settings. ??

Best of luck,
A

PS – if its helpful to anyone, this is the .htaccess file I use:

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

# END WordPress

@miloandrew: I don’t usually have any problems either (but then again, I’m a newcomer to WordPress compared to yourself, since I only started with 2.0 series) except 2.6 has baffled me a bit more than others ??

Is it true there is a type of fix you can do if your on IIS by switching one of the DLL files around? The ASAPI file?

@royfossblog
Are you referring to this ISAPI filter?
The con is finding a host that will install this on their servers for you.