Unless I'm mistaken, this would apply to all versions I tested, starting from v0.993.
The "Pages View By URL" report, shows pages that are NOT part of the site being tracked, in fact they belong to a referring site.
Since the links in the report are created with the assumption that all the listed pages are part of the tracked site, we're at times lead to a 404 error.
Perhaps some kind of filtering/validation should be applied to ensure only "proper" links are listed.
Regards.
Pages views by URL
Hi Daniel,
It can't be since v0.993 because the Page Views by URL report was added in v1.2. Can you elaborate further? I haven't been able to reproduce this.
Regards,
~Chad
Pages views by URL
You're right, it was introduced in version 1.200 Beta. After all, it's normal that you know your product better than anyone else, right ? :D
The "Page Views By URL" uses the "pl_scripturl" field to create the report. On some records, the value in that field is the name of the page on the referring site. Here's an example.
Site www.bbb.com has a page named outside.htm, which contains a link pointing to "my" site tracked with MetaTraffic. When the link is clicked on, an entry in the database is created with "/outside.htm" for the "pl_scripturl" field content, along with the referrer domain and all that good stuff.
When viewing the report, "/outsite.htm" is shown. Not being part of "my" site structure, the link fails right away, for obvious reasons, namely because the "pl_scripturl" file should normally contain pages that were tracked, not the ones from the external.
This is where I'm getting a bit confused as to how that page ended up there first place.
I noticed this situation is rather specific to 2 sites linking to us. The point they have in common is that they are using frames, and on some sections of "my" site, there are frames too. To prevent a mess, I'm "breaking" the frames not created by me. This is unfortunately resulting on a page reload, which re-triggers the logging, but it doesn't happen too often, therefore it's not too bad.
Hope I made it sound a bit better than the first time. :)
Pages views by URL
Hi Daniel,
Assuming you haven't made any changes that affect the way logging works, this might be caused by the fact that the javascript logging method uses referrer data to figure out what page is being logged. In most situations, this works perfectly and eliminates having to pass both referrer and page information to the tracking script. Maybe in future versions this needs to be changed so that the javascript logging methods passes both the referrer and url information of the page being logged.
Regards,
~Chad
Pages views by URL
Chad,
I've done a lot of customization to the class file, but nothing got customized in the LogFile() function's logic, so it follows the logging logic as per version 1.3 Beta.
I'm storing the IP Addresses as numbers, and for some other fields I'm using "index numbers" instead of strings, as I'm using some kind of lookup tables to minimize disk usage.
Best regards.