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 Display Date Same as Server HTTP Headers Date
- Google Cloud Load Balancer Firewall Rules
- Create Instance Template out of Disk Snapshot on Google Cloud
- Get User IP Address From Google Cloud Load Balancer
- Connect as Root using WinSCP on Google Cloud Compute Engine
- Become Root on Google Cloud Compute Engine VMs
- Connect to Google Cloud Compute Engine VM via PuTTY SSH
- DigitalOcean Slow, My Experience
Updated Posts
- PHP GetHostByAddr() Slow? Make it Faster
- PHP GetHostByName() Slow? Make it Faster
- How to Match Newline with Strpos() in PHP
- Use PHP Strpos() to Check if a String Starts with
- How to Run a Command with Time Limit in Bash Linux
- Unable to extract and upload PackageInfo.xml
- Stop Bad Bots from Crawling Your Website
- DEB.SURY.ORG Updated the Signing Key (March 2019)