Releases: crowdsecurity/cs-wordpress-bouncer
Releases · crowdsecurity/cs-wordpress-bouncer
1.10.0
Changed
- Modify ban and captcha walls templating for W3C validity
- Do not use cache tags for
memcached
as it is discouraged - Replace unauthorized chars by underscore
_
in cache keys
Added
- Add tests for WordPress 6.1
1.9.0
Added
- Add TLS authentication feature
Fixed
- Fix false negative connection test from admin when
trust_ip_forward_array
setting is not in database
1.8.1
Fixed
- Set missing default values in settings
1.8.0
Added
- Add
use_curl
configuration: should be used ifallow_url_fopen
is disabled andcurl
is available - Add
disable_prod_log
configuration
Changed
- Change log path to
wp-content/plugins/crowdsec/logs
- By default, the
bouncing_level
setting isbouncing_disabled
(instead ofnormal_bouncing
)
1.7.0
Added
- Add geolocation feature
Changed
- Do not throw exception if empty api url as it is the default after a fresh install and activation
- Changed default value for some boolean value as WordPress config are always string
1.6.0
Added
- Add "Test bouncing" action in settings view
1.5.1
Added
- Add tests for WordPress 6.0
1.5.0
Added
- Add configuration to set captcha flow cache lifetime
Changed
- Use cache instead of session to store some captcha flow values
Fixed
- Fix wrong deleted decisions count during cache refresh
1.4.3
Fixed
- Do not bounce if headers are already sent
1.4.2
Added
- Add WordPress debug log if bouncer logger is not ready