Cloudflare

Описание

What this plugin can do for you

One-click WordPress-optimized settings

The easiest way to setup Cloudflare for your WordPress site.

Web application firewall (WAF) rulesets

Available on all of Cloudflare’s paid plans, the WAF has built-in rulesets, including rules that mitigate WordPress specific 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

Occurs when you change the appearance of your website. This means that you can focus on your website, while we ensure that the latest content is always available to your visitors.
(Note: By default, Cloudflare does not cache HTML, and a cache purge is not required on updating HTML content such as publishing a new blog entry).

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

Скриншоты

  • Cloudflare Plugin

Установка

Prerequisite

Make sure your PHP version is 5.3.10 or higher.

From your WordPress Dashboard

  1. Visit “Plugins” → Add New
  2. Search for Cloudflare
  3. Activate Cloudflare from your Plugins page.

From WordPress.org

  1. Download Cloudflare
  2. Upload the “cloudflare” directory to your “/wp-content/plugins/” directory, using ftp, sftp, scp etc.
  3. Activate Cloudflare from your Plugins page.

Once Activated

  1. Go to cloudflare.com
  2. Login with your cloudflare account. (If you don’t have a Cloudflare account first sign up for Cloudflare)
  3. Press your account name on top right corner and select “My Settings”
  4. Scroll down to “API Key” → “Global API Key” → View API Key
  5. Copy the API key
  6. Return back to WordPress Cloudflare Plugin page
  7. Enter your email address and paste your API key
  8. Press Login.

Часто задаваемые вопросы

Installation Instructions

Prerequisite

Make sure your PHP version is 5.3.10 or higher.

From your WordPress Dashboard

  1. Visit “Plugins” → Add New
  2. Search for Cloudflare
  3. Activate Cloudflare from your Plugins page.

From WordPress.org

  1. Download Cloudflare
  2. Upload the “cloudflare” directory to your “/wp-content/plugins/” directory, using ftp, sftp, scp etc.
  3. Activate Cloudflare from your Plugins page.

Once Activated

  1. Go to cloudflare.com
  2. Login with your cloudflare account. (If you don’t have a Cloudflare account first sign up for Cloudflare)
  3. Press your account name on top right corner and select “My Settings”
  4. Scroll down to “API Key” → “Global API Key” → View API Key
  5. Copy the API key
  6. Return back to WordPress Cloudflare Plugin page
  7. Enter your email address and paste your API key
  8. Press Login.
Do I need a Cloudflare account to use the plugin?

Yes, on install and activation the plugin, first time users will be asked to enter their email address (used to sign-up for an account at cloudflare.com) and their user API key. This is needed to support all the features offered by the plugin.

What settings are applied when I click «Apply Default Settings» in Cloudflare’s WordPress plugin?

You can review the recommended settings that are applied here.

Does the plugin work if I have Varnish enabled?

Yes, Cloudflare works with, and helps speed up your site even more, if you have Varnish enabled.

Отзывы

The Plugin Working Absolutely the Way it Should!

Hello Friends,

I installed the plugin 2/3 days ago and was not even working. Thus raised a ticket in the support forum for solution. Believe me or not, they responded just within a while. Most importantly they nicely guided me to solve the issue and finally it was solved in less than 24 Hrs. I see some of your reviews that it dose not work, when you purge files from the WP dashboard and other issues. But I found that it’s working smoothly as it should. I had a negative impression before using this, but not anymore. I hope and request the developers to improve the analytics section like including country map, pie charts regarding file status. Also I highly recommend the users to go through the settings of your security plugin which may create a clash before coming to a conclusion. Thanks.

Cpmpletely unusable

On IE it only shows a grey screen. On Iridium (a Chromium browser) it shopwed the screen to enter cloudflare credentials, but froze after that. The plugin became deactivated and refused to activate. Makes me wonder if this is a scam to get people’s cloudflare credentials.

it made me crazy

After I clicked the button to clear cash it started to do crazy things:

1) cash was not clear probably as I couldn’t see CSS changes, only some html/php changes;
2) my WordPress panel started working with mistakes: it either couldn’t load some pages or save settings (like changes to the menu). If it allowed making changes (like header name etc), after refreshing WordPress, you could see they didn’t apply.

After I deleted plugin I still have issues with WordPress and website:(

Bad

Set everything up for CDN exactly and precisely as instructed after joining at Cloudflare site. DNS errors galore. Took my site completely down. Set my DNS back to the originals and had to disable their plugin too via France proxy. What a mess. I should have known better.

Посмотреть все 99 отзывов

Участники и разработчики

«Cloudflare» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники:

Участники

Перевести «Cloudflare» на ваш язык.

Заинтересованы в разработке?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Журнал изменений

3.3.1 — 2017-6-29

Fixed

  • Potential bug with using by unchecked $_GET.

3.3.0 — 2017-6-29

Added

  • 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.

Changed

  • Automatic Cache Purge now purges Autoptimize by everything rather than by URL.
  • Updated IP Ranges

Fixed

  • 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.

3.2.1 — 2017-3-14

Fixed

  • Bug where accounts which had more than 20 zones would not show up correctly.

3.2.0 — 2017-3-1

Added

  • Bypass Cache By Cookie functionality.
  • HTTP/2 Server Push functionality (disabled by default).

Changed

  • Lowered the plugin size.
  • Automatic Cache Management feature includes purging taxonomies.
  • Automatic Cache Management feature supports sites which use both HTTP and HTTPS.

Fixed

  • 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.

3.1.1 — 2016-11-17

Changed

  • Moved Admin Bar behind Automatic Cache Purge toggle.

3.1.0 — 2016-11-17

Added

  • 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

  • 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

  • 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.

3.0.6 — 2016-10-6

Added

  • Added ability to toggle Development Mode.

Fixed

  • Fixed bug where active zone dropdown was not working properly.

Changed

  • Compressed resources to lower plugin size.
  • Updated Cloudflare logo.

3.0.5 — 2016-09-28

Fixed

  • Fixed bug where refactored Flexible SSL fix was causing the settings page hook not to load.

3.0.4 — 2016-09-27

Added

  • Ability for users to toggle Automatic HTTPS Rewrites (enabled by default, solves for most mixed content errors).

Fixed

  • 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.

Changed

  • Compressed assets to lower plugin size.
  • Hooks loading logic refactored to make it more simple and readable.

3.0.3 — 2016-09-21

Fixed

  • 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

3.0.2 — 2016-09-16

Fixed

  • Disabled HTTP/2 Server Push which was leading to 520 and 502 errors for some websites.

3.0.1 — 2016-09-16

Fixed

  • Fixed HTTP/2 Server Push exceeding the header limit Cloudflare has which caused 520 errors.
  • Fixed warning message in HTTP/2 Server Push.

3.0.0 — 2016-09-15

Added

  • 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

  • Removed HTTPS Protocol Rewriting
  • Removed submission of spam comments
  • Removed ability to toggle Development Mode On/Off

Changed

  • Updated user interface
  • Started to support WordPress 3.4+ instead of 2.8+ because we depend on the WordPress Options API