Plugin Directory

Angry Creative Inspector

Inspects, logs and with the aid of WP-CLI, it may even repair possible issues with your WordPress installation.

  1. Download, unzip and upload the plugin folder to the /wp-content/plugins/ directory
  2. Activate the plugin through the 'Plugins' menu in WordPress (activate for network if multisite)
  3. Make sure the right log file path is set under the 'Settings/AC Inspector' menu in the WP admin panel (in network admin if multisite)

To get the file permissions and site visibility routines working properly, edit wp-config.php and add the following (before "That's all, stop editing!"):

//define("FS_METHOD", "direct"); // Recommended: Enable this for dev/stage-environments
define("DISALLOW_FILE_MODS", true); // Recommended: Enable this for production-evironments

define("HTTPD_USER", "www-data"); // The user of your HTTP-daemon (Apache/Nginx/Lighttpd/etc)
define("FS_USER", "my-user"); // The username/accountname you login and maintain your WordPress install with
define("SITE_RELEASE_TIER", "production"); // Possible values: 'local', 'development', 'integration', 'test', 'stage', 'production'

Setting FS_METHOD to 'direct' will ensure write permissions in your entire WordPress-directory for FS_USER as well as HTTPD_USER, while enabling DISALLOW_FILE_MODS will restrict the HTTPD_USER to only having write permissions as configured under the 'Settings/AC Inspector' menu in the WP admin panel (in network admin if multisite). Default allowed dirs:


Setting SITE_RELEASE_TIER helps the inspector determine wether the site should allow search engine indexing or not. Forgetting to block search engines in a development or staging site can have terrible results on your search engine ranking.

Requires: 4.0 or higher
Compatible up to: 4.2.5
Last Updated: 3 months ago
Active Installs: 90+


0 out of 5 stars


Got something to say? Need help?


Not enough data

0 people say it works.
0 people say it's broken.

100,1,1 100,1,1 100,1,1
0,1,0 0,1,0 100,1,1