Check out Yoast’s PayPal Donations Review »

Goal

To have an automatic cron process that polls Amazon S3 and/or CloudFront log files to your own server and then using logresolvemerge to combine them for processing with AWStats.

Requirements

An Amazon Web Services account where you collect your log files in a bucket. Your own dedicated server, VPS or host where you have shell access to install and configure your own solutions so you can have Python and boto installed as well as adding your own scripts. Also you should have AWStats installed and up and running.
I’ve made this setup using Ubuntu 10.04 which I run on a VPS over at Linode where I currently run a couple of projects.

Setup

I’m currently collecting logs from one CloudFront distribution and one S3 bucket which I have mapped my own CNAMEs to. Let’s call them s3.example.com and cdn.example.com. Then I have another bucket which is not public but where I store other things. So in this bucket I’ve made a folder named logs and in that folder I have a folder for each domain.
So the log prefixes for me in this case becomes
/logs/s3.example.com
/logs/cdn.example.com

Download AWS Logs

To be able to download the log files from Amazon to a local directory, check out my earlier post about downloading AWS logs with boto and Python.

Configure AWStats

Now we need to setup some AWStats configuration to prepare it for handling the AWS logs. I’ll create to configuration files for this example:
/etc/awstats/awstats.cdn.example.com.conf
/etc/awstats/awstats.s3.example.com.conf

I assume that you already know your way around configuring AWStats so I’ll focus on the specifics for AWS compability. The final log files that will be created later on for AWStats to use will be stored in /var/log/apache2/ so I point the LogFile option to that location. And then we just have to setup the LogFormat correctly. Below is the setup for S3 log files and then for CloudFront log files.

S3 AWStats LogFormat

LogFile="/var/log/apache2/s3.example.com.log"
LogFormat="%other %extra1 %time1 %host %logname %other %method %url %otherquot %code %extra2 %bytesd %other %extra3 %extra4 %refererquot %uaquot %other"

CloudFront AWStats LogFormat

LogFile="/var/log/apache2/cdn.example.com.log"
LogFormat="%time2 %cluster %bytesd %host %method %virtualname %url %code %referer %ua %query"

If you also want the CloudFront statistics to display information about the edges you can check out my post about CloudFront Edges in AWStats.

Automate everything

Now when we have all components in place, we just need to automate them so we later on can add it to cron. I’ve made a bash script which takes care of the automation. The script is not very complicated but I’ll make a quick walk through of it, so it can be modified to specific needs and setups. I added a number at the comment for each section in the script which I use as a reference in the list below.

1. A few variables used in the script. The date variable is just to collect the current date. I don’t really use this information at the moment other than appending it to a temporary directory name. But in case I want to expand on the script in the future to keep the archives around it could be handy. Then I create a variable for each log I want to process. In this example I process two logs, one S3 and one CloudFront, so I have 2 variables here containing paths to temp directories where the log files will be downloaded.
2. Here we use the boto Python script I created earlier to download all log files from Amazon to our local temp directories.
3. Now when all the log files have been downloaded, we need to combine them into a format that AWStats can understand. The first line combines the CloudFront logs. They are very straightforward so they just need to be combined into one large file and AWStats are ready to process it. Then the second line is to process the S3 log files into one large log file. S3 is a bit more tricky as it contains a few things AWStats don’t understand, so I use a regexp to remove the things that would cause AWStats some headache. I store my AWS final log files in /var/log/apache2/ which is the path I defined in the LogFile option for AWStats earlier.
4. Our log files are now downloaded and combined into the final log files that are stored in /var/log/apache2/ so I simply delete the temporary downloaded files, as I don’t need to keep them around anymore.
5. And finally we execute AWStats to update the statistics with the log files we just have processed.

#!/bin/bash
# Initial, cron script to download and merge AWS logs
# 29/11 - 2010, Johan Steen

