WordPress 3.1 Broke Permalinks

  • Resolved kenrik

    (@kenrik)


    13 years, 9 months ago

    My site was working perfect with custom permalinks. Now after upgrading to 3.1 I get a 404 error using custom permalinks.

    Normal ugly permalinks work but the custom ones are broken ??

    here is my .htaccess please let me know how to fix this. 

    RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule . index.php [L]

# deny access to wp-config.php
<files wp-config.php>
order allow,deny
deny from all
</files>

# deny access to readme.html
<files readme.html>
order allow,deny
deny from all
</files>

# deny access to .htaccess
<files .htaccess>
order allow,deny
deny from all
</files>

# prevent folder browsing
Options All -Indexes

# prevent comment posting to requests with no referer
RewriteEngine On
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .wp-comments-post\.php*
RewriteCond %{HTTP_REFERER} !.*example.com.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) ^https://%{REMOTE_ADDR}/$ [R=301,L]

# limit size of request body
LimitRequestBody 10240000
Viewing 15 replies - 1 through 15 (of 55 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    The .htaccess is always the same, and not where the custom permalinks live.

    The most likely answer is that you have a plugin which is incompatible. Try deactivating all your plugins. Most of the permalink problems that have been on the forums today have been due to incompatible plugins.

    Thread Starter kenrik

    (@kenrik)

    All plugins are deactivated…

    Still broken..

    Possibly the theme? What did they change in the permalinks code that broke my site!

    Thread Starter kenrik

    (@kenrik)

    I found that no matter what permalink code I try to put in it’s still looking for /%category&/%postname%/ in the 404 error. The only permalink that works is “default”.

    Thread Starter kenrik

    (@kenrik)

    These are my plugins:

    Akismet
    Date Exclusion SEO
    Gravity Forms
    hRecipe
    Page Links To
    s2Member Pro
    User Locker
    WPtouch Pro

    Help!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    You may need to let WP regenerate your .htaccess.
    https://dre.im/if-pages-return-a-404-after-wordpress-3-1-upgrade

    Thread Starter kenrik

    (@kenrik)

    Tried it… for some reason it did not regenerate the htaccess file. ?

    I don’t know why they had to go and break stuff in this new release ??

    BTW. It’s a dedicated server running OSX 10.6.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Tried it… for some reason it did not regenerate the htaccess file.

    Okay, make a BLANK .htaccess file and set the permissions to 755 or whatever you need ?? Try letting WP update THAT.

    (Honestly, nothing works perfectly. This is actually a fairly rare issue, and everyone’s aware of it. As soon as cause is sorted out, I’m sure there will be something concrete said, but it never showed up in the 3 months of tests we had for 3.1.)

    Same for me. Site totally hosed. Creating blank .htaccess with 777 perms ineffective as WP 3.1 will not write an .htaccess entry. I’ll try a default one from a fresh install, if that doesn’t work I’m going back to 3.0.

    But it should still give you what to manually paste into your htaccess file.

    I fixed the error by removing from functions.php

    $wp_rewrite->flush_rules();

    Also I disabled simple tags plugin.

    Now category permalinks works fine on:

    https://www.maniadecelular.com.br/cat/modelos-celular

    Same here. Completely hosed permalinks.

    I’ve spend the last few hours trying to get them back, but no dice.

    This is why I generally don’t upgrade. Before this, I skipped the last 5 or so releases.

    If I have learned anything, it’s that it it ain’t broke, the chances of an “upgrade” breaking it outweight having an older version.

    I wish I had gone with my gut longer. Next time I get a stable release, I am not upgrading again unless I really need a feature desperately.

    IMHO, software is actually getting less stable, not more stable.

    I’ve used Linux for 10 years, and Ubuntu 10.10 is the only one that has ever locked up on me (and it’s done it about 8 times now).

    Not sure if it is related to a problem I just encountered. But could help some people anyway.

    Whenever I would save options in my theme, it would somehow drop the siteurl (domain and path) from all my links.

    I did find a workaround for my issue. In multisite network admin, by saving changes to the site info tab with “update siteurl and home” checked, it rewrites the siteurl and path and everything works again (until i change theme options again).

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Rmedia – You would be incorrect, but you’re entitled to your opinion. Software is within .004% as stable as it was 20 years ago (per H. Hecht, a risk analyst specializing in software).

    Did you try everything listed in here: https://www.ads-software.com/support/topic/troubleshooting-wordpress-31-master-list?replies=7

    alukii – Unrelated, I think, but an interesting find! Thanks for sharing.

    OF NOTE! Rolling back to 3.0.5 without a database backup is incredibly risky, and in doing so, you open the door for conflicts. Should your site break after you roll back, you’re kinda on your own.

    Yes, I tried it all.

    Ended up having to scrub the site. Even the restoration back to the previous version was borked (apparently there have been numerous database changes between our version and this one).

    We have to go back even earlier and it’s taking all day to restore (and probably tomorrow as well)

    Our site was in WordPress for 5 years. That’s a pretty good track record, I will admit.

    This release, though … well … I’m sorry, really sorry, but it’s just inexcusable. Some bugs here or there are of course understandable, but this was a showstopper on a pretty basic LAMP server that has been up 600 days without a single hiccup.

    Not just the bug, but the fact that nobody is really sure how to fix it.

    It’s a mess. An unmitigated mess. An effing disaster if you may pardon my french.

    Sometimes, it’s better just to leave well-enough alone, and I wish we would have.

    I love WordPress, I really do, but man … what was who smoking when they decided this was ready for prime time?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    We beta tested for 3 months. No one had this problem. If we can’t reproduce something, it’s kinda hard to debug it and prevent it. Also it’s mathematically impossible to test EVERY variation.

    Even the restoration back to the previous version was borked (apparently there have been numerous database changes between our version and this one).

    Depends what version you were ON before you upgraded, really. But the restore SHOULD be ‘revert to your older database’ and not just copy the files up and pray. Reverting without a DB backup has problems, as you’ve found, excuse yes, the database was updated.

    Try a blank 3.1 install on your server, see if it works, just for grins and giggles. You’re already down the rabbit hole.

    As a reminder to everyone – When you upgrade, make a backup FIRST, then upgrade. And if your life depends on WP, test the upgrade on a NON ‘live’ site first.

Viewing 15 replies - 1 through 15 (of 55 total)
  • The topic ‘WordPress 3.1 Broke Permalinks’ is closed to new replies.