Deze plugin is niet getest met de laatste 3 grotere versies van WordPress. Mogelijk wordt het niet meer onderhouden of ondersteund. Ook kunnen er compatibiliteitsproblemen ontstaan wanneer het wordt gebruikt met recentere versies van WordPress.

Cloudflare

Beschrijving

Wat deze plugin voor je kan doen

Automatische Platform Optimalisatie (APO)

Speed up your WordPress site by up to 300% with Cloudflare’s Automatic Platform Optimization (APO) plugin. APO allows Cloudflare to serve your entire WordPress site from our edge network of over 250+ data centers worldwide ensuring fast & reliable performance for your visitors no matter where they are.

Optimizing your WordPress site with multiple plugins can be overwhelming. Take your WordPress site’s performance to the next level by switching to a single plugin for CDN, intelligent caching, and other key WordPress optimizations with Cloudflare (APO). Visit our announcement blog to learn more about APO.

What makes APO different from other caching plugins?

The key differentiating factor between Cloudflare APO and other traditional page caching and CDN solutions is its ability to directly cache static HTML at Cloudflare’s edge. Every other plugin and CDN will cache your static assets (images, javascript, CSS), but none help you cache the actual content on your site (the HTML) using a massive edge network like Cloudflare’s.

APO intelligently caches your HTML pages and will automatically purge content from the cache that you update, so users will always see the latest content without compromising the performance of pages that haven’t been recently updated

Wat je krijgt met Cloudflare APO

APO is a $5 add-on with Cloudflare’s free plan and comes with an unlimited amount of subdomains. With APO you also get to leverage many of the other benefits of Cloudflare such as Free DNS, Free Automated SSL Certificates, Free DDoS Mitigation, and more. APO is free for all paid plan users so if you have Cloudflare Pro or Business already you can just turn it on. You can compare all our plans here.

Protect your WordPress site with Cloudflare’s Web Application Firewall (WAF)

Cloudflare’s WAF is available on all our paid plans and comes with built-in rulesets, specifically tailored to mitigate WordPress threats and vulnerabilities. These security rules are regularly updated by our team of experts. At the flip of a switch, you’ll have your WAF up and running without any difficult adjustments to your site. With over 26 million internet properties under our protection, you can sleep easy knowing Cloudflare has your back.

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.

Speed Up Your WordPress Site with Cloudflare APO

Ga aan de slag

Cloudflare APO instellen

If you’re currently utilizing Cloudflare’s free plan you can add APO to your plan for just $5/month. If you are on Cloudflare’s Pro Plan Cloudflare APO is already included in your subscription. We recommend you start with our APO developer documentation which includes all the information you need to get APO up and running.

How to check if APO is working
Using Uptrends you can verify if Cloudflare APO is working by checking to see if APO response headers are present. You can follow along in this video.

APO Support Resource can be found here

Aan de slag met Cloudflare SSL hier

View our Cloudflare APO blog post here

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

