- Contributors: stklcode
- Requires at least: 4.7
- Tested up to: 6.7
- Requires PHP: 5.5
- Stable tag: 1.7.2
- License: GPLv2 or later
- License URI: https://www.gnu.org/licenses/gpl-2.0.html
Filter extension for the famous Statify WordPress plugin.
A filter extension for the famous Statify WordPress plugin.
This plugin adds customizable filters to Statify to allow blocking of referer spam or internal interactions.
Add a list of domains (for simplicity only second-level, e.g. example.com which blocks everything.example.com).
Add a list of target pages (e.g. /test/page/, /?page_id=123) that will be excluded from tracking.
Add a list of IP addresses or subnets (e.g. 192.0.2.123, 198.51.100.0/24, 2001:db8:a0b:12f0::/64).
Add a list of (partial) user agent strings to exclude (e.g. curl, my/bot, Firefox).
Filters can be applied to data stored in database after modifying filter rules or for one-time clean-up.
This plugin requires Statify to be installed. The extension has been tested with Statify up to version 1.8 The plugin is capable of handling multisite installations.
- If you experience any issues, use the support forums.
- Latest sources and development are handled on GitHub. You might contribute there or file an issue for code related bugs.
- If you want to translate this plugin you can do this on WordPress Translate.
- Author: Stefan Kalscheuer
- Special Thanks to pluginkollektiv for maintaining Statify
- If you don’t know how to install a plugin for WordPress, here’s how.
- Make sure Statify plugin is installed and active
- Goto Settings -> Statify Filter to configure the plugin
- PHP 5.5 or above
- WordPress 4.7 or above
- Statify plugin installed and activated (1.5 or above)
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, visitors from search engines, just "false" referrers from 301 redirects or you own IP address used for testing only depends on you.
No. It only prevents Statify from tracking, nothing more or less.
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.
No. The privacy policy of Statify is untouched. Data is only processed, not stored or exposed to anyone.
Yes, it is. Just select regular expressions (case-sensitive or insensitive) as matching method instead of exact or keyword match.
As you might know, Statify does not store any personal information, including IP addresses in the database. Because of this, these filters can only be applied while processing the request and not afterwards.
Yes. The plugin features subnet filters using CIDR notation. For example 198.51.100.0/24 filters all sources from 198.51.100.1 to 198.51.100.254. Same for IPv6 prefixes like 2001:db8:a0b:12f0::/64.
- Statify Filter settings page
This is a bugfix release to restore the manual cleanup function that was broken since 1.7.0.
This is a service release with minor corrections. Recommended for all users. Tested up to 6.5.
This is a service release with primarily internal rework. Tested up to 6.4 and PHP 8.3.
- Restore manual database cleanup functionality
- Fix HTML syntax for checkboxes on settings page
- Simplify some internal control structures
- Add plugin dependency to Statify
- Declared compatibility with WordPress 6.5
- Internal rework of plugin settings
- Make the IP filter list unique
- Fix options upgrade routine
- Declared compatibility with WordPress 6.4
- Minor internal code cleanup
- Declared compatibility with WordPress 6.3
- Always process IPv6 addresses lowercase
- Optimize internally used regular expression
- Minor adjustments to prevent warnings during user agent filtering with PHP 8.2
- Fix storage of user agent filter list (#28, props @BananaSquishee)
Plugin renamed to Statify Filter.
- Minor accessibility fixes on settings page
- Introduced new user agent filter (#20)
- Declared compatibility with WordPress 5.6
- Minor translation updates
- Declared compatibility with WordPress 5.5
- Fix initialization on AJAX calls for Statify 1.7 compatibility (#22)
- Minimum required WordPress version is 4.7
- Removed
load_plugin_textdomain()andDomain Pathheader - Added automatic compatibility check for WP and PHP version (#17)
- Added keyword filter mode for referer blacklist (#15)
- Layout adjustments on settings page
- Regular expression filters are validated before saving (#13)
- Fix live filter chain when regular expressions are active (#12)
- Fix issues with multisite installation (#11)
- Minor code fixes
- Relicensed to GPLv2 or later
- Fix filter hook if referer is disabled (#9)
- Fix problem with faulty IPv6 netmask in IP blacklist
- Minor changes for WP Coding Standard
- Minimum required WordPress version is 4.4 (#10)
- IP blacklist implemented (#7)
- Target page blacklist implemented (#8)
- Internal configuration restructured (upgrade on plugin activation)
- Statify hook name changed to
statify__skip_tracking(as of Statify 1.5.0)
- Continue filtering if no filter applies (#6)
- Regular expressions filtering implemented
- Fix live filter configuration check
- Switched from
in_array()to fasterisset()for referer checking - Optional cron execution implemented
- Prepared for localization
- Some security fixes
- One-time execution on database
- First release