=== WP Smart Analytics ===
Contributors: vinodsebastian
Tags: wp smart analytics, visitor, security, ban, behavior, analytics, actions, ip, logs, statistics, no database
Requires at least: 3.9.0
Tested up to: 5.7.2
Requires PHP: 5.3.0
Stable tag: 1.1.2
License: GPLv3
License URI: https://www.gnu.org/licenses/gpl-3.0.html

WP Smart Analytics provides insights into visitor analytics provides security to your wordpress installation. This 'Plugin' uses only Flat files.

== Description ==

WP Smart Analytics provides insights into visitor analytics provides security to your wordpress installation from the comfort of your WordPress dashboard. This plugin does not use database. The data required is stored locally as encrypted text files along with .htaccess to prevent unauthorized access.

Tag cloud provides you an overview of the various tags with their frequency in descending order. Clicking on an 'IP' or a tag would filter the visitor logs thereby helping the administrator take decisions. Ban tagging would generate security texts for updating '.htaccess' manually. Thus this plugin can be used for lead analytics, and security maintenance.

The plugin offers readonly and manage roles based on user role. A shortcode [wpsa_log] is also provided to display visitor logs. We strongly suggest to keep it hidden from public.

Please use the plugin if and only if it meets required statutory and regulatory compliances applicable in your jurisdiction.

More features are coming.

= Website =
http://www.vinodsebastian.com/plugins#wpsmartanalytics

= Documentation =
http://www.vinodsebastian.com/plugins#wpsmartanalytics

= Shortcode Demo =
http://vinodsebastian.com/demo/wpsa/

== Installation ==

1. Upload 'wp-smart-analytics' to the '/wp-content/plugins/' directory.
2. Activate the 'Plugin' through the 'Plugins' menu in WordPress.
3. On activation 'wp-smart-analytics' directory is created inside '/wp-content/uploads/' folder to store encrypted logs and meta data.
4. Files and directories inside it are secured from unauthorized access but please do validate. 

== Frequently Asked Questions ==
Q. Why is the plugin asking for ipstack.com API key?
A. IP stack has got a free API service used to obtain locality of an IP address. The plugin uses this. We are not affliated with the service provider.

Q. Is ipstack.com API key a must?
A. No. The plugin gracefully degrades without it. Unfortunately locality won't be logged.

Q. What is 'Do not log' in settings?
A. File paths containing any one of the comma seperated texts corresponding to 'Do not log' in settings panel are not logged. For example, assume you want to ignore logging a specific folder. In that case add it to the comma seperated ignore list.

Q. I want to reverse certain banned 'IP's?
A. You can update the ban texts by altering meta tags from settings panel and saving. Please be careful.

Q. Can I use [wpsa_log] shortcode anywhere?
A. A shortcode [wpsa_log] is also provided to display visitor logs. We strongly suggest to keep it hidden from public.

More questions, mail me at business[at]vinodsebastian.com
I will try to respond promptly.

== Screenshots ==

1. Administration screen.
2. Administration screen for mobile.
3. Filtered by cloud tag named Visitor_22.
4. Add a tag by clicking on Visitor (man with football icon).
5. How to ban an 'IP'.
6. 403 Access Forbidden.
7. Post with [wpsa_log] shortcode.

== Upgrade Notice ==

The Plugin has a definite upgrade plan.

== Changelog ==

= 1.0.0 =
* WP Smart Analytics is launched.

= 1.0.1 =
* Logs in reverse chronological order.
* Ability to tag IPs.
* Ability to ban IPs.
* Tag cloud.
* Minor bugs removed.

= 1.0.2 =
* Increased security.

= 1.0.3 =
* Tag cloud to display in descending order of frequency only above a threshold of 3.
* Ability to filter by clicking on cloud tag.
* Ajax loading icon.

= 1.0.4 =
* Aligned with WordPress theme.
* Aligned with WordPress internationalization.
* A Managed version for Administrators and Read Only version for Other Roles provided.
* Shortcode [wpsa_log] added for website WordPress frontend.

= 1.1.0 =
* Breaking change so please save old logs manually if required.
* Major revamp of code.
* Improved user experience.
* Enhanced security with logs being encrypted.
* Location of logs moved from plugin folder so that logs are not lost on future plugin updates.
* Introduced usage of cookies.
* Captures duration and referrer.
* Added settings section with many features.
* Enhanced functionality.

= 1.1.1 =
* Location API bug fixed. API key needs to be resaved from settings.

= 1.1.2 =
* Major bug due to typo fixed.