Support » Fixing WordPress » wp 3.1 permalinks still broken after many trys with fixes described

  • This was posted in a resolved thread but i have opened it up as it has not been fixed for me.

    I unlike a lot of people am still having issues with the wp 3.1 permalinks.

    I heard from users that categories ( the_category() in the loop ), post linking ( the_permalink() in the loop ) from index and categories sidebar ( using wp_list_categories() ) bring up 404 pages. I am using the custom permalink structure of /%category%/%postname%/ (which i thought was the most popular way, and featured on the wp help page).

    What I have done so far:

    – Started off by doing a clean install (new db, new folder on my dev server). Downloaded wp 3.1 and installed it in the new folder via my FTP client. Did the normal setup that i do all the time (100s of times before). Things were functioning from a wordpress standpoint except for the stated issues above (category and post pages getting 404s).

    – So since it was a clean install there were no plugins that might be causing the permalink issues. But i went ahead and deleted the two default ones that come with WP 3.1 just to make sure (even though they were still disabled). Still getting 404s.

    – So then i proceeded to do the suggested .htaccess delete and respawn action. Did this as described by many sites and still had the same issue. I did this like 10 times.

    – So i was starting to think it was my theme… So i turned off my theme and reverted to the default (twenty10 theme). Keeping my permalinks set to /%category%/%postname%/. The same issue was happening with this theme. So this is what made me think that it was not my theme and more of a WordPress 3.1 issue.

    – If i set my permalinks back to default, they of course work fine, but i have thousands of people using my theme and use the custom permalink structure. So I am afraid that those people are a.) going to have broken sites if they upgrade and b.) have broken links if they revert to the default permalink structure.

    – I tried to install the hotfix plugin and that did nothing.

    – I made sure that my code was not chaining permalinks like some of the plugins that were causing the issues. Nothing there to cause my troubles…

    The only other step that i have not done was install another instance of wp 3.1 in a completely different folder on my server… I was saving this as a last effort if there wasnt a fix that someone uncovered.

    So that is where i am and what i have done. Hope that this is clear and links you to a possible solution.



Viewing 15 replies - 1 through 15 (of 34 total)
  • Moderator Ipstenu (Mika Epstein)


    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    Try INSTALLING one of these two plugins:

    FV Top Level Categories
    Permalink Fix & Disable Canonical Redirects Pack plugin


    – I installed “FV Top Level Categories” plugin, then tested to see if it did anything. NOTHING different. Then deactivated it.

    – I then installed “Permalink Fix & Disable Canonical Redirects Pack” plugin, then tested to see if it did anything. It is now just keeping me on the home page when i click on post titles, category names.

    – I then tried to have both active to see if they worked together for some reason and got the same result as the second part.

    Still a no go…

    Moderator Ipstenu (Mika Epstein)


    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    Does it work when Permalinks are turned off? Like do the ugly Ugly works?

    Yah they work fine when those are set to default. just goes to ?p=1 etc.

    here is my demo site:

    Keep in mind that none of the pages are built out besides the standard pages that wordpress needs to function.

    You can see here that if you click on the post name that wordpress created or the uncategorized category link you will get a 404 page…

    Not sure what is going on…

    Moderator Ipstenu (Mika Epstein)


    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    I am using the custom permalink structure of /%category%/%postname%/ (which i thought was the most popular way, and featured on the wp help page).

    What happens when you use the default pretty permalinks? YYYY/MM/DD/POSTNAME?

    And what kind of server are you on? *NIX or IIS?

    I tested the following:

    – I Set the permalinks to: Day and name: /%year%/%monthnum%/%day%/%postname%/
    Like you suggested. Then the post links ( the_permalink() in the loop ) goes to the post correctly. When i click on a category ( the_category() in the loop ) it goes to a 404 page.

    – I Set the permalinks to: Month and name /%year%/%monthnum%/%postname%/
    As described above it goes to the post ok, but doesnt go to the category links, just 404 for these.

    I am using 1and1 for hosting, they use Linux.

    Running OSX 10.6 Server here.. self hosting with Comcast Business and a Mac Mini Server.

    All permalinks except for “default” are borked.

    None of the fixes work. Everything worked perfect prior to the update.

    My theme is now broken on my network sub sites now too.

    This is not a production site.. (Yet) it’s in development but it still sucks to divert so much of my time to fixing things that were working perfect prior to the update.

    Little bit of an update here. I tried 3.1 on my backup testing server (hosted by inmotion – Linux)

    permalinks work on that site with the same theme/plugins!

    Now I’m really confused! for some reason wordpress 3.1 does not like my OSX Server 🙁

    Moderator Ipstenu (Mika Epstein)


    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    I spun up a test site and cannot reproduce this, which given kenrik’s problem, makes me think it’s a server side issue. I’ve so far only seen it on IIS, though.

    estern23 – Make sure you have this at the top of your .htaccess at your webroot.

    AddType x-mapp-php5 .php
    AddHandler x-mapp-php5 .php

    1&1 can be weird.

    I was thinking about it and I wonder if it is a permission related issue. I have custom permissions on some of the folders (like 644 on wp-content) and maybe it did not upgrade cleanly even though it did not throw up any errors? When i get home from work i’ll manualy install the 3.1 update with stock permissions to see if that works.

    Php 5 is the only version of php i have on my server? Why would i need to define it?


    I did as you suggested for the 1and1 fix. I remember having to do this in the past so it would know it was php5.

    DIDNT FIX IT, I still get 404s after adding this into the htaccess.

    I do appreciate your help in trying to track down the issue here…

    Any other thoughts?


    I did a test…

    I created a new wp 3.1 instance and just set it to the custom peramlink ( /%category%/%postname%/ ) that i have been using and using twenty10 theme. The theme works fine now…

    So now it must be something with my theme… double ugh.

    I am thinking that it must be something in the archive.php page since that handles the category pages and or the single.php page.

    I am going to try to extract these sections into my theme from the twenty10 theme and see if i can pin point the exact issue at hand.

    I dont know what i will find but think this is where the issues are now.

    If you have any insight to where i might look besides these two theme template pages that would be awesome.



    Moderator Ipstenu (Mika Epstein)


    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    I’m … glad? it’s a theme? No. I’m not, but I’m relieved it’s not broken for everything. I did make a trac ticket for this, since there IS a chance WP broke this, after all, and that’s why it’s DOA now.

    If you have insights, please share them! And thank you for sticking with debugging hell! I appreciate it 😀 It’s much better to work with people on these things.

    Thanks for submitting this to the TRAC… I hope they agree that it is a WP issue and don’t close it.

    I too still think that it is WP core code that is the culprit here since it was fine before and there were no changes made to the theme in recent months.

    I hope to find what is going on and report back my findings. Maybe i can track it down to a function or something…


    Looks like it was added to 3.1.1 lets hope that they can track down the issue.

    I am still struggling with what is wrong and leaning back to the wp core code vs the theme…

Viewing 15 replies - 1 through 15 (of 34 total)
  • The topic ‘wp 3.1 permalinks still broken after many trys with fixes described’ is closed to new replies.