# 1. Setup variables
date=`date +%Y-%m-%d`
cdn_folder="/tmp/log_cdn_$date/"
static_folder="/tmp/log_static_$date/"

# 2. Call the python script to download log folders from Amazon to local folders
python /home/johan/get-aws-logs.py --prefix=logs/cdn.example.com/ --local=$cdn_folder
python /home/johan/get-aws-logs.py --prefix=logs/s3.example.com/ --local=$static_folder

# 3. Merge and add the downloaded log files to the local log file
/usr/local/bin/logresolvemerge.pl ${cdn_folder}* >> /var/log/apache2/cdn.example.com.log
/usr/local/bin/logresolvemerge.pl ${static_folder}* | sed -e 's/SOAP\.\([A-Z]*\)/\1/' -e 's/REST\.\([A-Z]*\)\.[A-Z]*/\1/' >> /var/log/apache2/s3.example.com.log

# 4. Delete the downloaded log files
rm -rf $cdn_folder
rm -rf $static_folder

# 5. Update the AWStats Logs
/usr/lib/cgi-bin/awstats.pl -config=cdn.example.com -update
/usr/lib/cgi-bin/awstats.pl -config=s3.example.com -update

Cron it!

And finally, add the bash script to your cron to be run as often as you feel is appropriate for your setup.

# Process the AWS Logs at 4:43 every night
43 4 * * * root /home/johan/get-aws-logs.sh >/dev/null

And that’s it. Feel free to leave a comment if you have any questions or suggestions for improvements.

Click to enlarge

Here’s a quick breakdown of how to get the usage of your different Amazon CloudFront Edge locations within AWStats. I confess that I get some crazy pleasure from collecting statistics, still though, bandwidth usage is of interest in this case, as well as hits and that it can be interesting to see which regions most of the visitors come from.

I use the cluster functionality in AWStats to display the CloudFront Edges, as can be seen in the screenshot to the right.

I’m running AWStats on an Ubuntu server and this guide assumes that you are already collecting your CloudFront logs to a server and processes them with AWStats. If not, check out my other article dealing with that.

Let’s work with our hypothetical CloudFront distribution named cdn.example.com.

In Ubuntu AWStats stores the configurations files in /etc/awstats/ so I will assume there is a file located there named
/etc/awstats/awstats.cdn.example.com.conf
which processes the CloudFront log already.

If you have configured the above .conf file properly for CloudFront, %cluster is collected in the LogFormat which contains all information needed to be able to display the edges. So now we only need to tell AWStats to start using that information.

First in the awstats.cdn.example.com.conf, enable cluster statistics by finding ShowClusterStats=0 and change it to:
ShowClusterStats=PHB
And then continue down to the plugin section and uncomment
LoadPlugin="clusterinfo"

Now we only need to tell AWStats the name of the edges, so they make sense when checking the statistics later on. In AWStats DirData directory, create a file named clusterinfo.[your awstats config name].txt

Which in our example would be
/var/lib/awstats/clusterinfo.cdn.example.com.txt

This file shall contain a tab separated list of cluster numbers and then a text to display for each cluster. At the time of writing this article this is the complete list to paste into that file for all available CloudFront Edges. If Amazon adds more edges in the future they will have to be added at that time.

DFW3    USA: Dallas/Fort Worth, TX
EWR2    USA: Newark, NJ
IAD2    USA: Ashburn, VA
JAX1    USA: Jacksonville, FL
JFK1    USA: New York, NY
LAX1    USA: Los Angeles, CA
MIA3    USA: Miami, FL
SEA4    USA: Seattle, WA
SFO4    USA: Palo Alto, CA
STL2    USA: St. Louis, MO
AMS1    Europe: Amsterdam
DUB2    Europe: Dublin
FRA2    Europe: Frankfurt
LHR3    Europe: London
HKG1    Asia: Hong Kong
NRT4    Asia: Tokyo
SIN2    Asia: Singapore

