Closed (fixed)
Project:
Google Analytics
Version:
5.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Dec 2007 at 20:03 UTC
Updated:
23 Feb 2008 at 20:31 UTC
Jump to comment: Most recent
Comments
Comment #1
buddaHow does the segmentation and codesnippet stuff work with this new patch? It looks like you've not supported it in the new version?
Comment #2
buddaI've worked up some code based on the new Beta, it's in CVS now. However i've not had a chance to check it works - specifically with user segmentation and/or code snippets.
Please try and post here any problems.
Comment #3
buddaComment #4
Anonymous (not verified) commentedGoogle has published a pdf guide to migrate from urchin.js to ga.js: http://www.google.com/analytics/GATCmigrationguide.pdf, a Guide to install the new tracking code: http://www.google.com/analytics/InstallingGATrackingCode.pdf and a analytics developer site: http://code.google.com/apis/analytics/
Hope this help
Comment #5
davidburnsSorry budda, still getting used to submitting patches. I did a patch from what I had installed locally rather then what you had in cvs.
Thanks for updating.
Comment #6
hass commented1. The committed patch break the download tracker. Aside the noscript tags should be removed!
2. and why are you adding
<!-- ... -->to the second line?3. Code Style is an issue here.
4. SSL example from the docs
5. local cached copy is not implemented
6. googleanalytics_cron() downloads the wrong file to cache
7. Text constants need to be altered to reflect ga.js.
Comment #7
hass commented#1 and #2 have some open questions.
D6: See http://drupal.org/cvs?commit=93222 where i fixed most of the above bugs.
Comment #8
hass commentedhttp://drupal.org/node/207452 is a duplicate
Comment #9
davidburnsHey hass,
I want to make sure that my coding standards continue to improve. I'm reviewing my patch from your 7 comments listed above.
1. the comment out codes were in the module I was originally working on. I think my original patch shows that.
2. same as #1 I believe
3. refers to #2 & #4
4. My patch code looks nearly identical to what you have listed
5. Local cache copy? does this refer to #6.
6. googleanalytics_cron -> that function doesn't exist in the version I was working with.
7. I thought my submitted patch did reflect the ga.js
document.write("\<script src=\'" + gaJsHost + "google-analytics.com/ga.js\' type=\'text/javascript\'>\<\/script>" );So my question is.... did your list really apply to my patch or something else. As you can tell I'm somewhat confused.
Thanks!
Comment #10
hass commentedYour patch above was outdated when it was comitted and has been reroled with bugs.
I think budda added your changes, but re-introduced bugs (for e.g. #1: noscript tags) fixed earlier but after you created your patch... that's the main problem i think. Now it's more a follow up to fix bugs introduced by this committ and to add some missing/incomplete parts.
Comment #11
davidburnsThanks for clarifying that. I was really thrown off by not using the most current version.
Since the code has been committed, should this thread still be status: code needs work?
Comment #12
hass commentedyes, the committed patch is buggy, so needs work.
Comment #13
micahw156subscribing
Comment #14
Duplika commentedSuscribing.
Comment #15
rickvug commentedsubscribing.
Comment #16
tancWill the new GA code be able to be cached by this module, like the legacy urchin code can be?
Comment #17
hass commentedYes. D6 already caches both, D5 need to be fixed.
Comment #18
buddaCache now downloads the old or new GA file depending on the legacy setting.
Cron now clears the right file.
Comment #19
hass commentedAll from #6 should be fixed now.
Comment #20
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.