Permalinks in 2.6.1 still not working

I’m having a issue with the Perma links too, running on a windows server. 2.5 worked fine. Upgraded to 2.6 did the workaround of the entering tags, and that worked.

I installed 2.6.1 on a new domain before upgrading my other ones and the workaround for the tags does not work..

Anyone have a solution?

This is very frustrating I know. I had 2 wordpress installations on the same IIS server. I upgraded both of them to 2.6. 1 worked perfectly, the other randomly gave 404.

The good news is 2.6.1 fixed my problem blog, but before the fix what worked for me was adding an extra category in the string. For example instead of index.php/%postname%/ I had to put something like frustrating/index.php/%postname%/ – and for some reason that worked, I don’t like the extra “directory” it puts in there, but atleast it got rid of the 404s.

None of the above mentioned fixes or alternate Permalink format works for me either unfortunately. Im wondering if I should just go back go 2.5 and be happy, why did I fix something that wasn’t broke? ??

I want to go back to at least 2.6 with the category base and tag base at least worked…

So far after setting permalinks…they seem to work as long as the site loads in as https://www.domain.com/index.php, but the landing page is just https://www.domain.com which generates the 404 message.

Knowing that some programmer can come up witha afix I’m sure… WordPress is not redirecting the site to https://www.domain.com/index.php when just the https://www.domain.com is loaded…

Someone please fix this issue…. Now I know whay I didn’t upgrade from 2.1 for a long time…this is messed up…..for us on IIS servers…

Too bad this issue was fixed with 2.6.1. The link with p_id= has really caused me a lot of problems.

this permalink issue is killing me! even with 2.6.1

Okay, this may not work for everyone but it worked for me. I updated to version 2.6.1. The permalinks were still broken like before. Everything was still 404ing- posts and pages alike.

I was manually changing my .htaccess file in the wp-admin folder after upgrading because it was not writable whenever I tried to update my permalink structure from the WordPress dashboard.

I changed my whole blog directory (the folder)to a 777 permission within my web host account utility (WebShell). I then changed the permalink structure as before, and WordPress was able to write to the .htaccess file at that point.

I then changed my blog directory back to a 755 permission (don’t leave your permissions at 777! you’ll be hacker bait if you do).

All my permalink nightmares dissolved in the dawn of my last desperate effort to understand the relationship between permalinks, permissions and the .htaccess file.

I hope that helps for at least one other person.

@ jojoma

Too bad this issue was fixed with 2.6.1. The link with p_id= has really caused me a lot of problems.

You must have lucked out with something then…I can’t even get the 2.6 workarounds to function with fresh installs on 2.6.1

@ wiselywoven

I changed my whole blog directory (the folder)to a 777 permission within my web host account utility (WebShell). I then changed the permalink structure as before, and WordPress was able to write to the .htaccess file at that point.

I then changed my blog directory back to a 755 permission (don’t leave your permissions at 777! you’ll be hacker bait if you do).

Unfortunately, my host doesn’t allow the .htaccess file. I tried to change my IIS permissions on the root (temporarily) and adjust my permalinks and didn’t have any luck…It was worth the shot though…

Any other suggestions out there?

Still having a problem with Permalinks on IIS. Is this topic being ignored or acknowledged by anyone? This is with a fresh install of 2.6.1

I installed 2.6.0 to replace my 2.1 installation, and had quite a problem with my categories… that I managed to correct with the help of this forum. I also had the problem of the permalink (I am on a Linux server) so I had to let the default manner until a solution is found. I did not want to risk another night of labor (upgrading to 2.6.1) without being confident that the permalink will be corrected.

So I was glad to try the solution of wiselywoven and to see that it works. After making temporarily my blog directory ‘777’, I was able to change the permalink from the default to “almost” what it was : index.php/year/month/day/postname.

The index.php was not there before : it is not just a question of having a “cute” or more lisible URL, the worst problem is that all the links that are… linking to pages of my blog, all the content of the caches of Google, will all give an error.

If I have correctly understood, the index.php on the permalink is still there, under 2.6.1, is it ? If so, I will have to wait… But this problem is a serious break in the web of links between blogs, search engines…

@ gillesenvrac

If I have correctly understood, the index.php on the permalink is still there, under 2.6.1, is it ? If so, I will have to wait… But this problem is a serious break in the web of links between blogs, search engines…

I think the “index.php” prefix is just for IIS servers if I am not mistaken.

I found this on another post about the permalink issue from 2.6:

If you’re using Linux/Apache on your webserver, you don’t really need the index.php anyway. Try removing it. The index.php thing was only meant for IIS servers, which don’t support mod_rewrite.

I am a little baffled as to what WAS fixed with this issue for IIS users that the release notes mentioned. So far the only change I see is that the 2.6 workaround doesn’t work AND the problem still exits.

I have 5 clients that want WP blogs integrated into their websites on IIS servers. All of them want SEO. This default permalink structure of p=whatever is going to tank that.

I sincerely hope that some solution or workaround can be found.

Any new thoughts out there on this issue?

Hey Guys We’re still needing some kind of solution here… Is there absolutely no work around yet for IIS users? This is getting frustrating and I’m waiting patiently for a fix ??

Hey WordPress Team,
I love your Blogsystem but same problem here. Permalinks don’t work.
I use a linux server.