Permalink Structure Problems in 3.1

  • MTS

    (@sciarrin)


    14 years ago

    Using multisite in 3.1 with a sub-directory set-up.

    Noticed a strange hiccup in my permalink structure today, and I’m not sure what happened. Apologies for this message being fairly long in advance!

    The Problem
    ————
    All of my URLs for blog posts, custom post types, and taxonomies now use the current structure:

    Custom post type: https://www.domain.com/blog/feature/%title%
    Custom taxonomy: https://www.domain.com/blog/program/%title%
    Regular blog post: https://www.domain.com/blog/%year%/%month%/%day%/%title%

    Before, they were using one of the following:

    Custom post type: https://www.domain.com/feature/%title%
    Custom taxonomy: https://www.domain.com/program/%title%
    Regular blog post: https://www.domain.com/%month%/%day%/%title%

    Solution
    ——–

    When I noticed this problem, I went to Network Admin > Sites and changed the Permalink Structure under the “Settings” tab. I noticed that somehow, it had appended the “/blog” there.

    I thought that would do the trick.

    However, I went back into the Dashboard of the site, and went to update the permalink settings. Not only had it not removed “/blog” in the options presented to me, it wouldn’t allow me to update my permalink structure to what I wanted. Every time I saved, it would revert to the default setting.

    What to Do?
    ———-

    I looked in my theme’s functions and there’s nothing mucking up the permalinks there. So my guess is that it’s somehow related to the server. Could it be an error with my .htaccess file? A permissions error?

    Your suggestions welcome — if this has been posted before, please let me know!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Yeah. /blog/ is appended, by default, to the main site on your network when there is a subdirectory install.

    Previously, there was a bug we all ruthlessly exploited to circumvent that.

    Now they fixed it so we can’t.

    There IS a plugin, but it doesn’t work all the way (internal links are broken a bit).

    Mind you, it SHOULD NOT affect Custom Post Types.

    Thread Starter MTS

    (@sciarrin)

    Augh. That seems like the most ridiculous default ever — especially if you are trying to use it like a CMS. Not every post type or taxonomy should fall under “/blog”. And it defeats the point of creating a rewrite!

    What can I do to have it not appear on my custom taxonomies?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    I wrote a longer explanation of this with 3.0 – https://code.ipstenu.org/2010/switching-to-wordpress-multisite-breaks-links

    I’m a bit surprised, though, that it’s affecting your CPTs, since I can’t reproduce THAT. They are NOT supposed to have /blog/ I thought

    Turn off your plugins for starters.

    Thread Starter MTS

    (@sciarrin)

    Oh, I’ve gone through and tried to figure out which plugin could be causing the problem. It’s slightly maddening.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Does it works with them all turned off?

    I will note… I found a sort-of fix, but I don’t really recommend it. What I did was made three sites:

    main
    videos
    news

    Then I made the NEWS site (which did not have /blog/ in the URLs) the main site and deleted the main site. My news site now has urls of domain.com/2011/blahblah

    But there were a LOT of other problems that came with doing this.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Permalink Structure Problems in 3.1’ is closed to new replies.