web site visitor stats - some third-party options
Posted: Tue Jun 15, 2010 2:37 am
these are mainly for those who don't want to use a hosted service like google analytics for whatever reason.
Slimstat http://slimstat.net/
TraceWatch http://www.tracewatch.com/
phpTrafficA http://soft.zoneo.net/phpTrafficA/index.php?l=en
these three free web stats scripts work with cms made simple. they can use *either* php include (simple edits near top of index.php) or client-side scripting. each method has its own pros and cons, so read the scripts' documentation before installing and configuring.
they are all php based and use mysql for data storage. while they could use the same database as your web site, i would recommend keeping the stats in their own. for testing purposes, i had put all three of these in the same database (but still separate from cmsms database).
if you opt for php method, the edits to index.php look something like this:
I do not know if these'll run as UDTs.. haven't had a chance to check yet.
if you are not comfortable with editing core files, or don't have a clue what i mean by that, then please choose to use the javascript method that does not require edits to core files.
My main sites run bbclone, as discussed here: http://forum.cmsmadesimple.org/index.ph ... 271.0.html --- still don't know if i'm willing to give up 3+ years of stats. I may end up running a couple of these side-by-side with bbclone until I make up my mind. I all know now is that i refuse to hand over visitor data and stats to google by using their analytics.
Note that my testing environment runs Linux, Apache 2.2.x and PHP 5.2.x (fast-cgi). While these "work for me", YMMV. If any of these take a byte out of your bits, don't blame me.
Slimstat http://slimstat.net/
TraceWatch http://www.tracewatch.com/
phpTrafficA http://soft.zoneo.net/phpTrafficA/index.php?l=en
these three free web stats scripts work with cms made simple. they can use *either* php include (simple edits near top of index.php) or client-side scripting. each method has its own pros and cons, so read the scripts' documentation before installing and configuring.
they are all php based and use mysql for data storage. while they could use the same database as your web site, i would recommend keeping the stats in their own. for testing purposes, i had put all three of these in the same database (but still separate from cmsms database).
if you opt for php method, the edits to index.php look something like this:
Code: Select all
$starttime = microtime();
clearstatcache();
// stats logging
// twatch
include_once $_SERVER[ 'DOCUMENT_ROOT' ].'/stats/twatch/api/LogRequest.php';
twatchLogRequest(true); // (true) use cookie, or () no cookie
// slimstat
@include_once( $_SERVER['DOCUMENT_ROOT'].'/stats/slim/stats_include.php' );
// phptraffica
$sid="123456"; // sid provided in phptraffica admin area
include($_SERVER[ 'DOCUMENT_ROOT' ]."/stats/traffic/write_logs.php");
// end stats loggingif you are not comfortable with editing core files, or don't have a clue what i mean by that, then please choose to use the javascript method that does not require edits to core files.
My main sites run bbclone, as discussed here: http://forum.cmsmadesimple.org/index.ph ... 271.0.html --- still don't know if i'm willing to give up 3+ years of stats. I may end up running a couple of these side-by-side with bbclone until I make up my mind. I all know now is that i refuse to hand over visitor data and stats to google by using their analytics.
Note that my testing environment runs Linux, Apache 2.2.x and PHP 5.2.x (fast-cgi). While these "work for me", YMMV. If any of these take a byte out of your bits, don't blame me.
