Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter jentorme

    (@jentorme)

    Wait, you mean like *me* show other people how to do it and add something to the Codex?

    Ok, done!

    Interestingly enough, when I followed the link on that first post, this issue was addressed. But the longer code sample put in the Codex didn’t work for me, so I added my solution as an alternate.

    I love this trick! Actually, I can’t imagine how anyone runs a commercial site without it. So I hope this stops being a “hack” and becomes a feature pretty soon…

    Thread Starter jentorme

    (@jentorme)

    samboll,

    Thanks for the assurance. As far as I know, that code above just comes from some WP blog out there. It’s not in the docs. But it works great, and the ability to have a prod/devel server is pretty important for a commercial site. So if this is indeed the right way to do it, then, shouldn’t we:

    1) add this info to the Codex

    2) add the code to wp-config.php in the actual distribution, with an option to turn it on

    I think this should really be a feature included in WP itself. If the user selects “Use a staging / development / production server” option, then the values for STAGINGURL and LIVEURL are plugged into the above.

    jen

    Anyone figure this out?

    I’m having the exact same problem. The Amazon boxes look great in every browser but IE.

    Thread Starter jentorme

    (@jentorme)

    Ok boys, I know how to kludge around this. You just make your 404.php a PHP redirect to wherever you want your 404 to go.

    But I still don’t get why .htaccess can redirect a 403 and not a 404. It’s probably because once you have these rewrite rules in place, there really *is* no 404 … it’s just passed right on to WordPress.

    If that’s the case, I think the codex really needs a big bold section on this. Because I’ve found so many people on here with the same problem, always unanswered. You guys listening? Please update the docs. Thanks!

    Thread Starter jentorme

    (@jentorme)

    Ok, this is definitely a Mod_Rewrite issue.

    When using the “default” WordPress URL format (ugly), the ErrorDocument directive in the .htaccess file is read.

    But changing the permalinks to anything at all, any of the giving formats, will make the ErrorDocument line useless.

    Why?

    Alex, what’s your .htaccess look like?

    I’m new to WP and am very, very surprised at how many questions are on these forums … with so few answers. Don’t WP hacker/developer types ever read the forums?

    Forum: Fixing WordPress
    In reply to: 404 not detected

    epoks, what do you mean by “when I have permalinks activated”?

    Have you tried using different permalinks styles?

    At first I thought this had to do with my use of “/%postname%/” but I’ve tried the default permalinks and still have the problem. No one seems to know the answer or is listening in these forums … I’m doing archive searches and see the same question again and again for over a year, no answers. It’s depressing!

    mprewitt and bysse, I want to let you know that I also have an “active” thread on this very topic:

    http://wordpress.org/support/topic/242392?replies=3

    I’m doing the same thing you guys are, with an “ErrorDocument” directive in my .htaccess, but no matter what I put in it, it doesn’t seem to work! I can redirect my 403’s even offsite, to anywhere on the web, but I can’t redirect my 404’s for nothing. So the regular index.php loads, and that’s wrong!

    Hmm, this is looking like a WordPress FAQ! Except nobody seems to have the answer yet!

    Hey, did you guys ever find an answer?

    I think there’s something funny going on with Mod Rewrite so that these pages don’t 404 … then wordpress will display the default page for a “bad” URL.

    Why doesn’t the server step in first with the ErrorDocument line? That’s what I can’t figure out.

    Have you ever figured this out? Did anyone ever help you?

    I am having a similar problem. I’m trying to specify where to go for 404s in .htaccess but for some reason WordPress ignores it. It doesn’t ignore 403s, only 404s.

    Frustrating!

    Anyone ever find answers to these problems?

    I’m searching like mad through the forums, and it looks like a lot of people have similar problems but no answers anywhere. Are there other WordPress forums that we can go to for help?

    Brenton, I’m using 2.7 and my problem is similar.

    If I go to: http://example.com/biglong404urldoesnotwork

    the page will render a copy of my main static page, http://example.com/ but the title will say “Page not found”

    (It’s basically loading the index.php page)

    This happens no matter how I change the .htaccess file.

    Thread Starter jentorme

    (@jentorme)

    I’ve been playing wtih my permalinks and I changed it to one of the defaults and still have this problem, so it’s not related to the use of postname as the sole delineator in permalinks.

    To sum up: I can’t redirect 404’s with my .htaccess file. 403’s redirect fine through that but not 404s, which instead load the index.php file. Why? How to change this? Anyone out there?

    Thread Starter jentorme

    (@jentorme)

    I should also mention that I’m using “/%postname%/” as my permalink structure because the site design calls for that. I’ve had no other problems with it at all and aside from the inability to get the 404 in .htaccess, the site’s running beautifully.

    Please if anyone is out there, please help!

    Did you ever solve your problem?

    I’m having basically the same problem. I use “/%postname%/” too, and it’s worked well for everything except this.

Viewing 14 replies - 1 through 14 (of 14 total)