Download the PHP package johnsnook/yii2-visitors without Composer
On this page you can find all versions of the php package johnsnook/yii2-visitors. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download johnsnook/yii2-visitors
More information about johnsnook/yii2-visitors
Files in johnsnook/yii2-visitors
Package yii2-visitors
Short Description This extension gets the visitors ip address, logs the access and checks if it's blacklisted or whitelisted. If it's a blacklist ip address, it redirects them to a blowoff page.
License Apache-2.0
Homepage https://snooky.biz/
FAQ
Example:
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 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.
Informations about the package yii2-visitors
Yii2 - Visitors
This extension is a half security, half SEO (search engine optimization) tool for webmasters to determing
It tracks the visitor information associated with the visitor ip address and user agent (browser/OS) info, retrieves proxy and "IP info", including ISP geographical information, logs the access and checks against rules for blacklisting or whitelisting, taking appropriate action.
Includes tools for viewing, searching, filtering and graphically (Including GIS!) exploring your websites visitors.
Installation
1. Download
The preferred way to install this extension is through composer.
Either run
or add
to the require section of your composer.json file.
2. Configure
Once the extension is installed, add 'visitor' to the bootstrap section of your configuration file :
Then add the bare-minimum module definition
The routes are defined in the Module file as $urlRules. These can also be redefined in the module definition. By default, they look like this for prettyUrls:
3. Update database schema
The last thing you need to do is updating your database schema by applying the
migrations. Make sure that you have properly configured db application component
and run the following command:
Free API Keys
1) For the map to render in Visitor view, you must have a MapQuest key. Go to https://developer.mapquest.com/plan_purchase/steps/business_edition/business_edition_free/register for a free API key. If you don't have this set, the map won't display.
2) Ipinfo.io limits the number of requests each day to 100 but with a key you can make 1000 a day. Go to https://ipinfo.io/signup for a free API key If you don't have this set, you'll be limited to 100 requests per day.
3) Proxycheck.io limits the number of requests each day to 100 but with a key you can make 1000 a day. Go to https://proxycheck.io/ for a free API key If you don't have this set, you'll be limited to 100 requests per day.
4) Whatismybrowser.com is serious business, so having an API is mandatory to use their service. Go to https://developers.whatismybrowser.com/api/signup/basic for a free API key, but be prepared to provide an "app name" and website. If you don't have this set, no data beyond the basic USER_AGENT string will be captured.
Customization
So, you should be able to go to or, if you have prettyUrl enabled, and see the visitor index.
But you'll probably want to make your own views. If it was me, I'd copy the controller and views to your backend or basic controllers & views directories. But maybe there's some best practices way to do it.
I have left the layout empty so that the pages should be rendered with your layouts/theme.
When you're done getting all your keys, and deciding that there are some controller actions you're not interested in tracking, your module configuration might look something like this:
As you see, you can add a custom 'blowoff' controller action. The visitor will be passed in so you can display the name and blowoff message.
A couple of things to note here about the 'ignorables' configuration array. You can add a controller and actions to ignore as well as a whitelist of IP addresses to ignore. These will not be added to the access log.
Usage
If you want to find out information on the current user, you can get the visitor model from the module and use it like so:
Importing Existing Apache Access Logs
To kickstart your visitor data, you can import apache2 logs, as long as you (not www-data) have permissions to view them and they are in the standard apache format.
This is achieved via the very excellent parser library which can be found at https://github.com/kassner/log-parser.
By default, it assumes that your access logs are at '/etc/httpd/logs' since that's where mine are. You can specify another path as the first argument.
The second argument is for specifying which files you'd like to import. By default, it looks for access*. but a comma delimted list with no spaces can be provided instead.
To see it live, check out https://snooky.biz/visitor
Screenshots!
The main screen
Detail visitor view
Updating the name and/or message for a visitor.
The default blocked user view. (As seen from Tor)
