[wpmu-trac] Re: [WordPress MU Trac] #641: blog URLs redundantly defined and hardcoded in DB - headache

[WordPress MU Trac]

#641: blog URLs redundantly defined and hardcoded in DB - headache
--------------------------+-------------------------------------------------
 Reporter:  jeremyclarke  |        Owner:  somebody
     Type:  defect        |       Status:  new     
 Priority:  normal        |    Milestone:          
Component:  component1    |      Version:          
 Severity:  normal        |   Resolution:          
 Keywords:                |  
--------------------------+-------------------------------------------------
Comment (by lunabyte):

 Site, home, files, etc. I could see being a global/site option pretty
 easy.

 Others though, where someone may have certain blogs with one setting,
 other with another, might be a little more tricky to overcome.

 If we're getting into saving DB space, magpie takes a LOT, especially when
 we're talking hundreds/thousands of blogs. Rewrite rules take their fair
 share as well, but we're getting into WP core vs MU core stuff. Although,
 I could see something that perhaps checks for the rewrite pattern, and if
 it's standard it grabs the global option, if it's customized it would grab
 the local one.

 Maybe put a function_exists around the current functions, then add in
 additional wpmu functions to override. Optional, of course, maybe similar
 to defining sunrise, it could check for a definition of say,
 GLOBAL_OPTIONS, and/or bounce against a setting in the blogs table
 (similar to spam, mature, etc.) where by default it's global options, with
 the site admin able to specify whether or not to use local blog options
 instead.

-- 
Ticket URL: <http://trac.mu.wordpress.org/ticket/641#comment:3>
WordPress MU Trac <http://mu.wordpress.org/>
WordPress Multiuser