WordPress 3.1 Broke Permalinks

  • Resolved kenrik

    (@kenrik)


    14 years 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 - 16 through 30 (of 55 total)
  • Rmedia

    (@rmedia)

    Look, I’m not arguing, I just find it frustrating. You would too.

    The other thing I just .. don’t … understand is why if something as complicated as say, Drupal, can release updates without touching the database, why WordPress always has to [moronic expletive deleted] around in the data for even the most minor upgrades.

    Leaving the data alone would be a HUGE step in the right direction for stability. Either that, or only touching the data when there is just no other alternative. It should be a last resort.

    It would make going back and forth in versions so much easier.

    I just loaded a completely fresh install of 3.1, it works and it’s nice, but as I was going through it, I kept wondering “they needed to munge my database for this? I don’t get it.

    If the decision is to include a minor feature and touch the database, or omit the minor feature and leave the db alone, I overwhelmingly vote for the latter. That’s just my opinion.

    Stability is everything.

    Everything.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    I’m not going to get into a debate about how and why WordPress does what it does, because it will dilute our ability to help in SOLVING your problem.

    Which is the goal of this. If you want to pitch in and help the devs find better and safer ways to do a major release (and yes, 3.1 is a MAJOR release), go do that. But this thread is for SUPPORT and that’s as far as we need to go.

    Do you still need help? If not, let’s be done here and go about supporting folks ??

    Rmedia

    (@rmedia)

    Fair enough, here is my solution:

    I installed 3.1 fresh, in a directory with no files.

    I installed the old WP installation on another domain, and we are literally copy/pasting articles from that site to the new one. All 10,000+ of them.

    It will probably been the end of the week until we are finished, but it works, and it is the ONLY thing that has worked for us.

    We could stick with the old site, I suppose, but I fear what will happen when 3.11 is released. We just need to get over the hump, and nothing listed above did anything at all.

    You have to do what you have to do.

    I suppose the issue is solved.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Drupal does do a DB upgrade, by the way. https://drupal.org/node/570162 step 10

    I installed the old WP installation on another domain, and we are literally copy/pasting articles from that site to the new one. All 10,000+ of them.

    Why not do an export/import with the build in WordPress functionality?

    i’m thinking the rewrite rules got flushed, and yes we do have a thread here (still can;t find it) that showed how to re-set them.

    Yes, ipstenu & I sympathize, that’s why we’re trying to find a way to fix the issue to save you work.

    Rmedia

    (@rmedia)

    Oh, this is really embarrassing.

    Somehow, someway,one of our admins turned off mod_rewrite during the upgrade process. Don’t ask me how, because frankly it was a fluke.

    I have been misattributing a problem to WordPress that is a result of our own error.

    I feel so terrible. Really I do. I look back in frustration and I feel like such an ass. I was just flustered.

    Please forgive me.

    We got 3.1 working.

    It was not, I repeat NOT a problem with WordPress itself. 100% our fault.

    I’m sorry.

    YogieAnamCara

    (@yogieanamcara)

    Well it is still the same bug as in 3.0.5

    https://core.trac.www.ads-software.com/ticket/16201#comment:8

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    I wonder if it’s related to the fact that the blog slug was force returned to 3.1 (after we all had that happy hack for 3.0.x)…

    Nacin said this:

    I think I’ve seen this before in MU, but I was just never able to reproduce it. It also didn’t just happen on upgrade, but that’s another story. I ended up just dropping some code in the 404 handler to check if the rewrite rules were corrupted (obvious by the missing /blog/) and set a locking transient then flush the rewrite rules if so.

    So I wonder if it’s that the re-write rules are seen as ‘broken’ because of a non-standard change? Give that Yogie’s ‘fix’ is to re-apply permalinks, that makes a disturbing bit of sense.

    YogieAnamCara – Did you remove the blog slug from your main site?

    well we have just encountered this error and we’re wondering if there has been a fix yet?

    We tried all the permalink flushing and rebuilding, auto and manual generating htaccess etc all with no solution.

    article/page links work perfectly fine, archive and category links do not work however, and either give a single post page (strange) or a 404 not found error..

    Solutions would be nice, huh?

    Ok I wont open a new thread since I have exactly the same problem on a multisite install, BUT ONLY on the main site !!!

    All subsites are /%category%/%postname%/ (know it is bad as otto says ?? but works.

    Only main site is affected, and impossible to :

    – access post using /%category%/ in slugs
    – acces post clicking on any category / tag link

    as you can see on this page : https://passion-cheval.net/dossiers-articles/

    I removed the %/category%/ in the permalink to keep the post accessible, but clic on the act or tags it retrurn a 404

    uggly permalink works BUT links by categories dont anyway.

    WP 3.1 updated from 3.0.5
    BP 1.2.8
    HTaccess WP generated with no other rules

    EDIT :
    Ok solved for me.
    A plugin using $wp_rewrite; function.

    But anyway there is an issue on that… too many people complains about it !

    Solutions would be nice, huh?

    there were two rewrite rules that got updated.

    go back to the network setup screen and get the htaccess file rules. paste them in.

    huh ok but where do you find this on a running network ?

    there is no more “network setup screen” !

    there is no more “network setup screen” !

    Sure there is.

    unless you removed the line from config that shows it. Some instructions told you to do that. (not mine)

    define('WP_ALLOW_MULTISITE', true);

    this line shows the menu item. this is all that line does. the menu item will be under network admin after setup.

    it is different than this line:

    define('MULTISITE', true);

    which tells wordpress a network is running.

    Ohhhh ok

    of course deleted this line ??

    ok ok trying that immediatly ??

    so my htaccess is exactly as mentionned…

    Anyway, found the culprit (a plugin)

    my rewrite are fine.

    thanks ??

    Hey,

    So I think I fall under this thread. I have been going around the web for the last few days trying to solve the problem as why my permalinks are now broken.

    I recently set up network sites on my wordpress. So now all permalinks are broken.

    I have tried disactivating all of my plugins, deleting my .htaccess file.

    I am on 3.1 and I am stuck.

    I am happy for somebody in the organisation to access my admin if necessary.

    Right now, if you press on any of my links on my site then you end up at a dead page.
    https://masshuu.com/blog/
    https://masshuu.com/blog/blog/2010/10/ghost-towns/

    Please is there any thoughts on this.

    thanks, matt

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