..

As easy as it is to plug in Googles Analytics JS code into the base of your website, you still wont get a good idea of what spiders are crawling your site, and how often, as well as a few other limitations / omitted abilities.

That is a simple way to use your own custom code to log what’s happening on your site. No fancy graphs here. The fact that it’s completely server-side cleans up the front end code and simplifies the loading of said HTML, with no external references on each page load. Sending it to a database would be one of the first desirable improvements.

NOTE: Be wary of using a single log file that isn’t purged, its fine for a few lines, but once it reaches a few thousand PHP needs to cycle right through it which drastically reduces performance, and pageload.

The following line creates a new file each day, which depending on how many pageloads are expected, should be fine…

$myFile =  "hide_melogs/".date(dMy).".txt";

http://blog.phil-taylor.com/2006/05/08/troubled-times-for-mambo-open-source-cms/

I’ve been meaning for a while to get my head around these… and why certain functions / formating cause errors in Citrix…

The function the browser looks for is:

function FindProxyForURL(url, host)
{
return "DIRECT";
}

“Return DIRECT” tells the browser to look locally for the address.

return “PROXY 192.168.0.254:80″ tells the browser to send the request to the specified proxy.

Handy free view of Optus AS7474 National routes

telnet route-views.optus.net.au

These should save some time… Common Linux Commands

If you want to turn it off, put

ini_set("url_rewriter.tags","");

immediately before

session_start();

Over at Sitepoint they have launched (a while ago) a very useful HTML and CSS reference.

JavaScript is coming soon too (doesn’t say when unfortunately) which I will be looking forward to most of all.

Good work guys, keep em coming