VHOST deprecated notice, switching to SUBDOMAIN_INSTALL breaks sub-sites
So I inherited a, let’s say weathered, multisite installation. I’ve been updating and pruning dated plugins and what not, and upon turning on WP_DEBUG I see the following PHP notice:
define() was called with an argument that is <strong>deprecated</strong> since version 3.0! The constant <code>VHOST</code> <strong>is deprecated</strong>. Use the boolean constant <code>SUBDOMAIN_INSTALL</code> in wp-config.php to enable a subdomain configuration. Use is_subdomain_install() to check whether a subdomain configuration is enabled
As the error suggested, I switched to using define(‘SUBDOMAIN_INSTALL’), true;. While the main site seems to continue to function, all urls for sub-sites turn up broken. I understand it’s just a notice and leaving it as VHOST doesn’t really do any harm, BUT it wouldn’t certainly feel great to be able to turn on debug and have (or at least very few) errors.
Any ideas on what I’m doing wrong? Here’s the multisite portion of my wp-config for reference:
/* Multisite */ define('DB_COLLATE', ''); define('VHOST', 'no'); $base = '/'; define('DOMAIN_CURRENT_SITE', 'mysite.com' ); define('PATH_CURRENT_SITE', '/' ); define('BLOGID_CURRENT_SITE', '1' );
- The topic ‘VHOST deprecated notice, switching to SUBDOMAIN_INSTALL breaks sub-sites’ is closed to new replies.