Plugin yìí kò tíì ṣe àyẹ̀wò pẹ̀lú àwọn ìtújáde mẹ́ta pàtàkì tó kẹ́yìn ti WordPress. Ó lè jẹ́ pé a kò tọ́jú tàbí ṣe àtìlẹ́yìn fún un mọ́, ó sì lè ní àwọn ọ̀ràn ìbámu nígbà tí a bá lò ó pẹ̀lú àwọn ẹ̀yà WordPress tuntun.

FOCUS Cache

Àpèjúwe

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Ìtumọ̀ Yorùbá: ’t need (W3 Total Cache), or were old and broken.

On the sites IÌtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’d recommend using Memcached, Redis, or your other quality cache of choice.

IÌtumọ̀ Yorùbá: ’ve been heavily influenced by redis-cache, wp-redis, W3 Total Cache, and wp-memcached to name a few.

Ìgbéwọlẹ̀

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.

Àwọn àgbéyẹ̀wò

Ọwẹ́wẹ̀ 8, 2017
I have installed some other cache plugins. I set expire time to 0, but the cache disappeared after 30 minutes. I donÌtumọ̀ Yorùbá: ’t know why and have no idea. my problem solved by your plugin. thanks for good job! hope more features on this.
Ka gbogbo àgbéyẹ̀wò 1

Àwọn Olùkópa & Olùgbéejáde

“FOCUS Cache” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

Àwọn Olùkópa

Túmọ̀ “FOCUS Cache” sí èdè rẹ.

Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.

Àkọsílẹ̀ àwọn àyípadà

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