Posts 404ing after permalink change

  • I recently downloaded and installed wordpress 2.7.1. Every attempt I have made to change my permalink structure has been met with a 404 page appearing where all of my posts should be located according to the permalink change.

    I had assumed that maybe the update was just not taking hold anywhere other than to the links on the main page. I changed the permalink structure and attempted to visit the post at the default ?p=123, it also returned a 404 error. The only way to make my posts visible on their own page was to return my permalinks setting to its default.

    Any ideas? Let me know if you would like me to try / test something.

Viewing 14 replies - 31 through 44 (of 44 total)

  • I’m having the same issue with ‘pretty permalinks’, could this be a larger issue?
    My blog is only about 10 days old, everything is up-to-date.

    I’ve tried looking at the ‘Using Permalinks’ guide and:
    My .htaccess is updating
    My servers supports mod_rewrite
    I am using only /%postname%

    The permalinks work in ‘Default’, but not ‘Pretty’. If I click on a post’s title I get: Not Found’
    I’m new to WordPress, and I can’t make my site public until I get this issue fixed. Any help would be greatly appreciated.

    Update: It’s fixed. I was missing the / after /%postname%
    Sometimes it’s the simple things!

    Americaninlima,

    I have installed and upgraded many versions of WordPress. One wonderful feature of WordPress 2.7 is the automatic update/upgrade features — that really work. I did the automatic upgrade from 2.7 to 2.7.1 as well as numerous plugin updates without any difficulty. I think you should be running 2.7, eventually.

    I had the same feeling about the new admin area as you do — at first. However, I don’t even think about it anymore now that I have used it for awhile.

    I must confess that when I upgraded my online blogs to 2.7, I thoroughly tested the new version first (see “Low-Stress WordPress Version 2.7 Upgrade“).

    After all you have been through, if you have a backup for 2.6 that would restore your blog to perfect health, it might be a good idea. However, at the very least, backup the current mySQL database first so that you can retrieve any posts you have created since your last backup. If it were me, I would also backup all of the current WordPress files, too: this might save you some time when you try the upgrade again. I assume your old backup included both the database and the WordPress files? If only the database, you will have to re-edit and upload any theme files you changed.

    With respect to Permalinks Moved Permanently, it might be worth a try, especially if you are thinking about restoring a previous WordPress version. What have you got to lose?

    As a last note, and for the long term, you might think about setting up your own test blogs. I have a test bed on my local PC (see “WampServer: A Test Bed For WordPress“) and also have an online test blog living in its own domain that I use to test new versions and plugins before using them on my main blog. My main blog does not have nearly the content on your blog, but I would still not like to have to do it over again. So, I test and backup. This takes all of the worry and stress out of making changes to my main blog.

    If you do restore to your older version, relax awhile and then try the upgrade again (possibly on your own test bed first).

    alexbasil,

    Thanks a lot for your posts. You are absolutely right about the “simple things”. The big problem about the “simple things” is that they are so darned hard to see: you can look at something like /%postname and just never notice that missing /. By pointing this out, you might have helped a lot of others solve their permalink problems.

    rtivel,
    I tried the Permalinks Moved Permanently plug-in, and it did not take the viewer to the old or new posts with pretty permalinks.

    The page would just sit there trying to load the new page for about 2 minutes and then a 404 error message would finally appear.

    So I’m stuck with a year’s worth of posts that can’t be accessed through their old permalink structure.

    I wish my problem were as easily fixed as alexbasil’s.

    Oh, and if it makes a difference: I upgraded to WordPress 2.7 through Fantastico Deluxe.

    I am still trying to get the pretty permalinks to work after upgrading 2.7.

    I read somewhere that I may need to clean my WordPress cache. Can anyone point me to a doc or a post that explains how to do this? Do I eliminate all files from the cache or just some?

    Okay, no one got back to me about how to clean the cache, and my pretty permalinks are still broken, after more than two weeks, so I’m trying a new solution:

    https://www.ads-software.com/support/topic/228380?replies=27

    Someone was having a similar problem three months ago when he upgraded to 2.7. It has to do with magic quotes being on, and how that interferes with 2.7.

    I just created a new file in my root directory called php.ini and put these instructions in it:
    magic_quotes_gpc = Off
    magic_quotes_sybase = Off

    Then I reset permalinks to pretty permalinks.

    I’m going to wait for an hour to see if this works.

    I tried the above fix last night, and it did not resolve the problem. All I get are error messages if I use any structure other than default.

    Does anyone have any other recommendations for me?

    I am disgusted with WordPress at this point and regret not going with a free wordpress.com blog or blogspot blog a year ago. I am not a programmer and so I cannot improvise a solution. All I did was try to upgrade thru Fantastico on MidPhase and it didn’t work.

    I am checking in again. It’s been three weeks since I upgraded to 2.7 and lost all my pretty permalinks. My blog traffic went down to 3 viewings a day for one week and now it’s inched up to a few dozen. I am beside myself. For this I spent more than one year building a great WordPress site and a steady readership?

    If anyone has more suggestions on how to fix pretty permalinks w/ 2.7, I’d love the input.

    Should I upgrade to. 2.7.1? Or will this screw up the whole thing?

    I fixed the problem tonight, after more than 1 month of broken permalinks.

    I thought, What the h*ll?, and did the automatic upgrade to 2.7.1 thru Fantastico, after disabling plugins.

    For whatever reason, after 2.7.1 was installed, I was able to go in and change the permalink structure from Default to pretty permalinks (with year, month and day). I saved the new permalink structure, and my new andold posts were instantly accessible.

    https://americaninlima.com/

    Americaninlima,
    Thanks so much for the very last post!! I too was recently working on the same issue and was about to bang my head into a brick wall.

    All I did was upgrade my wordpress through my control panel and BAMB! My posts are alive and well and working!

    THANK YOU!

    https://www.totemwebsolutions.com/blog

    I also found out instead of using /%postname%/ i used /%postname%

    It will definately show an error

    Can anyone tell me HOW to start a new thread?

    Look at the bottom of the page when viewing the list of threads.

    I’ll trim our replies from this thread once you have it figured out.

Viewing 14 replies - 31 through 44 (of 44 total)
  • The topic ‘Posts 404ing after permalink change’ is closed to new replies.