New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the advanced-cache.php (or object-cache.php) to get rid of wp-config.php modification #17
Comments
Thanks @ideag for pointing this possibility out :) |
This seems like a very good idea since If someone needs to use // Default mu-plugins directory if you haven't set it
defined( 'WPMU_PLUGIN_DIR' ) or define( 'WPMU_PLUGIN_DIR', WP_CONTENT_DIR . '/mu-plugins' );
// Also load mercator for domain mapping
require WPMU_PLUGIN_DIR . '/mercator/mercator.php'; |
Upon more investigation advanced-cache.php won't work since we need to enable it via a constant and filter. object-cache.php is a better candidate. |
Actually, plugin could modify |
@ideag no, the problem is we still need to define WP_CACHE in wp-config.php for advanced-cache.php to be loaded. |
@anttiviljami yeah, i meant |
Ah, ok 👍 Yes, definitely |
There's also a possibility to get rid of
db.php
as well by plugging into the advanced-cache.php file, which has the ability to modify the global $table_prefix variable since it gets loaded beforewp_set_wpdb_vars();
The text was updated successfully, but these errors were encountered: