stklcode/statify-blacklist
1
0
Fork 0
Code Issues Actions Releases 21 Activity

declare compatibility with WordPress 6.3

Browse Source
This commit is contained in:
Stefan Kalscheuer
2023-08-14 18:42:51 +02:00
parent 5d7a75ed31
commit 268e3933c8
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -6,7 +6,7 @@
# Statify Filter #
* Contributors: Stefan Kalscheuer
* Requires at least: 4.7
* Tested up to: 6.2
* Tested up to: 6.3
* Requires PHP: 5.5
* Stable tag: 1.6.2
* License: GPLv2 or later
@@ -62,7 +62,7 @@ The plugin is capable of handling multisite installations.
### What is blocked by default? ###
Nothing. By default, all filters are empty and disabled. They can and have to be filled by the blog administrator.
A default filter is not provided, as the plugin itself is totally neutral. If you want to filter out referer spam,
A default filter is not provided, as the plugin itself is totally neutral. If you want to filter out referer spam,
visitors from search engines, just "false" referrers from 301 redirects or you own IP address used for testing only depends on you.
### Does the filter effect user experience? ###
@@ -71,7 +71,7 @@ No. It only prevents _Statify_ from tracking, nothing more or less.
### Does live filtering impact performance? ###
Yes, but probably not noticeable. Checking a single referer string against a (usually small) list should be negligible compared to the total loading procedure.
If this still is an issue for you, consider deactivating the filter and only run the one-time-cleanup or activate the cron job.
### Is any personal data collected? ###
No. The privacy policy of _Statify_ is untouched. Data is only processed, not stored or exposed to anyone.