I think I’m getting somewhere. Could it have something to do with the face that the WPCACHEHOME is actually set in an include of wp-config.php. So I am not setting WPCACHEHOME in wp-config.php, but in wp-config.inc.php.
My wp-config.php
<?php
/**
* The base configurations of the WordPress.
*
* This file has the following configurations: MySQL settings, Table Prefix,
* Secret Keys, and ABSPATH. You can find more information by visiting
* {@link http://codex.ww.wp.xz.cn/Editing_wp-config.php Editing wp-config.php}
* Codex page. You can get the MySQL settings from your web host.
*
* This file is used by the wp-config.php creation script during the
* installation. You don't have to use the web site, you can just copy this file
* to "wp-config.php" and fill in the values.
*
* @package WordPress
*/
require_once(dirname(dirname(__FILE__)).'/config/wp-config.inc.php');
/* That's all, stop editing! Happy blogging. */
/** 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');
-
This reply was modified 8 years, 11 months ago by
mclaurent.
-
This reply was modified 8 years, 11 months ago by
mclaurent.
I think this seems indeed to be the cause. I have now removed the line from wp-config.inc.php that defined WPCACHEHOME, and let the plug-in write the setting itself into wp-config.php.
I had the same issue, same error message. Found this in my wp-config:
define('WP_CACHE', false);
Re-enabling caching here solved the problem:
define('WP_CACHE', true);
With this setting emptying the cache does not cause errors. Yay!
Fo some reason the define(‘WP_CACHE’, true); gets deleted from the config.php file