Okay, that’s it, the next time AWStats updates the statistics output you should start getting Edge usage outputted in the Cluster section, like in the screenshot above.

To make this happen I’ve written a script in Python with the boto module that downloads all generated log files to a local folder and then deletes them from the Amazon S3 Bucket when done. The log files downloaded to the local folder can then be further processed with logresolvemerge and AWStats.

You need to have the boto module installed for this to work. Personally I’m working with Ubuntu 10.04, where boto can be easily installed by executing:

sudo apt-get install python-boto

The script takes some command line arguments that are listed in the doc header. All of these can have a default value set in the head of the get_logs class. If you set default values in the script, the command line arguments are useful if you need to override a default value on some occasions.

get-aws-logs.py

#! /usr/bin/env python
"""Download and delete log files for AWS S3 / CloudFront

Usage: python get-aws-logs.py [options]

Options:
  -b ..., --bucket=...    AWS Bucket
  -p ..., --prefix=...    AWS Key Prefix
  -a ..., --access=...    AWS Access Key ID
  -s ..., --secret=...    AWS Secret Access Key
  -l ..., --local=...     Local Download Path
  -h, --help              Show this help
  -d                      Show debugging information while parsing

Examples:
  get-aws-logs.py -b eqxlogs
  get-aws-logs.py --bucket=eqxlogs
  get-aws-logs.py -p logs/cdn.example.com/
  get-aws-logs.py --prefix=logs/cdn.example.com/

This program requires the boto module for Python to be installed.
"""

__author__ = "Johan Steen (http://www.artstorm.net/)"
__version__ = "0.5.0"
__date__ = "28 Nov 2010"

import boto
import getopt
import sys, os

_debug = 0

class get_logs:
	"""Download log files from the specified bucket and path and then delete them from the bucket.
	Uses: http://boto.s3.amazonaws.com/index.html
	"""
	# Set default values
	AWS_BUCKET_NAME = '{bucket}'
	AWS_KEY_PREFIX = '{prefix}'
	AWS_ACCESS_KEY_ID = '{access key}'
	AWS_SECRET_ACCESS_KEY = '{secret key}'
	LOCAL_PATH = '{local path}'
	# Don't change below here
	s3_conn = None
	bucket_list = None

	def __init__(self):
		s3_conn = None
		bucket_list = None

	def start(self):
		"""Connect, get file list, copy and delete the logs"""
		self.s3Connect()
		self.getList()
		self.copyFiles()

	def s3Connect(self):
		"""Creates a S3 Connection Object"""
		self.s3_conn = boto.connect_s3(self.AWS_ACCESS_KEY_ID, self.AWS_SECRET_ACCESS_KEY)

	def getList(self):
		"""Connects to the bucket and then gets a list of all keys available with the chosen prefix"""
		bucket = self.s3_conn.get_bucket(self.AWS_BUCKET_NAME)
		self.bucket_list = bucket.list(self.AWS_KEY_PREFIX)

	def copyFiles(self):
		"""Creates a local folder if not already exists and then download all keys and deletes them from the bucket"""
		# Using makedirs as it's recursive
		if not os.path.exists(self.LOCAL_PATH):
			os.makedirs(self.LOCAL_PATH)
		for key_list in self.bucket_list:
			key = str(key_list.key)
			# Get the log filename (L[-1] can be used to access the last item in a list).
			filename = key.split('/')[-1]
			# check if file exists locally, if not: download it
			if not os.path.exists(self.LOCAL_PATH+filename):
				key_list.get_contents_to_filename(self.LOCAL_PATH+filename)
				if _debug:
					print "Downloaded from bucket: "+filename
			# check so file is downloaded, if so: delete from bucket
			if os.path.exists(self.LOCAL_PATH+filename):
				key_list.delete()
				if _debug:
					print "Deleted from bucket:    "+filename

def usage():
	print __doc__

