Cloudflare
| 开发者 |
icyapril
manatarms thillcf deuill epatryk jacobbednarz |
|---|---|
| 更新时间 | 2021年6月3日 09:11 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 5.6 |
| 版权: | BSD-3-Clause |
标签
下载
1.3.16
1.3.3
3.0.4
3.2.1
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
3.4.1
3.5.0
3.5.1
3.6.0
3.7.0
3.8.0
3.8.1
3.8.2
3.8.3
3.8.4
3.8.5
3.8.6
3.8.7
3.8.8
3.8.9
4.0.0
4.1.0
4.2.0
4.2.1
4.2.2
4.3.0
4.4.0
4.5.0
4.5.1
1.2.4
1.2.5.Beta
1.2.6.Beta
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
1.3.17
1.3.18
1.3.19
1.3.2.Beta
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
3.0.0
3.0.1
3.0.2
3.0.3
3.0.5
3.0.6
3.1.0
3.1.1
3.2.0
详情介绍:
What this plugin can do for you
Automatic Platform Optimization (APO)
Take your WordPress site's performance to the next level with Automatic Platform Optimizations (APO). APO allows Cloudflare to serve your entire WordPress site from its edge network ensuring consistent, fast performance for visitors no matter where they are. Find out more in our announcement blog.
One-click WordPress-optimized settings
The easiest way to setup Cloudflare for your WordPress site. Let us configure Cloudflare with the tried and true settings for an optimal experience.
Web application firewall (WAF) rulesets
Available on all of Cloudflare’s paid plans, the WAF has built-in rulesets, including rules specifically tailored to mitigate WordPress threats and vulnerabilities. These security rules are always kept up-to-date, once the WAF is enabled, you can rest easy knowing your site is protected from even the latest threats.
Automatic cache purge on website updates
If you don't take advantage of the performance benefits of Automatic Platform Optimization for WordPress, using the Cloudflare plugin still ensures that changes to the appearance of your website purge the cache. This means that you can focus on your website, while we ensure that the latest static content is always available to your visitors.
Additionally, Cloudflare’s plugin for WordPress automatically refreshes the Cloudflare cache of static content for each post/page/custom post type when you update the content.
Additional features
- Header rewrite to prevent a redirect loop when Cloudflare’s Universal SSL is enabled
- Change Cloudflare settings from within the plugin itself without needing to navigate to the cloudflare.com dashboard. You can change settings for cache purge, security level, Always Online, and image optimization
- View analytics such as total visitors, bandwidth saved, and threats blocked
- Support for HTTP2/Server Push
安装:
Prerequisite
Make sure your PHP version is 7.2 or higher.
From your WordPress Dashboard
- Visit “Plugins” → Add New
- Search for Cloudflare
- Activate Cloudflare from your Plugins page.
- Download Cloudflare
- Upload the “cloudflare” directory to your “/wp-content/plugins/” directory, using ftp, sftp, scp etc.
- Activate Cloudflare from your Plugins page.
- Go to https://dash.cloudflare.com
- Login with your cloudflare account. If you don’t have a Cloudflare account, first sign up for Cloudflare.
- Navigate to the API Tokens section of the user profile (found in the top right corner of the dashboard).
- Select 'Create Token'
- Select the 'WordPress' Template
- Select the Account and Zone to grant the plugin access to
- Then select "Continue to Summary" and "Create Token"
- Copy your API Token
- Return back to WordPress Cloudflare Plugin page
- Enter your email address and paste your API Token
- Press Login.
更新日志:
4.5.1 - 2021-06-03
- Rewrite PHP 8 bootstrap files for
symfony/polyfillto be PHP 7 compatible
- Document unintuitive
transition_post_statusWP hook behavior - Only purge public taxonomies while clearing any empty values from the list
- Better handling of cases where
wp_get_attachment_image_srcis false and not a usable array - Support activation of IDN domains
- Improve development experience by shipping a Docker Compose file with more tooling and documentation
- Purge posts when transitioning to or from the 'published' state
- Remove conditional logic for subdomain, allow to activate APO feature on the subdomain
- Further work to autocorrect APO settings
- Sanitise sensitive HTTP header logs
- Stop sending
cfCRSFTokento remote API - Add warnings for incorrectly configured Automatic Platform Optimization
- Purge posts that go from public to private
- Purge pagination for first 3 pages
- Fix warning for file_get_contents of composer.json
- Deprecate REST dashboard analytics
- Allow configuration of Cloudflare credentials via environment variables
- Prevent purging of cache before comments have been moderated
- Remove unnecessary symfony/yaml dependency
- Removed development dependencies from vendor directory
- Update CLOUDFLARE_MIN_PHP_VERSION to match the plugin requirements
- Drop support for PHP 5.6, 7.0 and 7.1
- Add Jacob to maintainers list
- Revert Add pagination purging
- Add pagination purging
- Purge taxonomy feed URLs
- Fix changing APO settings (cf, wordpress, plugin) when running on subdomain
- Fix setting hostname override
- Add subdomain support for APO card
- Added automatic purge cache on new comment
- Added composer's type=wordpress-plugin for Bedrock users
- Fixed typo in readme.txt
- Fix modify header exception thrown during wp-cron
- Cloudflare Plugin
- Fixed setting all APO values properly for correct dashboard rendering
- re-relase broken version, no changes
- Fixed typo in config.js(on) that resulted in warning #292
- Check for array indicies are set before using #278
- Added APO support
- Renamed Automatic Cache Management card to Auto Purge Content On Update
- Bump cloudflare-plugin-backend v2.3.0 and cloudflare-plugin-frontend v3.1.0 #283
- Bump cloudflare-plugin-backend #276
- Fixed Cache Purges failing #266
- Purge attachment URLs #208
- Purge URLs on page/post update #206
- Turn on IPv6 by default #229
- Add constants for better control HTTP/2 Server Push #213
- Allow custom actions for purge url and purge everything actions #212
- Updated list of contributors.
- Updated tested WordPress version to latest (5.2.2).
- Added support for API Token authentication.
- Bug in cf-ip-rewrite
- Added a new filter cloudflare_purge_by_url allowing users to have better control on automatically purged urls.
- Potential bug by using $_GET.
- Added a new Splash Screen
- Added userConfig.js file allowing custom configurations.
- Added logs in debug mode for Automatic Cache Purge.
- Added logs for oversized Server Push HTTP headers.
- Automatic Cache Purge now purges Autoptimize by everything rather than by URL.
- Updated IP Ranges
- Bug where domains which had capital letters not working.
- Bug where Automatic Cache Purge couldn't purge front page.
- Bug related to work with IWP.
- Bug where if PHP is compiled with ipv6-disable flag, it crashed the site.
- Bug where accounts which had more than 20 zones would not show up correctly.
- Bypass Cache By Cookie functionality.
- HTTP/2 Server Push functionality (disabled by default).
- Lowered the plugin size.
- Automatic Cache Management feature includes purging taxonomies.
- Automatic Cache Management feature supports sites which use both HTTP and HTTPS.
- Admin bar disappearing from the plugin.
- Bug where spinner was loading forever.
- Bug where the backend errors where not being shown in the frontend.
- Issues where IE11 was not working properly.
- Moved Admin Bar behind Automatic Cache Purge toggle.
- Added ability to automatically purge cache when a post is published, edited or deleted. (Thanks to brandomeniconi and mike503)
- Added ability to work with WordPress MU Domain Mapping plugin. (Thanks to brandomeniconi)
- Changed the UI to look more like cloudflare.com dashboard.
- Changed plugin description.
- Disabled showing WordPress Admin Bar and Edit Post Link to avoid caching problems for users using HTML Caching.
- Fixed bug where require vendor folders was not working.
- Fixed bug where static files were cached which caused issues updating the plugin.
- Fixed dependencies which caused issues with PHP Compatibility Checker plugin.
- Added ability to toggle Development Mode.
- Fixed bug where active zone dropdown was not working properly.
- Compressed resources to lower plugin size.
- Updated Cloudflare logo.
- Fixed bug where refactored Flexible SSL fix was causing the settings page hook not to load.
- Ability for users to toggle Automatic HTTPS Rewrites (enabled by default, solves for most mixed content errors).
- Fixed an issue where low PHP version where getting syntax error.
- Fixed issue where some users using Flexible SSL where not able to login to wp-admin .
- Fixed a bug where the active zone selector was not paginating through the whole zone list.
- Fixed an issue where the setting for Image Optimization was being displayed incorrectly.
- Fixed a bug in Analytics where the Uniques Visitors data was not displaying accurately.
- Compressed assets to lower plugin size.
- Hooks loading logic refactored to make it more simple and readable.
- Fixed an issue where some domains were being incorrectly propagated to the domain selector dropdown
- Fixed an issue where the Web Application Firewall was accidentally triggering RFI Attack Rules
- Fixed an issue where image optimization was not being enabled for Pro and higher Cloudflare plans
- Disabled HTTP/2 Server Push which was leading to 520 and 502 errors for some websites.
- Fixed HTTP/2 Server Push exceeding the header limit Cloudflare has which caused 520 errors.
- Fixed warning message in HTTP/2 Server Push.
- Added one-click application oft WordPress specific recommended settings
- Added ability to purge the Cloudflare cache
- Integrated with WordPress cache management to automatically clear the Cloudflare cache on updating site appearance
- Added ability to change Cloudflare settings (Always Online mode, I’m Under Attack, Image Optimization, Security Level, Web Application Firewall)
- Added Analytics showing Cached Requests, bandwidth used, unique visitors, threats blocked
- Added Header rewrite to prevent a redirect loop when Cloudflare’s Universal SSL is enabled
- Added HTTP/2 Server Push support
- Added Support for PHP 5.3+
- Removed HTTPS Protocol Rewriting
- Removed submission of spam comments
- Removed ability to toggle Development Mode On/Off
- Updated user interface
- Started to support WordPress 3.4+ instead of 2.8+ because we depend on the WordPress Options API