=== Bluetrait Event Viewer (BTEV) ===
Contributors: mwdmeyer
Tags: admin, btev, events, event viewer, stats, statistics
Requires at least: 2.0.0
Tested up to: 2.2.1
Stable tag: 1.2

This plugin monitors events that occur in your wordpress install.

== Description ==

This plugin monitors events that occur in your wordpress install.

BTEV tracks the following events:

By Default:

* password_reset
* delete_user
* wp_login
* lostpassword_post
* profile_update
* add_attachment
* wp_logout
* user_register
* switch_theme
* monitors activation/deactivation of other plugins (new in Version 0.5, requires WP 2.1+)

With wp_login overrride on:

* invalid_username
* invalid_username

With wp_mail override on:

* monitors emails sent from WordPress (new in Version 0.5)

WordPress 2.0.10 or higher is recommended.

== Installation ==

1. Download
1. Unzip (zip contains btev.php)
1. Upload to wp-content/plugins
1. Activate within Wordpress Admin Panel

== Frequently Asked Questions ==

= BTEV isn't tracking failed logins. Why? =

This option needs to be enabled on the settings page (enable wp\_login overrride).

= BTEV isn't tracking emails being sent. Why? =

This option needs to be enabled on the settings page (enable wp\_mail overrride).

= BTEV isn't tracking activation/deactivation of other plugins. Why? =

This feature requires WordPress 2.1.0 or higher to work and only works if you disable/enable the plugin from the WordPress plugin page.

= What does LOCKDOWN mode do? =

The LOCKDOWN mode is designed to make it more difficult to disable BTEV.  
It might be required for extra security or if you don't want users with Administrator permissions to be able to disable the plugin.
In LOCKDOWN mode the follow options are disabled:

1. Clear Logs
1. Update Settings
1. Uninstall
1. Deactivate

This can make it more affective in logging changes that occur in your site.

= How do I enable LOCKDOWN mode? =

open btev.php and find the line (near the top) that says:

		define('BTEV_LOCKDOWN', FALSE);
and change it to:

		define('BTEV_LOCKDOWN', TRUE);
		
Remember to upload the file if you edited it locally.

= What limitations does LOCKDOWN mode have? =

1. Please be aware that LOCKDOWN mode is NOT a guarantee that BTEV will say active if you site is hacked.
1. An extra layer of security is added but there are many other ways to disabled BTEV.  
1. It is recommended that btev.php is NOT writable so that the file cannot be editted from within WordPress.
1. Please run WordPress 2.0.10 or higher for LOCKDOWN to work correctly (lower versions of WordPress may allow BTEV to be deactivated).
1. Please be aware that LOCKDOWN mode is NOT a guarantee that BTEV will say active if you site is hacked.

= BTEV gives me the following message "Your BTEV settings have been set back to the default settings. This won't happen in future upgrades." Why? =

Two possibilities:

1. You've upgraded from an old version (0.1, 0.2 or 0.3).
1. You've just installed BTEV on a WordPress 2.2 or higher blog. You can ignore this message.

This message should only be displayed once. Let me know if you keep getting it.

= BTEV has a bug and/or I want to suggest some new features. How? =

Please contact me here: http://www.bluetrait.com/contact/

== Event API ==

It is possible to add your own events to the event viewer. Simply call the following function when you want add an entry:
        
        btev_trigger_error($error_string, $error_number, __FILE__, __LINE__);
or

        btev_trigger_error($error_string, $error_number);

Argument Descriptions:

1. $error\_string: This value can be any string, it is used in the description field in the event viewer.
1. $error\_number: This value can be one of the following: E\_USER\_ERROR, E\_USER\_WARNING, E\_USER\_NOTICE. These values determine the type of message in the event viewer (Error, Warning, Notice).
1. \_\_FILE\_\_: This is the file where the event occurred, please note \_\_FILE\_\_ is a PHP predefined variable. This value determines the source.
1. \_\_LINE\_\_: This is the line where the event occurred, please note \_\_LINE\_\_ is a PHP predefined variable.

So an example would be:
        
		btev_trigger_error('Login Successful: "' . $user_login . '"', E_USER_NOTICE);

or
        
		btev_trigger_error('Login Successful: "' . $user_login . '"', E_USER_NOTICE, __FILE__, __LINE__);

NOTE: You should check to make sure that the plugin is active. The easiest way to do this is as follows:

		if (function_exists('btev_trigger_error')) {
			btev_trigger_error('Login Successful: "' . $user_login . '"', E_USER_NOTICE);
		}


== Change Log ==

KEY  
* = Bug fix  
+ = Added feature/function  
- = Something changed (only if not a bug fix)  

Change Log Start

Note: Release Date is DD/MM/YYYY :)

1.2 (28/08/2007)

*Bug fix for MySQL 3 users  
*minor fixes

1.1 (17/05/2007)

+Lockdown Mode  
+Tracks Deactivate All plugins  
+API improvements

1.0 (Released 14/05/2007)

-wp_mail function now supported under WordPress 2.2  

0.6 (Released 22/04/2007)

*bug in lostpassword_post causing it to error  

0.5 (Released 22/04/2007)

+monitor activation/deactivation of other plugins  
+track email sent from WordPress  
-small code cleanup/changes  

0.4 (Released 07/04/2007)

+++Requires WordPress 2.0.0+++

+New Events Tracked:  
        +Switching Themes  
+Started cron code (not finished)  
+wp\_nonce protection stuff.  
+uninstaller  
-removed btev\_site table. Two less queries per page now.  
-Updated plugin website link  
-Small code fixes  
-removed btev\_site database  

0.3 (Released 01/04/2007)

+Logs file uploads, Logout, Added user, able to override wp\_login  
+Able to use set\_error_handler  
*fixed Previous/Next Page links  
*stops the file from being run directly  
-cleaned up and commented some code  

0.2 (Released 30/03/2007)

+Date is filled in for an event  
+Update checker  
+More events tracked  
-Moved Event Viewer to link under dashboard  

0.1 (Released 28/03/2007)

+Public release

== Screenshots ==
1. Dashboard Recent Events
1. Settings Page