def main(argv):
	try:
		opts, args = getopt.getopt(argv, "hb:p:l:a:s:d", ["help", "bucket=", "prefix=", "local=", "access=", "secret="])
	except getopt.GetoptError:
		usage()
		sys.exit(2)
	logs = get_logs()
	for opt, arg in opts:
		if opt in ("-h", "--help"):
			usage()
			sys.exit()
		elif opt == '-d':
			global _debug
			_debug = 1
		elif opt in ("-b", "--bucket"):
			logs.AWS_BUCKET_NAME = arg
		elif opt in ("-p", "--prefix"):
			logs.AWS_KEY_PREFIX = arg
		elif opt in ("-a", "--access"):
			logs.AWS_ACCESS_KEY_ID = arg
		elif opt in ("-s", "--secret"):
			logs.AWS_SECRET_ACCESS_KEY = arg
		elif opt in ("-l", "--local"):
			logs.LOCAL_PATH = arg
	logs.start()

if __name__ == "__main__":
	main(sys.argv[1:])

Have in mind that I’m pretty new to Linux and to Python, so I bet things can be solved better, easier or in a more beautiful way than what I’ve done, as well as making it more fail safe.

Feel free to suggest improvements that can be made to the code.

I used to use my own web server and FTP to host the images, but nowadays I’m using the excellent free service Dropbox for this, and for many of my other file sharing needs. If you don’t already have a Dropbox account, you can use the previous link to signup. It’s a referral link which gives you (and me) an extra 250 MB of storage for free in addition to the original 2 GB you get.

When I’ve a screenshot in my Clipboard I want a button in DOpus to perform the following:

1. Paste it to my Public Dropbox folder as a high quality JPEG.
2. Give the image a name of my choice.
3. Copy the URL to the image to my Clipboard, ready to be pasted into Messenger, Skype, a forum etc.

Paste to Dropbox button in DOpus

I’ve my screen grab application mapped to the keyboard shortcut Win+S to, so I can at any time drag out a rectangle on screen that goes into the Clipboard and then run the function in DOpus to be able to share it immediately.

Here’s the script I’ve added to my button:

@set url = http://dl.dropbox.com/u/<dropbox id>/
@set dropbox = E:\User Storage\Dropbox\Public\
@set imagequality = 90
@set imagefile = {dlgstring|Set image name (without extension)}

Clipboard PASTE jpg:{$imagequality} AS="{$dropbox}{$imagefile}.jpg"

Clipboard SET {$url}{$imagefile}.jpg

@confirm Done! URL copied to clipboard.|Okidoki

When you press the button, you get asked for a name to give the file, and then it copies it to your dropbox, and stores the URL in the clipboard and gives you a confirmation. Change the @set url line to use your own dropbox id so the URL stored in the clipboard is correct, and also change the path in @set dropbox to your public dropbox folder.

If you rather prefer to use your own FTP and web server instead of Dropbox, here’s my old button script that I used before I switched to Dropbox, feel free to use that as a starting point to tweak to fit your needs.

@set url = http://your.domain.address/
@set tmpfolder = E:\User Storage\Downloads\
@set imagefile = {dlgstring|Set image name (without extension)}

Clipboard PASTE jpg:90 AS="{$tmpfolder}{$imagefile}.jpg"

Copy FILE="{$tmpfolder}{$imagefile}.jpg" TO=@your-ftp-site-dopus-profile-name

Delete FILE="{$tmpfolder}{$imagefile}.jpg" QUIET

Clipboard SET {$url}{$imagefile}.jpg

@confirm Done! URL copied to clipboard.|Okidoki

Enjoy and have some fun with the precious time saved for each image shared.
Cheers!

Unfortunately at this time, SyncBack does not support using a service like Amazon S3 for backup. Not to worry though, after some research I found a solution for SyncBack by using Windows’ built-in PowerShell together with the awesome CloudBerry Explorer which comes with a PowerShell Snap-In.

