Resolved - Define status SQL possibilities in config file.

bq. *Update:* On Mon, May 20, 2013, I added several statements to config file. Need to finish with status statements in BlogData.pm.

bq. *Update:* on Thu, May 24, 2013, finished with adding status statements for BlogData.pm into the config file. Good enough for now.

For "status in ('o','v')" type of SQL statements, store the info in Config.pm as much as possible.

If need to add a new status option, should only have to edit code in one spot: the config file. 

Should not have to search for the SQL statements in multiple places to accommodate the new status addition.

For point 1. in this to do list...

bq. /blogpost/921/02May2013/Add-blog-reply-options

... need to add a new status option when hiding the blog reply link from an author's blog post.

bq. *Update:* - Thu, May 23, 2013 - will probably add a new column to the content table or create a new table to manage hidden blog reply posts and users blocked from replying, etc. Will NOT add a new status code in the content table.

But then will need to make sure the new status still appears in the other user's stream and in searches, etc.

h2. Existing status codes

For blog and microblog posts:

* o = open or displayed for all to view
* d = deleted. only logged-in owner can undelete
* p = pending or hidden from front page of a user's stream or All users stream, but it's still available for searches
* v = version. old version of a blog post
* s = secret or private blog posts that are accessible only to logged-in owner. not available for any searches.

o, p, and v posts can be viewed by ALL users, including users not logged in.

d and s are accessible only to logged-in owners.

#junco
#resolved