Pods Alternative Cache is a file-based or database-based caching solution for hosts that have limitations on object caching.
Check out our GitHub for a list of contributors, or search our GitHub issues to see everyone involved in adding features, fixing bugs, or reporting issues/testing.
Hosts like WPEngine have limits set on their object caching engine that are based on what they find optimal for their environment. Sometimes, plugins, themes, and even WordPress core can utilize object cache to the point where it gets too full. When that happens, certain caching engines like APC can remove objects from their cache and that can cause what appears to be random numbers of queries on each page load.
What Pods Alternative Cache does is store all of the Pods objects that need caching, separate from the default object caching engine. Depending on the environment or site, this may still not be optimal. You'll want to test things out and keep an eye on your site's performance to see if it's the right fit for you.
In your wp-config.php, or prior to the
plugins_loaded action, you can define other constants to change how the plugin works.
Change the storage type (be sure to deactivate/activate between storage type switches):
define( 'PODS_ALT_CACHE_TYPE', 'db' ); // Default is 'file', you can choose 'memcached' too
Change the path to the File cache folder:
define( 'PODS_ALT_FILE_CACHE_DIR', 'path/to/folder' ); // Default is 'wp-content/podscache'
Set MemCached Server host or IP address
define( 'PODS_ALT_CACHE_MEMCACHED_SERVER', '127.0.0.1' ); // Default is 'localhost'
Set MemCached Server PORT number
define( 'PODS_ALT_CACHE_MEMCACHED_PORT', '11211' ); // Default is '11211'
Disable Pods Alternative Cache:
define( 'PODS_ALT_CACHE', false ); // Default is true
Requires: 3.8 or higher
Compatible up to: 4.6
Last Updated: 3 weeks ago
Active Installs: 200+
0 of 1 support threads in the last two months have been marked resolved.
Got something to say? Need help?