I’m very happy I found CloudBerry Explorer, as it seems to support all new features introduced by Amazon S3 as soon as they are available, and I’ll probably start using it for all my S3 managing needs and not only to sync my backups.

Anyway, let’s get started with how to set this up.

PowerShell Setup

This was more or less the first time I used the new PowerShell in Windows, and I quickly noticed that it didn’t execute my script files. By default PowerShell’s script execution policy is set to restricted, so I started by changing this policy to RemoteSigned, which means that scripts needs to be signed to be executed except those I write myself. Perfect, just what I wanted.
Change the execution policy in PowerShell with this command:

Set-ExecutionPolicy RemoteSigned

See the screenshot below for how to check the current policy and changing it.

CloudBerry Explorer PowerShell Script

All available commands and parameters as well as a few examples for the CloudBerry Explorer PowerShell Snap-In can be found here >>.

Copy the script below to a local file and name it something like SyncFolderWithAmazonS3.ps1

# Setup
$key = "<your access key>"
$secret = "<your secret key>"
$s3bucket = "<bucket>/<path>"
$localsource = "<local path to sync>"

# Add the CloudBerry SnapIn to the Console
Add-PSSnapin CloudBerryLab.Explorer.PSSnapIn

# Connect to the Amazon S3 Account and select the path
$s3 = Get-CloudS3Connection -Key $key -Secret $secret
$target = $s3 | Select-CloudFolder -Path $s3bucket

#Connect to local file system and select local folder
$local = Get-CloudFileSystemConnection
$source = $local | Select-CloudFolder $localsource

# Perform the Syncing
$source | Copy-CloudSyncFolders $target -DeleteOnTarget -IncludeSubFolders

It’s pretty straightforward, change the values in the first section to your Amazon keys, your backup bucket name and path as well as your local folder to sync to Amazon S3.

Then run it from the command prompt in PowerShell to make sure it works as expected and that the CloudBerry Explorer PowerShell Snap-In is properly installed.

SyncBack Setup

In SyncBack I’ve created a profile which I’ve called ‘Backup to Amazon S3′. You can make an infinite number of different variations on the actual backup settings of this profile depending on how you like and prefer to make backups. But the core thing to setup is to go into your profile for Amazon S3 backups and switch to expert mode. In the option for ‘Programs – Before’, go to the sub page for ‘After’ and set PowerShell with the CloudBerry Explorer script to be run after the profile has finished.

Click to enlarge

The command line to add to the ‘Run after profile’ field:

PowerShell.exe &'E:\Web\Server\SyncFolderWithAmazonS3.ps1'

Personally I’ve set my Amazon S3 Backup Profile to run once every night. All my important working files are backed up to a folder on my local backup drive, using a mirror backup mode to not leave deleted files in the sync folder. This folder is also the folder I’ve set as the $localsource in my SyncFolderWithAmazonS3.ps1 CloudBerry Explorer PowerShell script. So after the files in the local backup folder has been updated and are in sync with my system, the profile executes the script to sync all the changes to my Amazon S3 bucket as well.

This works great and I just love how secure I feel with my backups these days if something should happen locally.

Cheers!

I’m also loving the new Custom Post Types, and on one of my sites, I have setup a few different post types. On the frontend I have different widths for posts, pages and my new WordPress 3.0 custom post type ‘portfolio. I wanted to reflect the different widths in my admin editor style sheet as well. The posts are the narrowest ones, while pages are wider and my custom post type portfolio is the widest, so I have made 3 style sheets which are pretty much the same, with the exception of the

html .mceContentBody {
	max-width:640px;
}

which sets the width for the editor. My style sheets are named; editor-style-post.css, editor-style-page.css and editor-style-portfolio.css.
To be able to decide which post type I’m editing I check post_type in the $current_screen variable and then set the correct CSS according to that.

The code I end up with adding to my functions.php file looks something like this.

