Closed (fixed)
Project:
Google Analytics Reports
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
20 Apr 2011 at 23:32 UTC
Updated:
12 May 2011 at 19:31 UTC
Jump to comment: Most recent file
Comments
Comment #1
2ndChanceTech commentedstill banging my head against the wall on this one... any input would be appreciated. I'd be happy to sponsor / pay for a solution if it would get things moving, seems like it's exactly what I need for my site.
Comment #2
grendzy commentedThanks for testing the -dev release! Can you try the latest version and report back? I would suggest uninstalling and re-installing the module as well. Normally, failures are recorded by watchdog, for example here's one that occurred during testing:
Comment #3
2ndChanceTech commentedI'm trying the latest dev version (uninstalled and deleted folder, then installed and updated).
I try going to admin/reports/google-analytics
and get the error. When I go to my watchdog at admin/reports/dblog
There's no new entries. Am I looking in the wrong places?
Comment #4
grendzy commentedweird, sounds like you are doing things right. Are you able to add a some debugging code?
If you install the devel module, adding "dd($summary);" will dump debugging data to a text file: /tmp/drupal_debug.txt. If you upload this debugging file perhaps we can figure out what happened.
Comment #5
grendzy commentedI think I've found something. There's some code where in_array() is used to test for failures - but since an empty array is equal to false, if there are no referrals for a page it looks like a failure. Fix coming soon...
Comment #6
2ndChanceTech commentedawesome! hopefully that's the case. I tried adding the debugging code but for some reason it's not outputting a debug.txt I'm switching vps's today, hopefully less issues after the change, and your fix!
Comment #7
Narvath commentedDoes this happen to everybody? I noticed not too much people are using this module yet and do I have to do the domain management for it to work? I don't think I did it properly (https://www.google.com/accounts/ManageDomains) I somewhat have to find the certificate for my server.
Comment #8
grendzy commentedThis should be fixed in alpha1.
Comment #9
2ndChanceTech commentedAWESOME!! Worked right away after upload and update! Thanks so much for this module. I'll continue to test it for bugs, and such.
Comment #10
grendzy commentedGreat! I actually meant to tag today's release as beta, but was a bit too tired and typed alpha instead. :-) Anyway the beta cycle will be very short, we're hoping to reach 1.0 quickly, so bug reports are appreciated.
Comment #11
Narvath commentedYeah it worked really well for me too! Do you think there would be a way to show other kind of information in the "Google Analytics page traffic (small)" block? Because right now I think it only shows the number of views for the current page. Thank you alot for this module!
Comment #12
grendzy commentedThanks for the feedback. The default reports are likely to stay fairly basic. For customizing the reports, you have several options:
-- Use CSS or template overrides
-- hook_chart_alter to change the display of the graphs
-- or use the API to create your own custom reports.
Future efforts for custom reports will go into #760592: Integrate with Views so Views can use Google Analytics as a data source. If we can get the views integration working it should be possible to build almost anything.