Support » Networking WordPress » plugin: Remove Blog Slug for resolving multisite url confusion?

  • Resolved daitya

    (@daitya)


    Maybe if I’m lucky, Andrea will see this and help me out with some advice…?

    I’m looking for the Remove Blog Slug plugin. Ipstenu mentioned that Andrea and Ron are the plugin’s authors, but no sign of it over at wpmututorials.com.

    Actually, I’m experiencing a conflict between the main site category urls and the sub site category urls. Refer to this post. Now I’m wondering whether using a plugin to remove the ‘/blog/’ from the url might resolve the confusion?

    I’ve been looking all over for the solution, but – tell the truth – I’m not really even sure what is causing the problem.

    Ipstenu’s write-up about switching to Multisite breaking links points to the plugin as one possible fix.

    BTW, has this issue of the ‘/blog/’ slug in url been addressed in WP 3.1?

Viewing 15 replies - 16 through 30 (of 35 total)
  • Indeed this must be fixed to either optional or atleast able to change it from /blog/ to something else.

    Oddly, it’s only the main site that has this. All my network sites don’t have /blog preceding their posts.

    You can remove the blog slug completely.

    Go into the primary site options in the network admin, and set your permalinks without blog included, to something like /%postname%/. Go back to the permalinks settings in your site’s dashboard, you should notice that /blog is removed from the permalinks. Set them to your desired structure again and save.

    This should remove the blog slug from your URLs.

    @jeff have you tried it in 3.1?

    You could do this in 3.0, but it was technically a bug that allowed you to do so. in 3.1 this behavior was changed.

    @andrea_r Yes, it still works. Here is a post I just made on my development install, which is in a subdirectory of the main blog, using its wp-content directory and database, but a separate install. /optic/ is the root of this multisite installation.

    http://jeffsebring.com/optic/no-blog-slug-wordpress-3-1-multisite-example-post/

    I haven;t had the chance to tinker, but Ipstenu was having issues. that’s why I asked.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    *blink* *goes to try this*

    ETA Okay this DOES NOT work on my Site with BuddyPress. Interesting.

    I am not using BuddyPress, just to be clear. I’ve done this on a number of sites, with all beta versions of 3.1 as well.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    Okay, it DOES change it, but it DOES NOT change the wp-admin/options-permalink.php part.

    THAT has /blog/ hard coded in :/ AND if you save permalinks there, it resets to /blog/<whatever>.

    Ah, did I not mention that part, in my post above – Remove /blog in url for root blog in wordpress 3.1 multisite installation… ;=)

    Oops!

    Let me mention it here then…

    Once you’ve found that the /blog is removed from your posts “live” permalink structure, do NOT go back in and change/save it again. It’s already “fixed”.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    Right 🙂 Which means IF you do want to change your permalinks, you have to ALWAYS do it from Network Settings.

    This is not… tenable or sustainable for CLIENT sites, alas.

    I’m not sure how this would be bad for a client. I don’t generally advise clients that it is wise to change permalinks, rather the opposite.

    True that, Ipstenu.

    Ipstenu said:

    Right 🙂 Which means IF you do want to change your permalinks, you have to ALWAYS do it from Network Settings.

    This is not… tenable or sustainable for CLIENT sites, alas.

    Users the world over are hoping you’ll do this… ;=)

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    I’m not sure how this would be bad for a client. I don’t generally advise clients that it is wise to change permalinks, rather the opposite.

    It’s bad because they can change it and thusly break their links.

    Of course they shouldn’t change their permalinks! Have you ever met a client who always does exactly what they should, all the time? 😀

    And if for some reason a plugin or upgrade flushes their rewrite rules and they need to resave their permalinks to fix it… this’ll bork it.

    It’s bad because they can change it and thusly break their links.

    Of course they shouldn’t change their permalinks! Have you ever met a client who always does exactly what they should, all the time? 😀

    Not sure if im missing something but if you go into the client sites permalink settings, the /blog/ is not there which means they can’t really screw anything up. The client sites permalinks start from that sites name.. eg domain.com/Client_Site/hello-world/

    Im using a sub-directory install. lets say you change /blog/ to a static term like /cheese/ (via network_admin>site>edit>settings)
    domain.com/cheese/hello-world/

    As long as you black-list cheese in the “Banned Names” field (via network_admin>settings) so clients can’t create sites called cheese, you wont have any problems with permalinks colliding..

    RIGHT?¿? or am i completely missing something?

    Im new to WPMU so forgive me if i’ve made this post out of ignorance..

Viewing 15 replies - 16 through 30 (of 35 total)
  • The topic ‘plugin: Remove Blog Slug for resolving multisite url confusion?’ is closed to new replies.