Good day,
I'm actually doing some normalization, mainly to minimize database disk space requirements for the database.
When looking closely at the code, we see 3 logging methods having their corresponding "logtypes", which are the ASP "way" via the #include (0), File downloads (1), and Javascript (2).
When using the ASP method (0), the page being "tracked" is the page on which the include is located and identified with the server variable "SCRIPT_NAME". So far so good.
The second method, Downloads (1), seems to log the scriptname passed via the "r" parameter. I dunno for sure if this is the url of rhe page or the url of the file being downloaded, as I'm not using this feature, at least for the moment being.
Where the things are getting confusing, is with the Javascript Method (2). The scriptname field, which normally would be the page where the call to the javascript is done, is in fact the sciptname of the referrer, which I tend to believe is wrong. We're interested at logging accesses to the different pages of the "current site", so do we really care about the referrer scriptname ?
In fact, the referrer's url is stored in the DB, under "pl_referrerurl", so I don't think storing the related scriptname in the "pl_scriptname" field is appropriate, as we're dealing with 2 different sources here, aren't we ?
So, is this me who doesn't understand what is happening or what should happen, or have we overlooked at something inadvertly ?
The above is based on the code for version 1.3, but may apply to earliest versions as well.
Suggestions/comments/ideas are more than welcome.
Regards.
Information consistancy.
Hi Daniel,
When logging with the javascript method, it works different then the other 2 logging methods. The page being logged is not passed to the tracking script, only the referrer is. This is because the tracking script can figure what the url of the page being logged is by grabbing its referrer. The page name doesn't need to be passed, so I decided not include it.
Regards,
~Chad