WordPress Ideas » Topic: Remove /blog/ on multisite installations

Ipstenu (Mika Epstein) on "Remove /blog/ on multisite installations"

Ipstenu (Mika Epstein) — Thu, 19 Feb 2015 20:21:48 +0000

I posted about this in more detail here: http://halfelf.org/2015/mailbag-trash-blog-slug/

It's a problem, we know, but the solutions thus far are incomplete.

Marie on "Remove /blog/ on multisite installations"

Marie — Thu, 19 Feb 2015 18:02:49 +0000

the plugin don't work well as as soon as there some update it comes automatically back to the blog, the CRON is necessary but it also means several times of 1h 404 pages

Marie on "Remove /blog/ on multisite installations"

Marie — Wed, 18 Feb 2015 20:57:06 +0000

great, you all work hard on this, thank you, it looks like it is almost ready, I hope for the next update :-)

Ipstenu (Mika Epstein) on "Remove /blog/ on multisite installations"

Ipstenu (Mika Epstein) — Wed, 18 Feb 2015 14:24:06 +0000

You can read the ticket. Yes.

Marie on "Remove /blog/ on multisite installations"

Marie — Wed, 18 Feb 2015 05:27:31 +0000

hi, still "working on it"?

Ipstenu (Mika Epstein) on "Remove /blog/ on multisite installations"

Ipstenu (Mika Epstein) — Wed, 23 May 2012 19:31:59 +0000

http://core.trac.wordpress.org/ticket/12002

wrk on "Remove /blog/ on multisite installations"

wrk — Wed, 23 May 2012 18:10:16 +0000

Very good idea!

I think the whole purpose of Wordpress's flexibility does not fit in the idea of a hardcoded /blog prefix.

My vote fore this!

DJIO on "Remove /blog/ on multisite installations"

DJIO — Wed, 15 Jun 2011 18:37:15 +0000

In time,

This could be a good Idea to have this done for 3.2 launch
;-)

DJIO on "Remove /blog/ on multisite installations"

DJIO — Wed, 15 Jun 2011 18:36:10 +0000

I hate /blog/ prefix in my multisite installations

As far as I can see this was an arbitrary addition to the 3.1 version.
I couldn't find a single ticket (Trac) or suggestion (Ideas) about this.

Fact is I use WP for several companies as a CMS solution.
Unfortunately some of the companies use proxy blockers to filter employees access to the web. Now guess on of the most popular words they commonly block... BLOG !!

So the employees can't access blogspot and so, but they can't also access their own company's posts becouse of the infamous mandatory /blog/ prefix

My idea for a solution is to set this "compatibility mode" to avoid conflicts as optional in the main settings page. In addition the word 'blog' should be optional too, if I like 'news' instead, there would be no problem with proxies, blockers, etc.?

As a conclusion, each scenario is different, we cannot impose a (commonly blocked) word as a mandatory prefix if we want to keep growing in the professional market.