Description
WARNING The development of WP-FFPC had been put on hold.
If you need new features, please send code and pull requests to WP FFPC @ Github.
A short why: I developed this plugin in 2010 to support my own site. Right now, as it is, its working on a few sites I still maintain for friends and since I dont need any additional features, Im not planning to extend it with things I have no real use of. During the past years Ive received some heartwarming donations unfortunately the amount never came close to consider the project financially beneficial. I removed the donation links and put it on hold for now.
WP-FFPC is a cache plugin for WordPress.
It works with any webserver, including, but not limited to, apache2, lighttpd, nginx.
It can be configured together with NGiNX but use memcached plugin directly from the webserver, bypassing PHP.
Requirements
This plugin does not kick in right after activation. You have to adjust the setting in Settings -> WP-FFPC and save the settings.*
- WordPress >= 3.0
- at least one of the following for storage backend:
- memcached with PHP Memcached > 0.1.0
- memcached with PHP Memcache > 2.1.0
- APC
- APCu
- PHP 5.3+ is really highly recommended, see Known issues
Known issues
- errors will not be displayed on the admin section if PHP < 5.3, only in the logs. This is due to the limitations of displaying the errors ( admin_notices is a hook, not a filter ) and due to the lack of proper anonymus functions in older PHP.
- If youre using PHP 5.4+ avoid the APC backend: the plugin with that setup can even make your site slower. Please use APCu or memcached in this case.
Features:
- various backends
- memcached with PHP Memcached
- memcached with PHP Memcache
- APC
- APCu
- cache exclude options ( home, feeds, archives, pages, singles; regex based url exclusion )
- minor Woocommerce support
- (optional) cache for logged-in users
- 404 caching
- canonical redirects caching
- Last Modified HTTP header support (for 304 responses)
- shortlink HTTP header preservation
- pingback HTTP header preservation
- talkative log for WP_DEBUG
- multiple memcached upstream support
- precache ( manually or by timed by wp-cron )
- varying expiration time for posts, taxonomies and home
- (warning: untested since WordPress 3.8) WordPress Network support
- fully supported domain/subdomain based WordPress Networks on per site setup as well
- will work in Network Enabled mode only for subdirectory based Multisites ( per site settings will not work in this case )
Many thanks for donations, contributors, supporters, testers & bug reporters:
Harold Kyle, Eric Gilette, doconeill, Mark Costlow, Jason Miller, Dave Clark, Miguel Clara, Anton Peleev, Firas Dib, CotswoldPhoto, tamagokun, Many Ayromlou, mailgarant.nl, Christian Rner, Ameir Abdeldayem, Alvaro Gonzalez, Meint Post, Knut Sparhell, Christian Kernbeis, Gausden Barry, Maksim Bukreyeu, Lissome Hong Kong Limited, Gabriele Lauricella, 7th Veil, LLC, Julia Harsch, Grant Berntsen, Jorgen Ilstad, Cinema Minima for Movie Makers Worldwide
Screenshots
Installation
- Upload contents of
wp-ffpc.zipto the/wp-content/plugins/directory - Enable WordPress cache by adding
define('WP_CACHE',true);in wp-config.php - Activate the plugin through the
Pluginsmenu in WordPress ( site or Network wide ) - Check the settings in
Settings( site or Network Admin, depending on activation wideness ) ->WP-FFPCmenu in WordPress. - Save the settings. THIS STEP IS MANDATORY: without saving the settings, there will be no activated caching!
Using the plugin with NGiNX
If the storage engine is either PHP Memcache or PHP Memcached extension, the created entries can be read and served directly from NGiNX ( if it has memcache or memc extension )
A short configuration example is generated on the plugin settings page, under NGiNX tab according to the saved settings.
NOTE: Some features ( most of additional HTTP headers for example, like pingback, shortlink, etc. ) will not be available with this solution.
FAQ
-
Did you save the settings as mentioned in this document?
Do you have at lest one supported backend? -
So far this only happened if PHP 5.4 or higher was used with APC.
Please avoid this setup; PHP 5.4 shipped opcache and APC is full of bugs since then. Use APCu with PHP 5.4+. -
No, it doesnt, and with the way its currently working, it never will.
WP-FFPC is using the URL as key for caching, so it cant differentiate if there is no change in the URL.
(I personally also disagree with separation of mobile and non-mobile theme; you need to support a plethora of screen sizes and resolutions, so just use responsive designs instead of splitted logics.) -
Sure. Send me a code and a pull request on WP FFPC @ Github.
Unfortunately I dont have the resources to code it myself, but there are plenty of WordPress developers who would probably do it for a minor fee.
