Cloudflare

Omschrijving

Wat deze plugin voor je kan doen

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.

Met één klik geoptimaliseerde WordPress instellingen

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 applicatie firewall (WAF) regelsets

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.

Extra functies

  • Herschrijven van header om een omleidingslus te voorkomen wanneer Universal SSL van Cloudflare is ingeschakeld

  • 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

  • Bekijk analyses zoals totale bezoekers, bespaarde bandbreedte en geblokkeerde bedreigingen

  • Ondersteuning voor HTTP2/Server Push

Schermafdrukken

Installatie

Voorwaarde

Zorg ervoor dat je PHP versie 7.2 of hoger is.

Van je WordPress dashboard

  1. Ga naar “Plugins” Nieuwe plugin toevoegen
  2. Zoeken naar Cloudflare
  3. Activeer Cloudflare vanuit je plugins pagina.

Van WordPress.org

  1. Download Cloudflare
  2. Upload the “cloudflare” directory to your “/wp-content/plugins/” directory, using ftp, sftp, scp etc.
  3. Activeer Cloudflare vanuit je plugins pagina.

Eenmaal geactiveerd

  1. Go to https://dash.cloudflare.com
  2. Log in met je cloudflare account. (Als je nog geen Cloudflare account hebt, meld je je eerst aan voor Cloudflare)
  3. Navigate to the API Tokens section of the user profile (found in the top right corner of the dashboard).
  4. Select ‘Create Token’
  5. Select the ‘WordPress’ Template
  6. Select the Account and Zone to grant the plugin access to
  7. Then select “Continue to Summary” and “Create Token”
  8. Copy your API Token
  9. Keer terug naar de WordPress Cloudflare plugin pagina
  10. Voer je e-mailadres in en plaats je API token
  11. Druk op login.

FAQ

Heb ik een Cloudflare account nodig om de plugin te gebruiken?

Yes, on install and activation of the plugin, first time users will be asked to enter their email address (used to sign-up for an account at cloudflare.com) and either an API Token or their 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.

What do I do if Cloudflare does not detect the WordPress plugin for use with APO (Automatic Platform Optimization)

APO works best when the WordPress plugin is used. We do not recommend using APO without the plugin installed. If you face issues with Cloudflare detecting the plugin then follow these steps:
1. Go to Cloudflare WordPress plugin
2. Disable APO in the card
3. Enable APO in the card (will set proper settings for APO feature)
4. Clear any server cache used via other plugins (WP Rocket being an example)
5. Verify that your origin starts serving response header “cf-edge-cache: cache,platform=wordpress”

You can read more about APO with WordPress here

Werkt de plugin als ik Varnish heb ingeschakeld?

Ja, Cloudflare werkt met en helpt je site nog sneller te versnellen, als je Varnish hebt ingeschakeld.

Beoordelingen

2 juni 2021
Hello, same problem after the update. I will switch to Stackpath. More reliable than Cloudflare. A service like Cloudflare should do a better job of maintaining your plugin. We pay Cloudflare Pro and get delivered crap that destroys the whole website? Horror club!
25 mei 2021
For those people who gives bad rating. They just don't know how to use this. If you don't know anything just use default setting, do not change anything. You will not have a problem.
4 mei 2021
The servers are slow. Cloudflare is not like before, it has changed for the worse No support Demasiados errores 520 The Pro + Argo plan, did not solve my problems My web visits dropped considerably Inadvisable.
4 mei 2021
This is an excellent plugin. Eliminates the need to login to Cloudflare unnecessarily. I find it too time-wasting to access though. To purge the cache, I have to navigate through Settings > Cloudflare > Purge Cache. I understand this is not a caching plugin in the traditional sense, but it would be a million times better if it came with a "Purge Cloudflare Cache" link in the admin bar thus eliminating the time spend waiting for the page to load just to access the plugin dashboard and click on a single button. Will give five stars when they add this feature. It's a wonderful plugin nevertheless.
Lees alle 143 beoordelingen

Bijdragers & ontwikkelaars

“Cloudflare” is open source software. De volgende personen hebben bijgedragen aan deze plugin.

Bijdragers

Vertaal “Cloudflare” naar jouw taal.

Interesse in ontwikkeling?

Bekijk de code, haal de SVN repository op, of abonneer je op het ontwikkellog via RSS.

Changelog

4.5.1 – 2021-06-03

  • Rewrite PHP 8 bootstrap files for symfony/polyfill to be PHP 7 compatible

