Este plugin no se ha probado con las últimas 3 versiones mayores de WordPress. Puede que ya no tenga soporte ni lo mantenga nadie, o puede que tenga problemas de compatibilidad cuando se usa con las versiones más recientes de WordPress.

FOCUS Cache

Descripción

I needed a persistent object cache while doing work on a budget hosting provider. A lot of the other file-based caching plugins were either bundled with other things I didn’t need (W3 Total Cache), or were old and broken.

On the sites I’ve tested this with, that have slow database servers, I have noticed an increase in page generation times of about 2x. On the other hand, for sites that have fast database servers it can actually increase page generation time. Whenever possible, I’d recommend using Memcached, Redis, or your other quality cache of choice.

I’ve been heavily influenced by redis-cache, wp-redis, W3 Total Cache, and wp-memcached to name a few.

Instalación

Install like any other plugin, directly from your plugins page or manually by copying the files to the plugins/ folder. Go to the plugin settings page at Settings->FOCUS Cache and click Enable Object Cache.

FAQ

Installation Instructions

Install like any other plugin, directly from your plugins page or manually by copying the files to the plugins/ folder. Go to the plugin settings page at Settings->FOCUS Cache and click Enable Object Cache.

Reseñas

8 de septiembre de 2017
I have installed some other cache plugins. I set expire time to 0, but the cache disappeared after 30 minutes. I don't know why and have no idea. my problem solved by your plugin. thanks for good job! hope more features on this.
Leer la 1 reseña

Colaboradores y desarrolladores

«FOCUS Cache» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

Traduce «FOCUS Cache» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

1.0.1

  • Bugfix: Plugin was unable to be activated in the “Add Plugins” page. This was due to the fact that WordPress detected the wrong PHP file as the plugin and tried to activate it. Renaming the “Plugin Name” header from the PHP files in the includes/ directory resolved the issue. Thanks to @ramonjosegn on the WordPress.org Support Forums for bringing this to my attention.
  • Bugfix: The plugin is now required to be activated across all sites in a multisite installation.
  • Readme updates.

1.0.0

First Version