function my_editor_style() {
	global $current_screen;
	switch ($current_screen->post_type) {
	case 'post':
		add_editor_style('editor-style-post.css');
		break;
	case 'page':
		add_editor_style('editor-style-page.css');
		break;
	case 'portfolio':
		add_editor_style('editor-style-portfolio.css');
		break;
	}
}
add_action( 'admin_head', 'my_editor_style' );

By expanding on the code above you can continue defining stylesheets for any custom post types you might end up with in WordPress 3.0.

That’s it folks, cheers!

PayPal Widget Setup

I just released a new version of PayPal Donations, version 1.2.

New in this version is the inclusion of a sidebar Widget for the PayPal button. I’m using the new WordPress 2.8 API for the Widget, so it’s only available if you run the plugin on WordPress 2.8 or newer.

In the widget admin you can specify a descriptive text as well as overrides for Purpose and Reference if you wish.

Enjoy and cheers!

The Issues

• The url to the AJAX loader symbol is hardcoded into the plugin, so if you don’t use a white background in your theme the loading symbol looks quite ugly. If you replace the default icon with your own it gets overwritten on each plugin update.
• The javascripts for the plugin gets loaded on every single page of the site no matter if the plugin is used or not on that page, which adds unnecessary loading time where it’s not needed.
• The path to the stylesheet for the validation and submit messages is also hardcoded into the plugin, and if you edit the stylesheet to fit your theme, the edits gets lost on each update, and you have to reupload your custom stylesheet for the plugin.

The Solutions

So to not have to edit the plugin file, I added a few overrides in my theme’s functions.php file instead to change the behaviour of the plugin where needed.

Let’s start by taking care of the AJAX loading symbol. To change the path to the gif file I use a regular expression to update the url.

// Change the URL to the ajax-loader image
function change_wpcf7_ajax_loader($content) {
	if ( is_page('contact') ) {
		$string = $content;
		$pattern = '/(<img class="ajax-loader" style="visibility: hidden;" alt="ajax loader" src=")(.*)(" \/>)/i';
		$replacement = "$1".get_template_directory_uri()."/images/ajax-loader.gif$3";
		$content =  preg_replace($pattern, $replacement, $string);
	}
	return $content;
}
add_filter( 'the_content', 'change_wpcf7_ajax_loader', 100 );

This function filters the content, tracks down the AJAX loader tag and replaces the URL with a path to the current {theme folder}/images/ajax-loader.gif. So you can have your own custom AJAX loader stored in your theme folder instead, untouched on each plugin update. I added the if( is_page(contact) ) {} to the function to make sure the filter only runs on pages where needed, to not waste CPU cycles on pages where the plugin is not used. Contact is the name of the page where I use the form, change it to the name, or names of pages where you use the plugin.

Okay, now let’s see take care of the script loading on each page of the site.

// Add the Contact Form 7 scripts on selected pages
function add_wpcf7_scripts() {
	if ( is_page('contact') )
		wpcf7_enqueue_scripts();
}
if ( ! is_admin() && WPCF7_LOAD_JS )
	remove_action( 'init', 'wpcf7_enqueue_scripts' );
add_action( 'wp', 'add_wpcf7_scripts' );

This function removes the call to add the Contact Form 7 scripts on every page, and then adds back the call where needed, in my case I add them back at the page called contact, but change that to whatever works for you.

And finally, let’s deal with the stylesheet.

function remove_wpcf7_stylesheet() {
	remove_action( 'wp_head', 'wpcf7_wp_head' );
}
add_action( 'init' , 'remove_wpcf7_stylesheet' );

Here I actually remove the call to the stylesheet completely. As I have made my own style that fits my theme, I don’t use the default stylings. If you use the default stylings but just want it to load where needed, you could use an is_page condition like on the loading of the scripts. I could have put the Contact Form 7 Stylesheet in the theme folder using the same technique as on the AJAX loader to leave it untouched on a plugin update, but as I like to keep the calls to external files to a minimum to have the site load as fast as possible, I just put the WPCF7 CSS styles directly in my default style.css of my theme instead and got rid of the plugin stylesheet loading.