4.5.0 – 2021-06-02

  • Document unintuitive transition_post_status WP hook behavior
  • Only purge public taxonomies while clearing any empty values from the list
  • Better handling of cases where wp_get_attachment_image_src is 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

4.4.0 – 2021-03-23

  • 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

4.3.0 – 2021-03-19

  • Sanitise sensitive HTTP header logs
  • Stop sending cfCRSFToken to remote API
  • Add warnings for incorrectly configured Automatic Platform Optimization
  • Purge posts that go from public to private
  • Purge pagination for first 3 pages

4.2.2 – 2021-03-08

  • Fix warning for file_get_contents of composer.json

4.2.1 – 2021-03-05

  • Deprecate REST dashboard analytics

4.2.0 – 2021-03-02

  • Allow configuration of Cloudflare credentials via environment variables
  • Prevent purging of cache before comments have been moderated
  • Remove unnecessary symfony/yaml dependency

4.1.0 – 2021-02-11

  • Removed development dependencies from vendor directory
  • Update CLOUDFLARE_MIN_PHP_VERSION to match the plugin requirements

4.0.0 – 2021-02-09

  • Drop support for PHP 5.6, 7.0 and 7.1

3.8.10 – 2021-01-29

  • Add Jacob to maintainers list

3.8.9 – 2021-01-14

  • Revert Add pagination purging

3.8.8 – 2021-01-13

  • Add pagination purging

3.8.7 – 2020-12-07

  • Purge taxonomy feed URLs
  • Fix changing APO settings (cf, wordpress, plugin) when running on subdomain
  • Fix setting hostname override

3.8.6 – 2020-11-19

  • Add subdomain support for APO card

3.8.5 – 2020-10-15

  • Added automatic purge cache on new comment

3.8.4 – 2020-10-13

  • Added composer’s type=wordpress-plugin for Bedrock users
  • Fixed typo in readme.txt
  • Fix modify header exception thrown during wp-cron
  1. Cloudflare Plugin= 3.8.3 – 2020-10-05 =
  • Fixed setting all APO values properly for correct dashboard rendering

3.8.2 – 2020-10-02

  • re-relase broken version, no changes

3.8.1 – 2020-10-02

  • Fixed typo in config.js(on) that resulted in warning #292
  • Check for array indicies are set before using #278

3.8.0 – 2020-10-01

  • Added APO support
  • Renamed Automatic Cache Management card to Auto Purge Content On Update

3.7.0 – 2020-09-25

  • Bump cloudflare-plugin-backend v2.3.0 and cloudflare-plugin-frontend v3.1.0 #283

3.6.0 – 2020-09-17

  • Bump cloudflare-plugin-backend #276

3.5.1 – 2020-07-02

Fixed

  • Fixed Cache Purges failing #266

3.5.0 – 2020-06-26

Fixed

  • Disable HTTP/2 Push on wp-admin pages #214
  • Fix PHP 7.4 notice #256

Added

  • 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

3.4.1 – 2019-08-29

Fixed

  • Updated list of contributors.
  • Updated tested WordPress version to latest (5.2.2).

3.4.0 – 2019-08-29

Added

  • Added support for API Token authentication.

3.3.2 – 2017-12-12

Fixed

  • Bug in cf-ip-rewrite

Added

  • Een nieuw filter toegevoegd cloudflare_purge_by_url waardoor gebruikers betere controle hebben over automatisch opgeschoonde url’s.

3.3.1 – 2017-6-29

Fixed

  • Potentiële bug met $ _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 gerelateerd aan het werken met IWP.
  • Bug waar als PHP is gecompileerd met de vlag ipv6-disable, het de site heeft gecrasht.

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

  • Ga om cache heen door cookie functionaliteit.
  • HTTP/2 Server Push functionaliteit (standaard uitgeschakeld).

Changed

  • De grootte van de plugin verlaagd.
  • De functie Automatisch cachebeheer omvat opschoning taxonomieën.
  • De functie Automatisch cachebeheer ondersteunt sites die zowel HTTP als HTTPS gebruiken.

Fixed

  • Toolbar verdwijnt uit de plugin.
  • Bug waar de spinner voor altijd aan het laden was.
  • Bug waarbij de backend fouten niet in de frontend werden getoond.
  • 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

  • Verwijderd HTTPS protocol herschrijven
  • Inzending van spam reacties verwijderd
  • De mogelijkheid om de ontwikkelmodus aan/uit te schakelen is verwijderd

Changed

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