I already had mySQL running on my server (was 4.0, so I upgraded it as the installation docs recommended), installed the mySQL/ODBC connector, and tried it. I needed to give write permisson to the metatraffic2 folder, then it upgraded. Took about 10 minutes to upgrade 41,000 records into mySQL running on the same server (dual 1 GHz Xeon).
The new interface isn't bad, holds mostly the same info as before. I wish there was a way to see what pages were viewed by each visitor, but maybe that's in the non-lite version.
Operating system data seems to have dissapeared, but all other reports look about the same as they did before.
I'll keep using v1.3 until things are a bit more finalized.
Odd thing: I was testing the upgrade on a different server and javascript errored there. It worked fine on the first server. Strange, I haven't changed my browser settings in the meantime.
2.0 lite first impressions
I just figured out why it didn't work; it was my fault (left an automatic footer on the directory and it put the footer on the .js file also).
2.0 lite first impressions
More info:
On the second install it took 15 minutes to upgrade 51300 records. Old Access db size = 23.4 MB; new Access db size = 4.4 MB
The Access version has the operating systems info okay. Maybe it's a mySQL thing?
2.0 lite first impressions
There seems to be a little confusion about where the track.js file is supposed to point: The upgrade docs say you can move everything to /metatraffic, but the track.js points to /metatraffic2. I guess that needs to be added to the upgrade section of the readme.
2.0 lite first impressions
Boy, Access is sure a lot faster than mySQL, at least when calculating a month of entry or exit pages.
2.0 lite first impressions
If you want to see how it looks, I've made a demo account on one of the servers I run:
http://research.uvsc.edu/metatraffic
Username = demo
password = demo
Running on a dual Xeon 2.8 GHz P4 server using an Access DB.
2.0 lite first impressions
Hmmm, track.asp seems to be tracking itself, even though I've not told it to do so.
Maybe it's users using track.asp?r= instead of the new track.asp?mtr= format.
Here's what I think it is: perhaps some users have a cached track.js file that is using the old tracking syntax, and when those old scirpts call track.asp they are returning the old syntax so the tracking file counts nothing but itself, having no page references to use.
2.0 lite first impressions
Regarding the MySQL speed issue, there are a few reports that run very slow under MySQL for some reason. This will hopefully be fixed in the final release.
~Chad
2.0 lite first impressions
I'm still getting about 10% of my traffic showing up as metatraffic/track.asp when using the javascript method. I thought that would be lower by now.
2.0 lite first impressions
If everything is setup correctly, you should never see hits to the track.asp script directly.
The only reason I could see that happening is because you have an old track.js file that is calling the track.asp script with the incorrect querystring variable names. All of the variables should now have an mt prefix such as mtr instead of just plain r. This was changed to avoid collisions with other apps you may have installed on your site. It could also be redirects that are using the r variable name instead of mtr. If you can do a site wide find on the files of your site, I would search for ?r= and see if you can find anything that way.
~Chad
2.0 lite first impressions
Well chad, v1.3 run fine, so I don't think it was the ?r= problem
I've included below a small section of the page URL's that caused the track.asp hits. By way of explanation, I've moved the old metatraffic over to metatraffic1, and only metatraffic 2.0 is in the metatraffic folder. I just confirmed that v2.0 files exist for track.js and track.asp.
Pages & Files ยป Urls
May 2 2004
Url Count %
31. /chemistry/horn/chem1110files/gradebook/1110final.htm 1 0.60%
32. /chemistry/horn/chem1110files/gradebook/1110quiz.htm 1 0.60%
54. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/chem1110home.html&t=2&s=1024x768&z=0.18962541359373552 1 0.60%
55. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/chem1110home.html&t=2&s=1024x768&z=0.321075998228275 1 0.60%
56. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/chem1110home.html&t=2&s=1024x768&z=0.4927859584490072 1 0.60%
57. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/chem1110home.html&t=2&s=1024x768&z=0.6717693838821248 1 0.60%
58. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/chem1110home.html&t=2&s=1024x768&z=0.6906639047419583 1 0.60%
59. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/chem1110home.html&t=2&s=1024x768&z=0.701522218585253 1 0.60%
60. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/chem1110home.html&t=2&s=1024x768&z=0.9404961503619795 1 0.60%
61. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/gradebook/gradebook.html&t=2&s=1024x768&z=0.08500099677730488 1 0.60%
62. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/gradebook/gradebook.html&t=2&s=1024x768&z=0.19283005386459145 1 0.60%
63. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/gradebook/gradebook.html&t=2&s=1024x768&z=0.5861012358784383 1 0.60%
64. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/gradebook/gradebook.html&t=2&s=1024x768&z=0.7153202241943286 1 0.60%
65. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/gradebook/gradebook.html&t=2&s=1024x768&z=0.936967916275063 1 0.60%
66. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/gradebook/gradebook.html&t=2&s=1024x768&z=0.9468660998178229 1 0.60%
67. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/chemistry/horn/chem1110files/gradebook/gradebook.html&t=2&s=1024x768&z=0.9699424557252023 1 0.60%
68. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/&t=2&s=1024x768&z=0.1001617836774879 1 0.60%
69. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/&t=2&s=1024x768&z=0.16753674431277488 1 0.60%
70. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/&t=2&s=1024x768&z=0.17754727679921228 1 0.60%
71. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/&t=2&s=1024x768&z=0.18983743904597078 1 0.60%
72. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/&t=2&s=1024x768&z=0.3761825023035866 1 0.60%
73. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/&t=2&s=1024x768&z=0.40330066238301365 1 0.60%
74. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/&t=2&s=1024x768&z=0.4665706000718615 1 0.60%
75. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/&t=2&s=1024x768&z=0.8721502257746587 1 0.60%
76. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/manuscript.htm&t=2&s=1024x768&z=0.9477685804432731 1 0.60%
77. /metatraffic/track.asp?r=http%3A//research.uvsc.edu/mcdonald/wanderweb/transcription.htm&t=2&s=1024x768&z=0.92216809875312 1 0.60%
78. /metatraffic/track.asp?r=http%3A//www.google.ca/search%3Fq%3D%2522The+Wanderer%2522%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26start%3D20%26sa%3DN&t=2&s=1024x768&z=0.032114494837414576 1 0.60%
79. /metatraffic/track.asp?r=http%3A//www.google.ca/search%3Fq%3D%2522The+Wanderer%2522%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26start%3D20%26sa%3DN&t=2&s=1024x768&z=0.19052212291545972 1 0.60%
80. /metatraffic/track.asp?r=http%3A//www.google.ca/search%3Fq%3D%2522The+Wanderer%2522%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26start%3D20%26sa%3DN&t=2&s=1024x768&z=0.2309142308588889
2.0 lite first impressions
It looks like you have some pages using the javascript tracking method that are calling the old track.js file. MetaTraffic v2.0 doesn't use those querystring variables anymore, they are from v1.3 or previous. Update your track.js file with the file from version 2.0 or check that the all your pages are calling the correct version of the track.js file.
Regards,
~Chad
2.0 lite first impressions
Hi,
I have a few questions:
1. what's the difference between the metatraffic lite and metatraffic pro?
2. Is there a price for the upgrade yet?
I've installed the demo and i am impressed. It is very professional.
The upgrade from a previous version is very good. Slow but efficient.
2.0 lite first impressions
quote:Originally posted by cdegroot
It looks like you have some pages using the javascript tracking method that are calling the old track.js file. MetaTraffic v2.0 doesn't use those querystring variables anymore, they are from v1.3 or previous. Update your track.js file with the file from version 2.0 or check that the all your pages are calling the correct version of the track.js file.
Regards,
~Chad
Well, the entries of track.asp in the log have gone away, so I still think it was cached versions of the old track.js causing the trouble. I hadn't changed anything.
Bruce