Posted on December 11, 2016 at 11:46 am
If you get this warning message in your WordPress website:
Notice: Constant WP_POST_REVISIONS already defined in /var/www/wordpress/wp-config.php on line 95 |
Make sure that the definition of the constant WP_POST_REVISIONS is after WordPress has been loaded. Edit wp-config.php and make sure WP_POST_REVISIONS is defined after require_once(ABSPATH . ‘wp-settings.php’); like this:
/** Disable post revisions */
define('WP_POST_REVISIONS', false );
/** Disable plugin and theme editor */
define('DISALLOW_FILE_EDIT', true);
/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php'); |
Other Posts
- PHP Generate Secure Random Passwords
- Google Cloud SQL and Public IP Address Security
- How to use Highlight.js to highlight code
- Nginx HTTP to HTTPS and non-www to www behind Google Load Balancer
- Quota 'IN_USE_ADDRESSES' exceeded. Limit: 8.0 in region
- Only allow Google Load Balancer traffic (Firewall Rules)
- Lost connection during Debian apt-get upgrade
- Bootstrap 3 Navbar with Logo Image
Updated Posts
- PHP StrToTime() Returns Incorrect Timestamp '-1 MONTH'
- PHP Correctly Get Last 12 Months (Month per Month)
- Nginx Redirect From a Website to Another Website
- PHP Multi-cURL to Run Parallel cURL Requests (Example)
- Let's Encrypt on Nginx and SSL Grade A+
- Vertically align Facebook and Twitter share buttons
- Download Windows 10 ISO without Media Creation Tool
- DEB.SURY.ORG Updated the Signing Key (March 2019)