Two bugs - Search engine tracking - WAP2 logging and general bug..

[Alyx]

I (think I've) found two bugs in SMF 2.0 RC1.2's Search Engine tracking.

I'm using the "Very High" setting, to see individual page views.

Bug #1:
When Google (and.. probably any other search engine) visits WAP2 (index.php?wap2) pages in the SE Tracker sometimes it shows the pages it visits similar to the following:

Code Select Expand

a:5:{s:5:"topic";s:0:"";s:4:"wap2";s:0:"";s:5:"board";s:0:"";s:6:"action";s:0:"";s:10:"USER_AGENT";s:169:"SAMSUNG-SGH-E250/1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 UP.Browser/6.2.3.3.c.1.101 (GUI) MMP/2.0 (compatible; Googlebot-Mobile/2.1; +http://www.

It seems to just record some internal stuff, rather than the page it's actually visited.. I'd assume WAP2 views are handled slightly differently to the normal pages.

I'm not entirely sure what pages produce the errors, because sometimes things manage to slip through..

Bug #2:
When (as an example, although it occurs with other agents) Googlebot-Mobile visits, it is recorded just as though only "Googlebot" had visited. The same happens to Googlebot-Image, it's just recorded as "Google" (the name set for "Googlebot")..

Hope I managed to explain well enough for it to be helpful

[karlbenson]

I believe Bug 2 has already been fixed in the svn.
In future we sorted the spiders in reverse, so googlebot mobile will be detected before googlebot.

Not sure about Bug 1 as yet.
If i'm reading it correctly, it sounds like a bug.  Haven't yet confirmed.

[Joshua Dickerson]

Do these issues still exist?