Closed (fixed)
Project:
Google Analytics
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
13 Dec 2007 at 21:04 UTC
Updated:
26 Feb 2019 at 20:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
buddaDo you have a link to the info on the Google Analytics site for this functionality.
Comment #2
Anonymous (not verified) commentedHere you have some info:
http://www.google.com/support/analytics/bin/answer.py?hl=en&answer=75969
http://analytics.blogspot.com/2007/11/site-search-now-available.html
http://www.epikone.com/blog/2007/10/16/ga-on-site-search-pt-1-overview-s...
Comment #3
hass commentedI tried to build this feature in GA. Patch attached against latest D6 code. I will not commit this patch until we get some good reviews and the search results are tracked for sure correctly in GA. I have not done much testing on this patch, yet. Please also check the wording in the strings.
Today i don't trust this urlencode($keys) and the $keys list very much... It should be tested with special chars, Chinese, Arabic, German Sonderzeichen, double blanks and whatever bad chars you might think about... let's try to break it! :-)
Comment #4
Anonymous (not verified) commentedWow!
I have test your patch and it works almost perfectly, but foreigns char.
If I search for: artículo, analytics show it like: art%25C3%25ADculo
Thank you!
Is it possible to have a Drupal 5.x version?
Comment #5
hass commentedCould you try again this patch, please. I missed to see url() does URL encoding themself for query params. So it was double escaped with the prior patch. This should be fixed now, but it'm not sure if this is correct inside GA JS code. It could be possible we must use drupal_to_js() here and do not use url() what is the source of this encoding.
Do you have any info how special chars are handled by google and how they must be escaped here?
Comment #6
hass commentedIf the above patch do not work, could you please try to replace the following line in googleanalytics.module line 123:
with this:
I found a discussions where some people complain about a bug in GA... they have troubles with Turkish and Polish chars, too. It could be possible that we commit the patch above and wait for google to fix this bug in ga.js... maybe you are able to test urchin.js and ga.js for a comparison!?
Comment #7
Anonymous (not verified) commentedI have tested this patch (ga.js) and yet the foreign chars are wrong, but I think it is a google problem, because in "Content Overview" it shows: /search/node?search=españa but in Site Search Terms it shows: espa%C3%B1a.
Let my try the other mod: http://drupal.org/node/200701#comment-715041 <- Updated: the same problem with foreign chars
Comment #8
hass commentedI wonder how this is possible...?!? With the code in #6 there is no URL encoding in place... this must be a GA bug...
Comment #9
hass commentedThis patch has been committed to D6 and could be back ported to D5.
Comment #10
hass commentedComment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #12
Wolfgang Reszel commentedHi,
are there special requirements for D7? I activated the feature but I still have no query parameters in the URL.
Tekl
Comment #13
hass commentedNo. Look into code, not the browser address bar.