404 Error for Category Permalinks After Upgrade to 3.1 (15 posts)

  1. memitch08
    Posted 5 years ago #

    Here's my site http://restorationgateway.org

    I'm getting 404 errors when I try to access the category pages. I've been able to access the category pages by putting "?category_name=" in for the category slug under the permalinks page.

    I don't know if it has something to do with my desire to eliminate the /blog slug - which somehow I was able to do.

    I'm running 3.1.1 - but the problem started when I upgraded to 3.1.

    I would like the slug to read /category/example_category/ or simply /example_category/

    I upgraded to 3.1.1 when I saw that they had fixed the category issue and reverted back to the /category/ slug - but it didn't help.

    Steps I have taken so far -
    1. Recreated all permalinks (to default - then to custom)
    2. Used the top-level categories plugin
    3. Disabled all plugins
    4. Deleted .htaccess file
    5. Re-created .htaccess file
    6. Set permalinks through network admin

    If I remove the "?category_name=" slug - then the links simply show as /category/example_category/ - but when you click them they return a 404 page.

    I've been to all of these and tried everything suggested there (that I am aware of) but to no avail.


    Any ideas? Thanks!

  2. Are you using any plugins to mangle permalinks? Because you cannot, by default, use JUST /category-name for your cats.

    Also, IIS or Linux?

  3. If you stripped out the /blog AND the /category, then yeah... likely you did mangle something.

  4. memitch08
    Posted 5 years ago #

    I'm not using any plugins to mangle permalinks. I tried to use them but they didn't work.

    I was using the remove /blog slug plugin before upgrade to 3.1. I don't like having /blog in there. But that plugin is not active now. In fact - I am not entirely sure where the /blog slug went. It shows on the permalinks page - as a constant that cannot be edited - but none of the links show it.

    I should also note that adding the /blog slug in manually to the /category permalinks still return a 404.

    I have multisite - with mapped domains - and I have full control of all sites - so removing the /blog slug is not a threat as I see it.

    The problem is that /category/example-category/ returns a 404. I tried using the plugin that removed the /category slug - but that didn't help either. I saw that the /?category_name=/example-category/ would go to the correct page - at some point during my trials and errors - so when I put ?category_name= into the category slug on the permalinks page - it works - but it's ugly and I don't like it. Also - I tried to put just "cat" into the category slug - but it too returned a 404.

    I don't know if it's linux or IIS - my host is BlueHost.


  5. memitch08
    Posted 5 years ago #

    Another note - it seems this issue has effected all of my sites. Not just this one.

  6. So if all your permalinks are hosed, and the htaccess file is there... then either a server settings changed (meh, maybe) or the rewrite rules got flushed form the db.

    and if I can find that thread again... gah.

    Go resave the settings on the permalinks page. what happens?

  7. memitch08
    Posted 5 years ago #

    So I didn't realize that they had moved the network plugins - so I did have the remove /blog slug plugin activated through the network admin.

    I deactivated this - but I still get the same results - except now - I get the /blog slug in my permalinks. The categories now look like /blog/category/example-category and the result is a 404 page.

    When I set the permalinks to default - to reset - it goes to:
    /?cat=4779 - and I do not get a 404 page - the category is displayed.

    But when I change to custom permalinks - the permalinks for categories points to: /blog/category/ which results in a 404 page.


  8. memitch08
    Posted 5 years ago #

    I believe the problem is with 3.1 onward -

    I had no problem with permalinks before upgrading - it was only after the upgrade - so it seems funny that the server settings would change at the same time.

    I found I can eliminate the /blog slug from wp-admin/network/site-settings.php.

    But the category still will only work with the /?category_name=/example-cat permalink.


  9. crock2
    Posted 5 years ago #

    I think I'm having a similar problem. My custom structure is /archive/%postname%/ and I have no category base or tag base. Unfortunately since 3.1 all of my tag and category pages are now re-written to /archive/tag/example-page and /archive/category/example-page.

    Basically they are taking the custom structure as the base now.

    I run my own LAMP server and have changed nothing. No new plugins, no old plugins to consider and nothing else that could explain this besides a WordPress bug.

    I'm heading over to the bug tracker page now to see if this is a known issue. If I find anything I'll be back.

  10. I found I can eliminate the /blog slug from wp-admin/network/site-settings.php.

    Yes but NOTE! If you ever go in and re-save your permalinks, it'll come back!

    I don't know if it's linux or IIS - my host is BlueHost.

    Go ask BlueHost please and thank you :D

  11. @memitch, right that means your PRETTY permalinks are not working. If the htaccess file is in place, go hassle your host.

    the /blog part is a separate issue.

  12. welshy
    Posted 5 years ago #


    I had same problem, under the permalinks setting next to Category base I entered: blog

    Not sure if it will fix your problem but it helped me.

  13. welshy
    Posted 5 years ago #

    Ok forget my first comment, seems like the problem reoccurred when I edited the custom menu.

  14. diegopolo
    Posted 5 years ago #

    I have the same problem in http://br.wwwhatsnew.com

    I am redirecting the *categoria* url to the Search page

    The problem began with the upgrade to 3.1.1

  15. diegopolo, please make a new topic all your own :)

Topic Closed

This topic has been closed to new replies.

About this Topic