Load packaged object cache when advanced-cache.php and object-cache.php don't implement wp_cache_init( ) — at Version 10
|Reported by:||wonderboymusic||Owned by:|
|Cc:||tollmanz@…, mikeschinkel@…, kpayne@…, aaroncampbell|
Description (last modified by wonderboymusic)
This ticket has 2 purposes:
1) introduces wp_using_ext_object_cache() - mimic wp_suspend_cache_invalidation() and disallow direct access to $_wp_using_ext_object_cache, cleans up importing of globals in functions and provides function to modify that global
2) load the wp-packaged object cache when object-cache.php doesn't implement wp_cache_init()
3) adds file_exists for advanced-cache.php
wp_start_object_cache(), at its core, is on the hunt for wp_cache_init() and then sets the toggle for the external object cache. We only care about the external object cache if it has that function. Rather than throwing a fatal error if their is a missing method, load the default object cache.
If someone installs Memcached properly, then nothing changes - file loads, all is good. If they install a blanks file, the default Object Cache will load. If they install an external object cache without wp_cache_init(), the default cache loads.
IMO - there is no reason to turn off non-persistent caching or throw a fatal error if the author of a cache plugin sucks or the user made a mistake in moving the files.