WordPress.org

Support

Support » How-To and Troubleshooting » Subdomain / Subdirectory 404 After 2.5.1

Subdomain / Subdirectory 404 After 2.5.1

  • I just upgraded two of my blogs to 2.5.1 (was waiting for K2 RC6).

    The installation directory looks like this:
    brettmickelson.com/blog
    And I have used cPanel to configure this subdomain:
    blog.brettmickelson.com

    WordPress has both the WP directory and the blog URL set to blog.brettmickelson.com.

    Previously, a reader could view EITHER blog.brettmickelson.com OR brettmickelson.com/blog and successfully view the site.

    Now, however, a 404 error is received when viewing brettmickelson.com/blog. This happens in both Firefox and IE. In Firefox, the page tries to redirect to blog.brettmickelson.com/blog, but in IE it stays on brettmickelson.com/blog.

    Any thoughts? I’ve run a few searches on here and come up with nothing. I would like for both to work since some people view the subdirectories in their favorites (for some reason).

    The addresses are:

    blog.brettmickelson.com (works)
    brettmickelson.com/blog (does not work)
    roadtrip.brettmickelson.com (works)
    brettmickelson.com/roadtrip (does not work)

Viewing 12 replies - 1 through 12 (of 12 total)
  • I should clarify a few things as well…

    I tried changing the WP settings to reflect brettmickelson.com/blog instead and that worked, but then for some reason blog.brettmickelson.com did not work properly. It didn’t provide the same 404 error, but it redirected to my main brettmickelson.com page.

    I’ve also tried using a different theme.

    I would like people to be able to view both the subdomain AND the subdirectory URLs if possible.

    whooami

    @whooami

    Member

    canonical urls, perhaps?

    depending on what you upgraded from, you didnt say.

    One of them was upgraded from 2.3.3 and the other was upgraded from something older…maybe 2.2.1?

    With a quick glance at that Canonical URLs page, it looks like you might be right on, I’ll look more closely.

    whooami

    @whooami

    Member

    2.2.1 was pre-canonical urls.. Google knows all –

    So it may come down to a choice between (a) dealing with it (b) disabling the entire function?

    I might just deal with it then…from what I’ve read there, I’m almost certain this is the cause, although I somehow never noticed it after the upgrade to 2.3.

    whooami

    @whooami

    Member

    Sigh.

    Google knows all.

    Did you actually look at any of the links returned? Had you clicked through to Mark’s blog, you would have noticed he provides a plugin that disables it.

    And I am just guessing at the cause.

    I did look through the links and I did see the plugin that disables it which is why I said “disabling the entire function”.

    Previously, a reader could view EITHER blog.brettmickelson.com OR brettmickelson.com/blog and successfully view the site.

    You might think that was a good thing, although it was not. It is called duplicate content, so be happy that WP prevents it.

    whooami

    @whooami

    Member

    the first link in that google search is to Mark Jaquith’s web site. Last I checked he was still a WP dev. At the bottom of his post, is a link to a plugin. The link works.

    You might think that was a good thing, although it was not. It is called duplicate content, so be happy that WP prevents it.

    As I’ve explained, I UNDERSTAND why this has changed. But in this case it is not what I WANT. And that should be up to me.

    the first link in that google search is to Mark Jaquith’s web site. Last I checked he was still a WP dev. At the bottom of his post, is a link to a plugin. The link works.

    Are you kidding me? I’ve made it clear twice now that I SAW the plugin. I do not want to entirely disable this feature, which is WHAT THE PLUGIN DOES.

    in this case it is not what I WANT. And that should be up to me.

    It is open source – meaning it’s up to you to modify its behaviour by writing your code. Or just use htaccess to redirect the wrong (subfolder url) to the right one (subdomain).

    Or just use htaccess to redirect the wrong (subfolder url) to the right one (subdomain).

    Don’t want to sound like a moron here, but how would I do that?

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Subdomain / Subdirectory 404 After 2.5.1’ is closed to new replies.