What started in #2032687: Drush Integration for GA Stats became a runaway train on github. I simply had more to do to the module for troubleshooting and production comfort-level than I could achieve by following the normal patch workflow. I have now been given committer rights, and will be merging my changes into the 1.x branch here.
So far, nothing I've done will create a BC break, but changes to cron scheduling works may cause a wrinkle in the stat collection happening a bit sooner or later than expected as the system works itself out.
Preliminary changelog
* Drush integration of statistics collection.
* Drush command to populate the data table with some faked up statistics.
* Administrative UI improvements.
* Improved logging and user messaging of error states
* Multiple status report entries for both good and bad conditions.
* Refactored API functions and general code flow.
* Minor fixes: Administrative permission
* Module un-installation cleanup
* General coding & commenting standards cleanup
Merge forthcoming...
Comment | File | Size | Author |
---|---|---|---|
#5 | ga_stats-2122793-5.patch | 939 bytes | hadsie |
Comments
Comment #1
Grayside CreditAttribution: Grayside commentedhttp://drupalcode.org/project/ga_stats.git/commit/28ff3fd
http://drupalcode.org/project/ga_stats.git/commitdiff/28ff3fd?hp=0164911...
Comment #3
lmakarovThe administrative permission (https://drupal.org/node/1802378) is not fixed.
The permission should be "administer site configuration" and not "administer site config".
Comment #4
lmakarovComment #5
hadsie CreditAttribution: hadsie commentedHere's a patch for the access arguments issue.
Comment #6
DamienMcKennaThat should help.
Comment #7
DamienMcKennaComment #9
marcelovaniThis really needed fixing, I am going to make a new release soon
Comment #10
marcelovaniCommit should have done against #1802378: GA Stats Settings Page only accessible by user 1
Re-opening this issue.
Comment #11
wranvaud CreditAttribution: wranvaud at Phase2 commentedThis has been committed and released here, the other issue #1802378 points to this issue as the final one. I believe this one should be marked as fixed to avoid further confusion (and mark #1802378 as duplicate)
This was released in 7.x-1.0-beta3