Cache Alternatif Pods


Pods Alternative Cache provides optimal performance with Pods sites on hosts with no object caching or low limits. It was developed for and tested on the WPEngine platform to improve performance of cached objects generated from Pods, but it works on numerous other hosting providers.

Cache Alternatif Pods est un excellent ajout à un site utilisant déjà la mise en cache d’objets, il sépare et permet à Pods d’utiliser une mise en cache persistante plus cohérente sans affecter d’autres extensions/plugins et des objets de mise en cache de WordPress. Surtout lorsque l’on utilise des configurations plus grandes, ce plugin améliore les performances en s’assurant que les autres objets nécessaires ne sont pas supprimés par le serveur pour faire place aux objets Pods mis en cache.

This plugin requires the Pods Framework version 2.4 or later to run.

For more information on how to use this plugin, see

Also check out the FAQ below for more details on customizing the configuration through your wp-config.php file.


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.


  1. Unpack the entire contents of this plugin zip file into your wp-content/plugins/ folder locally
  2. Upload to your site
  3. Navigate to wp-admin/plugins.php on your site (your WP Admin plugin page)
  4. Activate this plugin

OR you can just install it with WordPress by going to Plugins >> Add New >> and type this plugin’s name


Why an Alternative Cache?

Les hôtes comme WPEngine ont des limites définies sur leur moteur de mise en cache d’objets qui sont basés sur ce qu’ils trouvent optimal pour leur environnement. Parfois, les extensions/plugins, les thèmes et même le noyau WordPress peuvent utiliser le cache d’objets au point où il devient trop complet. Lorsque cela se produit, certains moteurs de mise en cache comme APC peuvent supprimer des objets de leur cache et peuvent causer ce qui semble être un nombre aléatoire de requêtes sur chaque chargement de page.

Le Cache Alternatif Pods stocke tous les objets Pods qui nécessitent une mise en cache, séparés du moteur de mise en cache des objets par défaut. Selon l’environnement ou le site, cela peut ne pas être optimal. Il vous faudra donc tester les choses et surveiller les performances de votre site pour voir si c’est le bon choix pour vous.

What options are available?

Dans votre wp-config.php ou avant l’action plugins_loaded, vous pouvez définir d’autres constantes pour modifier la façon dont l’extension/plugin fonctionne.

Modifiez le type de stockage (assurez-vous de désactiver/activer entre les commutateurs de type de stockage):

define( 'PODS_ALT_CACHE_TYPE', 'db' ); // Default is 'file', you can choose 'memcached' too

Changer le chemin vers le répertoire du Ficher de cache:

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', '' ); // Default is 'localhost'

Set Memcached Server PORT number

define( 'PODS_ALT_CACHE_MEMCACHED_PORT', 11211 ); // Default is 11211

Désactiver Pods Alternative Cache

define( 'PODS_ALT_CACHE', false ); // Default is true

Disable object cache fallback, when File writes fail:

define( 'PODS_ALT_CACHE_FALLBACK', false ); // Default is true


4 janvier 2019
It helped me to clean up the autoloaded data in the wp_options table. Before: 0.775MB After: 0.065MB
3 septembre 2016
A site we built was totally grinding to a halt on our BlueHost shared hosting account when we started getting traffic over a few hundred sessions. Other caching options weren't working and Pods Alt Cache did the trick! After setting up the cache parameters, it very quickly resolved the issue. Great file-based solution for server configurations that don't offer customized control over object/mem caching.
3 septembre 2016
Works like a charm! I had to disable object caching on one site due to inconsistency of GoDaddy's caching with another plugin (Google Calendar Events). After renaming of the /wp-content/object-cache.php file (to just make object caching not function) - PODS ended in Fatal Error crashing the entire website: Cannot call overloaded function for non-object in .../general.php on line 230 Then I spotted this cute "Pods Alternative Cache" plugin, installed it and made the trick with object caching disabling again. Keeping my breath I reloaded my website and ALL WORKED! Now both PODS and GCal Event are functioning with no errors. Thank you guys very much for creating this addition to your beautiful PODS framework!
Lire les 5 avis

Contributeurs & développeurs

« Cache Alternatif Pods » est un logiciel libre. Les personnes suivantes ont contribué à cette extension.


Traduisez « Cache Alternatif Pods » dans votre langue.

Le développement vous intéresse ?

Parcourir le code, consulter le SVN dépôt, ou s’inscrire au journal de développement par RSS.


[2.1.2] September 4th, 2021

  • Fixed: Now compatible with PHP 8.0+

[2.1.1] August 14th 2021

  • Tested against WordPress 5.8 for compatibility

[2.1.0] July 14th 2020

  • Added: Now requiring PHP 5.6+
  • Added: Freemius support when running Pods 2.7.17+
  • Fixed: SiteGround and other sites that use the domain name in the path no longer cause directory/file writes to fail.

[2.0.7] March 2nd 2020

  • Fix DB-based storage value sets (props @Danone89)
  • Tested against WordPress 5.4 for compatibility

[2.0.6] March 2nd, 2019

  • Fixed caching issues with fallback cache
  • Added more tests to improve stability

[2.0.5] November 15th, 2018

  • Fix PHP notices when handling fallback values

[2.0.4] October 26th, 2018

  • Added a new object cache fallback for File storage (default alt cache) so if any writes fail it will save them to the normal object cache; You can disable this by setting define( 'PODS_ALT_CACHE_FALLBACK', false );

[2.0.3] October 23rd, 2018

  • Fixed cases where transients/object cache could be used by Pods before Pods Alt Cache fully loads
  • Updated WP compatibility version
  • PHPCS fixes

[2.0.2] June 2nd, 2017

  • Revamped branding assets
  • Fixed php notice
  • Fixed usage of Memcached port to be an integer

[2.0.1] July 13th, 2016

  • Fixed cache file/folder deleting bug that wouldn’t let Pods clear / preload caches properly
  • Typo fix (props @szepeviktor)

[2.0] June 23rd, 2016

  • Added support for a Memcache caching (props @shaer)
  • Added support for WP_Filesystem usage instead of using PHP directly
  • Added additional WPEngine compatibility
  • Refactored into a better OO pattern so the code is easier to use and extend
  • Added ability to create custom storage types through the pods_alternative_cache_storage_types filter, return $storage_types; where you’ve set $storage_types[ 'your_type' ] = 'Your_Class';
  • File storage now uses md5-based folder structure to avoid issues on sites with a large amount of cached objects to avoid having folders with too many files in them which could cause issues with certain hosts
  • Found a bug? Have a great feature idea? Get on GitHub and tell us about it and we’ll get right on it:

[1.0] April 16th, 2014

  • First official release!