Charleston Software Associates

less info
123 reputation
bio website
location Charleston, SC
age 49
visits member for 2 years, 3 months
seen Feb 28 at 1:11


Dad. Explorer. Rum Lover. Code Geek. Not Necessarily In That Order.

comment Is moving wp-config outside the web root really beneficial?
This response does not directly address the question. Any plugin author can have a field day with WordPress if they convince you to install their code and have malicious intent. It is no different than willingly installing a virus on your system. This argument to not move wp-config.php is pointless. This is like saying that willfully installing a car bomb in your car makes setting the car alarm useless. Technically true but WTF?!?
comment Is moving wp-config outside the web root really beneficial?
This response is spot-on. My web hosting company had a drive array failure. When all was said & done they restored the system PARTIALLY. Turns out they used a series of cPanel/WHM scripts to rebuild httpd.conf files that did so incorrectly. Luckily I already had wp-config.php outside of the doc root, but if I hadn't the contents were there for the taking. Yes rare, but as noted the rare cases are what you need to worry about. Also, stating "simple minded folk would be lost" is a bad excuse for having LESS security.
comment Any examples of adding custom fields to the category editor?
Use add_action(<taxonomy-slug>."_add_form_fields",my_action) to extend the category form editor. i.e. add_action("store_add_form_fields",array($this,'add_form_fields)) in an object context for your custom action hooks for a taxonomy type of 'store'. Version 3.X+ of WordPress prefers the <taxonomy-slug><blah> format for action hooks, the older style of "edit_category_form_fields" and others are marked as "legacy support" in the code, which means they may/will eventually go away. ref:…
awarded  Supporter
awarded  Autobiographer