[wp-trac] [WordPress Trac] #12002: Option to /blog prefix on permalinks (was: WPMU should not lock the root blog into using a /blog prefix on permalinks)

WordPress Trac wp-trac at lists.automattic.com
Thu Jun 16 14:58:27 UTC 2011


#12002: Option to /blog prefix on permalinks
-------------------------+-----------------------------
 Reporter:  wpmuguru     |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  Permalinks   |     Version:  3.2
 Severity:  blocker      |  Resolution:
 Keywords:  needs-patch  |
-------------------------+-----------------------------
Changes (by djio):

 * severity:  normal => blocker
 * cc: wordpress@… (added)
 * component:  Multisite => Permalinks
 * version:  3.0 => 3.2
 * keywords:   => needs-patch


Comment:

 Just to pont a real life situation:[[BR]]
 Where I come from, and I mean Brazil, major companies block some words
 like hot, sex, porn, fuck, and also '''blog''' to avoid waste of employees
 labor time with "minor distractions". So, the employees can't access
 blogspot and so, but they can't also access their own company's posts
 because of the infamous mandatory /blog/ prefix

 I don't mean creative or development companies, but any other market or
 industry. It's sad but true. I encounter myself in the position of a long-
 time developer facing this same problem over and over: when I offer
 Multisite solutions using WP to my clients I must always ask how is their
 proxy/firewall policy agains the 'blog' word, and most of the time people
 won't change the policy so I must find another solution. I believe that in
 this case hardcoding a solution will never be a solution, because I'll
 lose it in next WP update.

 My idea for a solution is to set this "compatibility mode to avoid
 conflicts" as an option in the main settings page. In addition the word
 'blog' should be optional too, if I prefer 'news' instead (or any other),
 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.

 ---

 I tried removing the /blog/ completely in the code but my website just
 ignores it, please check
 [http://www.djio.com.br www.djio.com.br] in the categories sidebar widget:
 every category has a /blog/ prefix and it doesn't work if a manually
 remove the prefix i the URL.

 I usually help the community with Localizations of WP Core and Plugins
 (GlotPress, etc.) but I didn't want to mess with anything submiting a
 patch without knowing exactly the implications, so I ask, what exactly
 files deal with /blog issue?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12002#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list