Download the PHP package stklcode/statify-blacklist without Composer

On this page you can find all versions of the php package stklcode/statify-blacklist. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package statify-blacklist

CI Quality Gate Status Packagist Version License

Statify Filter

Filter extension for the famous Statify WordPress plugin.

Description

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.

Features

Referer Filter

Add a list of domains (for simplicity only second-level, e.g. example.com which blocks everything.example.com).

Target Filter

Add a list of target pages (e.g. /test/page/, _/?pageid=123) that will be excluded from tracking.

IP Filter

Add a list of IP addresses or subnets (e.g. 192.0.2.123, 198.51.100.0/24, 2001:db8:a0b:12f0::/64).

User Agent Filter

Add a list of (partial) user agent strings to exclude (e.g. curl, my/bot, Firefox).

CleanUp Database

Filters can be applied to data stored in database after modifying filter rules or for one-time clean-up.

Compatibility

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.

Support & Contributions

Credits

Installation

Requirements

Frequently Asked Questions

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, 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?

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.

Are regular expression filters possible?

Yes, it is. Just select regular expressions (case-sensitive or insensitive) as matching method instead of exact or keyword match.

Why is IP and User Agent filtering only available as live filter?

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.

Can whole IP subnet be blocked?

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.

Screenshots

  1. Statify Filter settings page

Upgrade Notice

1.7.2

This is a bugfix release to restore the manual cleanup function that was broken since 1.7.0.

1.7.1

This is a service release with minor corrections. Recommended for all users. Tested up to 6.5.

1.7.0

This is a service release with primarily internal rework. Tested up to 6.4 and PHP 8.3.

Changelog

1.7.2 / 06.06.2024

1.7.1 / 24.03.2024

1.7.0 / 11.03.2024

1.6.3 / 14.08.2023

1.6.2 / 25.02.2023

1.6.1 / 28.05.2021

1.6.0 / 09.12.2020

Plugin renamed to Statify Filter.

1.5.2 / 03.09.2020

1.5.1 / 20.05.2020

1.5.0 / 13.05.2020

1.4.4 / 19.05.2018

1.4.3 / 09.01.2018

1.4.2 / 12.11.2017

1.4.1 / 16.07.2017

1.4.0 / 10.06.2017

1.3.1 / 09.12.2016

1.3.0 / 17.10.2016

1.2.1 / 10.10.2016

1.2.0 / 29.08.2016

1.1.2 / 17.08.2016

1.1.1 / 16.08.2016

1.1.0 / 15.08.2016

1.0.0 / 14.08.2016

All versions of statify-blacklist with dependencies

PHP Build Version
Package Version
Requires php Version >=5.5
composer/installers Version ~v1.12|~v2.2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package stklcode/statify-blacklist contains the following files

Loading the files please wait ....