I was with you in the fairytale maigrare idea. I thought it would be me and my husband against the world. Wow was I in for a rude awakening for a lot of years. Now, 22 years later we are happy and ONE.Raising a child is such a privilege and such a responsibility.Have a blessed day!Beth

As usual I only concentrate on Recent Pageloads since that is the log itlesf. Anything else can be fine-tuned later, as long as the logging is the same.I see 3 main issues right away:1) There is an apparent time stamp difference of about 1 minute between matching hits for servers c3 (my old ttracker) and c34 (my beta project) with c34 being earlier than c3. I placed the beta counter after the one on c3 so the difference isn't due to the beta counter loading later in the page in any case 1minutes is a long time difference for what would be at most a second.2) I have some hits that I see in the regular counter but not in the beta one and vice versa, sufficiently far apart (and different IP's and countries) so it's not a server clock difference. I wonder if it's possible some visitor have c3 blocked and other have c34 blocked in theri hosts file or other security settings, but not both.3) I seem to have more hits recorded with the beta tracker for the same IP address than with the old tracker I have a nagging feeling that to be able to test more accurately we would have to have the 2 projects on the same server, but using different scripts, so as to eliminate discrepancies due to visitors blocking one server but not the other.Another little thing is that exit links don't seem to be part of Recent Pageloads information. I can see there would be some difficulty in figuring out how to carry a blank line for all hits form one visitor for the purpose of maybe showing eventually some info for the last hit whre an external link might have been clicked and with that a different time stamp.