Inspects, logs and with the aid of WP-CLI, it may even repair possible issues with your WordPress installation.
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:
wp-content/uploads/* wp-content/blogs.dir/* wp-content/cache/* wp-content/avatars/* wp-content/*/LC_MESSAGES/*
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.7
Last Updated: 5 months ago
Active Installs: 100+
Got something to say? Need help?