WordPress Plugin WP-FFPC - NOT MAINTAINED ANY MORE
14ff53b371
git-svn-id: http://plugins.svn.wordpress.org/wp-ffpc/trunk@684144 b8457f37-d9ea-0310-8a92-e5e31aec5664 |
||
---|---|---|
readme.txt | ||
uninstall.php | ||
wp-ffpc-abstract.php | ||
wp-ffpc-acache.php | ||
wp-ffpc-admin.css | ||
wp-ffpc-backend.php | ||
wp-ffpc-class.php | ||
wp-ffpc-nginx-sample.conf | ||
wp-ffpc.php |
=== WP-FFPC === Contributors: cadeyrn Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XU3DG7LLA76WC Tags: cache, memcached, full page cache, NGiNX, memcache, page cache Requires at least: 3.0 Tested up to: 3.5.1 Stable tag: 0.6.1 License: GPLv3 License URI: http://www.gnu.org/licenses/gpl-3.0.html Cache WordPress to memcached and serve them with NGiNX - unbeatable speed! == Description == WP-FFPC ( WordPress Fast Full Page Cache ) is a cache plugin for [WordPress](http://wordpress.org/ "WordPress"). Supports PHP Memcached, PHP Memcache and APC as storage engines. = Features: = * [NGiNX](http://NGiNX.org "NGiNX") compatibility * full Wordpress Network support * cache exclude possibilities ( home, feeds, archieves, pages, singles ) * (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 * (optional) talkative log for troubleshooting * multiple memcached upstream support Many thanks for supporters, testers & bug reporters: [Eric Gilette](http://www.ericgillette.com/ "Eric Gilette"); [doconeill](http://wordpress.org/support/profile/doconeill "doconeill"); [Mark Costlow](mailto:cheeks@swcp.com "Mark Costlow"). Thanks for [Hyper Cache](http://wordpress.org/extend/plugins/hyper-cache "Hyper Cache") for beeing inspirational. == Installation == 1. Upload contents of `wp-ffpc.zip` to the `/wp-content/plugins/` directory 2. Enable WordPress cache by adding `define('WP_CACHE',true);` in wp-config.php 3. Activate the plugin through the `Plugins` menu in WordPress ( site or Network wide ) 4. Check the settings in `Settings` ( site or Network Admin, depending on activation wideness ) -> `WP-FFPC` menu in WordPress. 5. Save the settings. THIS STEP IS MANDATORY: without saving the settings, there will be no activated caching! == Frequently Asked Questions == = How to use the plugin on Amazon Linux? = You have to remove the default yum package, named `php-pecl-memcache` and install `Memcached` through PECL. = Information: network wide settings always overwrite site settings = Since the plugin can be used as per-site configured in a network, if the plugin get network active later, the network settings will always overwrite the per site configuration. = Information: Log levels = Log levels ( if logging enabled ) includes info, warning and error level messages; error level most usually means PHP configuration error or missing plugin configuration. = Information: Using it 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. = Information: Support & Info = I provide support for the plugin as best as I can, but it comes without guarantee. Please post feature requests to [WP-FFPC feature request topic](http://wordpress.org/support/topic/feature-requests-14 "WP-FFPC feature request topic"). = PLugin requirements = * WordPress >= 3.0 and **at least one** of the following for storage backend: * PHP APC * PHP Memcached > 0.1.0 * PHP Memcache > 2.1.0 == Screenshots == 1. settings screen, cache type and basic settings 2. debug and in depth-options 3. cache exceptions 4. apc settings 5. memcached servers settings 6. NGiNX example == Changelog == = 1.0 = *in RC state* * Software licence change from GPLv2 to GPLv3 * backend code completely replaced ( object-based backend, improved readability & better structure, lot less global vars, etc. ) * added proper uninstall ( uninstall hook was not removing options from DB, uninstall.php will ) * revisited multisite support ( solved overwriting-problems ) * preparations for localization support ( all strings are now go through WordPress translate except for advanced-cache logging, since there's no WordPress available at that point ) * more and more detailed log & error messages * retouched Memcache initialization ( faster connect, cleaner persistent connections ) **Bugfixes** * reported bug of faulty expiration times fixed * eliminated warning message for memcache when no memcache extension is present * fixed multisite settings overwriting issue **Dropped functions** * APC entry compression support **Planned features for next major release** * support for Redis backend * optional NGiNX header preservation for shortlink, pingback and last-modified headers = 0.6.1 = *2013.03.08* * refactored & corrected backend status check for memcached driver = 0.6 = *2013.03.08* * true WordPress Network support: * if enabled network-wide, settings will be the same for every site * if enabled only per site settings could vary from site to site and cache could be active or disabled on a per site basis without interfering other sites * delete options button to help solving problems = 0.5.1 = *2013.03.07* * settings link for plugins page * readme cleanup * setting link URL repair & cleanup = 0.5 = *2013.03.06* WARNING, MAJOR CHANGES! * default values bug ( causing %3C bug ) really fixed by the help of Mark Costlow <cheeks@swcp.com> * UI cleanup, new tabbed layout * WP-FFPC options moved from global menu to under Settings in both Site and Network Admin interfaces * added 'persistent' checkbox for memcached connections * added support for multiple memcached servers, feature request from ivan.buttinoni ( ivanbuttinoni @ WordPress.org forum ) * case-sensitive string checks replaced with case-insensitives, contribution of Mark Costlow <cheeks@swcp.com> * refactored settings saving mechanism * additional syslog informations * additional comments on the code * lots of minor fixes and code cleanup * donation link on the top = 0.4.3 = *2013.03.03* * long-running %3C bug fixed by the help of Mark Costlow <cheeks@swcp.com>, many thanks for it. It was cause by a bad check in the default values set-up: is_numeric applies for string numbers as well, which was unknown to me, and cause some of the values to be 0 where they should have been something different. = 0.4.2 = *2012.12.07* * added optional sync protocoll option: replace all http->https or https->http depending on request protocol * binary mode is working correctly with memcached extension * added warning message for memcache extension in binary mode **KNOWN ISSUES** There are major problems with the "memcache" driver, the source is yet unkown. The situation is that there's no response from the memcached server using this driver; please avoid using it! = 0.4.1 = *2012.08.16* * storage key extended with scheme ( http; https; etc. ), the miss caused problems when https request server CSS and JS files via http. = 0.4 = *2012.08.06* * tested against new WordPress versions * added lines to "memcached" storage to be able to work with NGiNX as well * added lines to "memcached" to use binary protocol ( tested with PHP Memcached version 2.0.1 ) **KNOWN ISSUES** * "memcache" extension fails in binary mode; the reason is under investigation = 0.3.2 = *2012.02.27* * apc_cache_info replaced with apc_sma_info, makes plugin faster = 0.3 = *2012.02.21* * added syslog debug messages possibility * bugfix: removed (accidently used) short_open_tags = 0.2.3 = *2012.02.21* * NGiNX-sample.conf file added, NGiNX config is created from here = 0.2.2 = *2012.02.21* * memcache types bugfix, reported in forum, thanks! = 0.2.1 = *2012.02.21* * bugfix, duplicated inclusion could emerge, fix added, thanks for Géza Kuti for reporting! = 0.2 = *2012.02.19* * added APC compression option ( requires PHP ZLIB ). Useful is output pages are large. Compression is on lowest level, therefore size/CPU load is more or less optimal. = 0.1 = *2012.02.16* * first public release