18 april 2024
The plugin doesn't have many options interesting unless you have a Cloudflare premium plan to use APO. That looks like to be the most interesting feature of it. It would be at least useful if it had integration with Turnstile to properly apply on website.
13 oktober 2023
I have installed this plugin and then I subscribed to the Cloudflare APO offer. This saved me a lot of money and energy because normally without cloudflare APO, i would have been forced to move my website from germany to the USA. So, now everything is working like a charm Javascript minification. I have only 1 JS file left for my entire wordpress installation. The cookies are still there and it returns the right ones. I don't know how they succeed in this black magic. this plugin is better than super cache for cloudflare because when you use super cache for cloudflare, cookies are stripped from http headers. Also, when you are logged in APO still caches it while super cache for cloudflare bypass it. You don't need to use cloudflare rules along with this plugin. If you activate APO, cloudflare applies all the settings for you. you don't need touch anything. so from what I understand, you must only use the features from cloudflare like minification and cache from cloudflare. Uninstall wp super cache or any other cache and uninstall autoptimize. Let cloudflare manage the minification and cache of your website.
24 augustus 2023
Customers on our Free plans can only submit tickets for billing, account, and registrar issues.Cloudflare support If I paid for the ‘APO’, well, I’m not on the ‘Free plan’, do you agree? Honestly, I feel completely offended. I don’t recommend Cloudflare’s ‘APO’, you’re on your own.
8 augustus 2023
This plugin is fine, it does the job. Those that give low ratings have no idea what they are doing and of course they break their websites.
Lees alle 171 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.12.7 – 2024-04-02

  • Upgrade cloudflare-plugin-frontend to v3.10.0 (#542)

4.12.6 – 2024-03-04

  • Upgrade cloudflare-plugin-frontend to v3.9.0 (#537)

4.12.5 – 2024-03-04

  • Upgrade cloudflare-plugin-frontend to v3.8.0 (#535)
  • Retrieve the WordPress domain only from the active zone (#532)

4.12.4 – 2024-01-19

  • Fix “creation of dynamic property is deprecated” notice

4.12.3 – 2024-01-04

  • Prevent usage of cloudflare_proxy action on /admin-ajax endpoint for non-Administrator users

4.12.2 – 2023-07-18

  • Revert the incorrect fix to Cloudflare Partners endpoint

4.12.1 – 2023-07-18

  • Fix Cloudflare Partners endpoint

4.12.0 – 2023-06-01

  • Updated plugin to be tested on WordPress 6.2

4.11.0 – 2022-07-27

  • Restrict access to sensitive files using .htaccess configuration.
  • Added cloudflare_use_cache hook to determine when to cache.
  • Allow arrays with url keys to be passed into cache purge requests.
  • Handle getZoneSettings not returning a key and throwing an unset array key error.

4.10.1 – 2022-06-06

  • Fix logic for ignoring cache purge operations.

4.10.0 – 2022-06-03

  • Ignore feed URLs in cache purge operations unless a cache override is in place.

4.9.1 – 2022-05-04

  • Handle empty URL arrays for purging.
  • Swap publicly_queryable for is_post_type_viewable when determining if the post is public.
  • Update always_use_https check to work with the API lacking a “value” for the key.
  • purgeCacheByRelevantURLs now accepts either an array or single ID

4.8.3 – 2022-03-22

  • When a zone has “Always Use HTTPS” enabled, only send HTTPS based URLs. HTTP URLs will never be hit and never present in the cache.

4.8.2 – 2022-03-18

  • Retag 4.8.1 with correct version in user agent

4.8.1 – 2022-03-18

  • Loosen domain check for cache purge calls to allow subdomains

4.8.0 – 2022-03-15

  • Ondersteunde WordPress versie naar 5.9 geüpdatet
  • Replace Guzzle with wp_remote_request for remote calls
  • Update cache purge logic to improve efficiency of what we send to the remote service

4.7.0 – 2021-10-28

  • Merge cloudflare-plugin-backend into Cloudflare-WordPress repository

4.6.0 – 2021-10-11

  • Make frontend use native await/async
  • Purge cache on mobile if APO Cache By Device Type

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

  • REST dashboardanalyses afschaffen

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

  • Ondersteuning voor PHP 5.6, 7.0 en 7.1 laten vervallen

3.8.10 – 2021-01-29

  • Jacob aan lijst met onderhouders toegevoegd

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
  • Opgelost instelling hostnaam overschrijven

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
  • Opgelost typfout 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

  • heruitgave van kapotte versie, geen wijzigingen

3.8.1 – 2020-10-02

  • Fixed typo in config.js(on) that resulted in warning #292
  • Controleer of array indices zijn ingesteld voordat je #278 gebruikt

3.8.0 – 2020-10-01

  • APO ondersteuning toegevoegd
  • 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

Opgelost

  • Fixed Cache Purges failing #266

3.5.0 – 2020-06-26

Opgelost

  • Schakel HTTP/2 Push op wp-admin pagina’s uit #214
  • Fix PHP 7.4 notice #256

Toegevoegd

  • 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

Opgelost

  • Lijst van bijdragers geüpdatet.
  • Updated tested WordPress version to latest (5.2.2).

3.4.0 – 2019-08-29

Toegevoegd

  • Added support for API Token authentication.

3.3.2 – 2017-12-12

Opgelost

  • Bug in cf-ip-rewrite

Toegevoegd

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

3.3.1 – 2017-6-29

Opgelost

  • Potentiële bug met $ _GET.

3.3.0 – 2017-6-29

Toegevoegd

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

Veranderd

  • Automatic Cache Purge now purges Autoptimize by everything rather than by URL.
  • IP bereiken geüpdatet

Opgelost

  • 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

Opgelost

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

3.2.0 – 2017-3-1

Toegevoegd

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

Veranderd

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

Opgelost

  • 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.
  • Problemen waarbij IE11 niet goed werkte.

3.1.1 – 2016-11-17

Veranderd

  • Moved Admin Bar behind Automatic Cache Purge toggle.

3.1.0 – 2016-11-17

Toegevoegd

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

Veranderd

  • De gebruikersinterface gewijzigd om meer op het dashboard van cloudflare.com te lijken.
  • Plugin omschrijving veranderd.
  • Uitgeschakeld om WordPress Beheerderbalk en Bewerk bericht link weer te geven om cachingproblemen te voorkomen voor gebruikers die HTML Caching gebruiken.

Opgelost

  • Fixed bug where require vendor folders was not working.
  • Fixed bug where static files were cached which caused issues updating the plugin.
  • Opgelost afhankelijkheden die problemen veroorzaakten met PHP Compatibility Checker plugin.

3.0.6 – 2016-10-6

Toegevoegd

  • De mogelijkheid om ontwikkelingsmodus te togglen toegevoegd.

Opgelost

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

Veranderd

  • Gecomprimeerde bronnen om de grootte van de plugin te verkleinen.
  • Cloudflare logo geüpdatet.

3.0.5 – 2016-09-28

Opgelost

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

3.0.4 – 2016-09-27

Toegevoegd

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

Opgelost

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

Veranderd

  • Gecomprimeerde middelen om de grootte van de plugin te verkleinen.
  • Hooks loading logic refactored to make it more simple and readable.

3.0.3 – 2016-09-21

Opgelost

  • 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

Opgelost

  • HTTP/2 Server Push uitgeschakeld, wat leidde tot 520- en 502-fouten voor sommige sites.

3.0.1 – 2016-09-16

Opgelost

  • 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

Toegevoegd

  • Added one-click application oft WordPress specific recommended settings
  • Mogelijkheid toegevoegd om de Cloudflare cache op te schonen
  • 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
  • HTTP/2 Server Push ondersteuning toegevoegd
  • Ondersteuning toegevoegd voor PHP 5.3+

Verwijderd

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

Veranderd

  • Gebruikersinterface geüpdatet
  • Started to support WordPress 3.4+ instead of 2.8+ because we depend on the WordPress Options API