[wp-trac] [WordPress Trac] #16614: Allow blog privacy to be set in wp_config.php

[WordPress Trac]

#16614: Allow blog privacy to be set in wp_config.php
-------------------------+------------------------------
 Reporter:  kanuck54     |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:  3.1
 Severity:  normal       |  Resolution:
 Keywords:  close        |
-------------------------+------------------------------

Comment (by kanuck54):

 My main issue with that solution is that `wp-content/` is typically
 synched between live and dev environments; so ultimately, if I write a
 theme function or a plug-in, it's going to have to look at a constant
 defined in each config file anyway.

 And should my plug-in or theme wind up deactivated during a live-to-dev
 migration, the worst case scenario is that I could potentially have a
 broken dev site being indexed by a search engine.

 It's just not as robust as I'd like. I find it's always safest to assume
 myself and everyone else an idiot, and therefore I always like things
 idiot-proofed.

 I understand where you're coming from, and obviously in the meantime I'll
 just short-circuit `blog_public` based on my own constant in
 `wp_config.php`. I'm just hoping you'll consider this for the
 future—especially since I would disagree with the notion that the blog
 privacy option ought to be downplayed. It looks like #16416 will re-word
 the option to better indicate to non-techies what it does; and for the
 tech-inclined, it does exactly what it ought to do, so being able to
 control it absolutely alongside other instance-specific options would be
 ideal.

 Cheers.

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