Releases: crowdsecurity/cs-wordpress-bouncer
v1.0.7
- test(wordpress 5.8): Add compatibility test for WordPress 5.8
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
- Update the package metadata to indicate to the Wordpress Marketplace that this plugin has been successuly tested with the latest Wordpress 5.7 release (PHP 7.3, 7.4, 8.0)
- Update E2E tests dependencies
- Fix a problem when running dev environment on linux hosts : the "enable_ipv6" docker compose attribute was no more accepted since in docker compose v3.
v1.0.0
Standalone mode
We added the standalone mode, an option allowing the PHP engine to no longer have to load the WordPress core during the bouncing stage.
This feature helps reduce resource consumption in the event of heavy traffic from malicious users. On the other hand, the option allows to bounce all the PHP scripts present in the project, and no longer only when wp-load.php is loaded.
To be able to apply this mode, the webmaster has to set the auto_prepend_file PHP flag to the script we provide.
Debug mode
Now the WP user can enable the debug mode directly from the CrowdSec advanced settings panel. A more verbose will be written when this flag is enabled.
Adding WordPress 5.7 support
This plugin is now supported by the latest WordPress release 5.7.
Adding PHP 8.0 support
This plugin is now tested with PHP 8.0 (WP 5.7)
Plugin options are now stored in a flat file
Now the options are stored in a flat file, this is a step to prepare the standalone mode.
Prevent proxies from caching the wall pages
When the WP is covered by a reverse proxy (like a CDN, Varnish, Nginx reverse proxy etc), the wall page (ban or catpcha) is no more cached.
Fix incompatibilities with other plugin (session_start)
When another plugin uses PHP sessions, using the two plugins together trigger a PHP notice (session_start already sent). This has been fixes.
Update composer dependencies
Many composer deps has been upgraded.