Error in Language Report

yep, you have an older version. v1.3 uses pl_language

Good day,

As far as I recall, some fields were either added or removed between the versions via the update.asp page, however I'm pretty sure none of them were simply renamed to hold the same information that was held in a differently named field of a previous version.

Perhaps some of you, who "adjusted" the scripts for some other needs, would be able to confirm.

I noticed that some fields, the pl_languageactual for instance, were dropped down the road, however I was wishing to keep a few of them around for a tad longer, so I did the changes to scripts myself to accomodate my needs.

Globally, I started to test MetaTraffic when it was at version 0.992 or something like that earlier this year and I can confirm that if people are following the instructions provided by Chad, the MetaTraffic programmer, they will not have any issue in regards to the fields names, or scripts location.

Honestly, I can almost say that 99% of the failures in MetaTraffic were caused simply because the instructions weren't followed/read properly, or important details were taken for granted. Even if I know VBScript rather well, when I'm installing something I didn't write, I take the time to read the instructions carefully. It saved me a lot of time and unjustified frustrations over the time.

Without being offensive or nasty or whatever, the basic rule is "RTFM" and it applies quite well to MetaTraffic since it didn't choke once when I followed the instructions to the letter.

Regards.

Well, believe it or not, I did RTFM. In fact, I RTFMed twice. And the problem still exists.

Try it yourself. Download v1.3 from this site, extract it, and do a search in class.asp for pl_languageactual. You'll find it twice.

I don't see how I could have an older version when I literally just downloaded it the day I wrote this message. The class.asp file contained in the download must be the wrong one.

yep, you're right. The first time I looked, I didn't see it - but I can see it now. Good call.

Good day,

To my knowledge, the "class.asp" script included in v1.3 was written in such a way to handle databases having the same structure as the one included in the zip distribution file.

If you did a fresh installation with all the files from the zip then adjusted the few variables to work with your site structure, everything shoul work just fine.

Upgrading from a previous version, requires you to run the "upgrade.asp" script on the server where the files were uploaded to, assuming you uploaded all the files from the distribution file with the exception of the new database and adjusted the paths specifications, before running "upgrade.asp" and attempting to log any new entry.

I will double-check and download the zip file as you suggested, and see if the upgrade.asp is in fact required, even on a fresh installation. Perhaps Chad changed few elements in the distribution file, although I would doubt as there is no mention of anything like that on the site.

Best regards.

quote:If you did a fresh installation with all the files from the zip then adjusted the few variables to work with your site structure, everything shoul work just fine.

That's exactly what I did. Everything does not work fine. Almost everything, just not the language report.

Does Chad monitor this forum? Seems like a simple mistake he just needs to fix.

Good day,

Sorry for being so long, I was busy on other things lately.

First thing, you're 100% right in regards to the "pl_languageactual" field.

The field was dropped from the database since v1.3. Sorry for the inconvenience, I modified my scripts and database so much that I can't really compare them accurately with the ones from the site, so I had to create another "test" environement with the supplied scripts.

Anyhow, the "pl_languageactual" field is constructed based on the "pl_language" field content. Also, "pl_languageactual" is not used in any of the generated reports, therefore its content can simply be disgarded, at least as far as the script is concerned.

So to "eliminate/hide" the error, until an official position is taken by the developper to confirm if the field will be or won't be kept with the upcoming version, you can comment out 3 lines of the "class.asp" file as distributed with the zip file.

Lines 1758-1760 calling the "GenerateLanguageData" function are the ones causing you griefs. They are as follow :

==========================================================
'If blnAnalyzeData Then
' Call GenerateLanguageData(datReportStart, datReportEnd)
'End If
==========================================================

Simply put a single quote in front of each line (as shown above) and you'll be all set and ready to go.

Therefore if the developper decide to change something, you'll still have all the original code handy to apply the changes as necessary.

I would believe Chad is still monitoring the forum although I haven't heard from him much lately. Nevertheless, the script should definitely be fixed, no question about that.

Please bare with me, I'm not part of the support team, nor the development group. I learn ASP/VBScript as I go, no more no less. I'm not an expert, but I can do coding and give a hand whenever possible. Like you, I come over here to ask/answer questions and find tips and tricks users may be willing to share.

I'm not doing web related work for living, this is only a "hobby". If I have some spare time, I take a part of it to improve my skills, otherwise it just waits till the time I can get back to it.

Regards.

Nevertheless, always Have fun!! :D

Yes, this is definately a bug.

It only occurs when you change the intAnalyzeData setting to 2 or 3 which is why it probably hasn't been identified until now. Thank you Paul for reporting this. I have posted a fix and a new version of MetaTraffic (v1.301).

Regards,
~Chad

Thanks for fixing this Chad! I downloaded and installed the new version and it works great.

Paul