The Final Code

And here is what the final code looks like, ready to get pasted into the functions.php file in the theme you are using.

/**
 * Functions:	Optimize and style Contact Form 7 - WPCF7
 *
 */
// Remove the default Contact Form 7 Stylesheet
function remove_wpcf7_stylesheet() {
	remove_action( 'wp_head', 'wpcf7_wp_head' );
}

// Add the Contact Form 7 scripts on selected pages
function add_wpcf7_scripts() {
	if ( is_page('contact') )
		wpcf7_enqueue_scripts();
}

// Change the URL to the ajax-loader image
function change_wpcf7_ajax_loader($content) {
	if ( is_page('contact') ) {
		$string = $content;
		$pattern = '/(<img class="ajax-loader" style="visibility: hidden;" alt="ajax loader" src=")(.*)(" \/>)/i';
		$replacement = "$1".get_template_directory_uri()."/images/ajax-loader.gif$3";
		$content =  preg_replace($pattern, $replacement, $string);
	}
	return $content;
}

// If the Contact Form 7 Exists, do the tweaks
if ( function_exists('wpcf7_contact_form') ) {
	if ( ! is_admin() && WPCF7_LOAD_JS )
		remove_action( 'init', 'wpcf7_enqueue_scripts' );

	add_action( 'wp', 'add_wpcf7_scripts' );
	add_action( 'init' , 'remove_wpcf7_stylesheet' );
	add_filter( 'the_content', 'change_wpcf7_ajax_loader', 100 );
}

This tweak was published when Contact Form 7 was at version 1.10, and should continue to work just fine as long as no major changes is made to the inner workings of the plugin.

This led me to think that it would be real handy to get the log messages sent out by email as well, so you don’t risk to have a problem going on at the site unnoticed for days or even weeks.

So I wrote an extension to the native Log class in CodeIgniter which adds this functionality. Below is the code for MY_Log.php which extends the CI_Log class. MY_Log calls the native Log functions so the log file still gets generated, and if a log message was executed it also gets sent out by email afterward.

Change the email address in the code to the one you want to receive the log messages to, and then save the file in your application/libraries/ folder as MY_Log.php. This assumes that your Class Extension Prefix is set to MY_ in your config file.

I hope some of you find this class extension useful, and feel free to improve upon it. Cheers!

<?php
/**
 * MY_Log Class
 *
 * This library extends the native Log library.
 * It adds the function to have the log messages being emailed when they have been outputted to the log file.
 *
 * @package		CodeIgniter
 * @subpackage		Libraries
 * @category		Logging
 * @author		Johan Steen
 * @link		http://wpstorm.net/
 */
class MY_Log extends CI_Log {
	/**
	 * Constructor
	 *
	 * @access	public
	 */
	function MY_Log()
	{
		parent::CI_Log();
	}

	/**
	 * Write Log File
	 *
	 * Calls the native write_log() method and then sends an email if a log message was generated.
	 *
	 * @access	public
	 * @param	string	the error level
	 * @param	string	the error message
	 * @param	bool	whether the error is a native PHP error
	 * @return	bool
	 */
	function write_log($level = 'error', $msg, $php_error = FALSE)
	{
		$result = parent::write_log($level, $msg, $php_error);

		if ($result == TRUE && strtoupper($level) == 'ERROR') {
			$message = "An error occurred: \n\n";
			$message .= $level.' - '.date($this->_date_fmt). ' --> '.$msg."\n";

			$to = 'someone@example.com';
			$subject = 'An error has occured';
			$headers = 'From: Example Name <no-reply@example.com>' . "\r\n";
			$headers .= 'Content-type: text/plain; charset=utf-8\r\n';

			mail($to, $subject, $message, $headers);
		}
		return $result;
	}
}
?>