Analyze This! Using the Google Analytics API
Google Analytics is a great way to monitor site usage and traffic. You add Google Analytics to your site using the Google Analytics module, which is super simple to set up. After it's in place, you can go to the Google Analytics site and dig into a ton of data, create custom reports, etc.
But you can also use the Google Analytics API to pull Google statistics into your own site and display them there. There is a Drupal module, Google Analytics API that was created by Joel Kitching as a Google Summer of Code project. It provides a wrapper you can use to create tailored queries of your analytic data. You can turn on the included 'Google Analytics API Reports' module to display Google statistics in blocks or pages right on your site, and/or create custom code to suck in specific statistical data and do any Drupally thing you like with the results.
Lullabot Podcast 81: Live from Do It With Drupal 2009
A panel of Drupal experts take questions at the Do It With Drupal Seminar 2009. Panel members: Nate Haug (Lullabot), Josh Koenig (Chapter Three), Emma Jane Hogbin (Hick Tech), Angie Byron (Lullabot), Ryan Szrama (Ubercart / Commerce Guys), Alec Hendry (MTV UK), Paul Reeves (MTV UK), and Jeff Robbins (Lullabot).
User Management for Real World Groups
Drupal's default methods of handling user names, emails, and registration processing work pretty well out of the box for many web sites. Drupal assumes your users are online, have unique email addresses, and that you want to create a site that grows organically as users find it and register themselves. Drupal out of the box may not work so well for real-world groups of people where the group already exists and consists of specific people who may or may not be online, may or may not have unique email addresses, and may or may not be able or willing to register themselves on your site.
Some good examples of the problems I have run into are creating web sites for families, clubs, and churches, but the same problems exist for any other real world organization or group. They have established groups of members, some of whom may share email addresses or have no known email address. And in these cases the administrator will probably create user accounts for everyone rather than waiting for users to self-register. On top of that, we may want some control over usernames so that users can recognize each other once they do get online, by forcing the username to be FIRSTNAME LASTNAME.
This creates several problems that have to be overcome creatively. After several years of trying various approaches, here is a summary of the problems I ran into and the ways I eventually solved them. I have included links to the ones I discuss, with the number of downloads in the week of November 22 as a measure of how commonly used they are.
Command Line Basics: Symbolic Links
- 6 comments
- by addi
- play
- 7 min 8 sec
- 28.4 MB
Drupal Voices 75: Bevan Rudge on Civic Actions and Drupal in New Zealand
Bevan Rudge has been a Drupal developer and engineer at Civic Actions and talks about the structure of Civic Actions and challenges and benefits of being spread out across many different time zones. Bevan also talks about the Drupal scene in New Zealand.
Drupal Voices 74: Katherine Druckman on Managing the Linux Journal Website
Katherine Druckman is the sole "webmistress" for the Linux Journal's Drupal site. She talks about the evolution of managing the site, including recently incorporating version control and starting to build out more and more features as their needs grow.
Some of the modules that she mentions are Views Bulk Operations to help manage a streamlined workflow, Twitter & Activity for beefing up the user profiles, Flag for bookmarking content.
Finally, she talks about some of the motivations for coming to events like Drupalcon and Do It With Drupal, and compares and contrasts the difference between the two.
Drupal Voices 73: Liza Sabater on Drupal Site Building and Power Blogging
Liza Sabater is a Drupal Site Builder and active blogger who runs both Culture Kitchen and The Daily Gotham. She talks about being a non-module developing, site builder and the role of technical adviser to non-technical clients. And she also talks about why she chose Drupal for her blogging platform and some of her favorite modules including:
Drupal Voices 72: Simon Hobbs on the Evolution of his Drupal shop
Simon Hobbs (aka "sime") talks about the evolution of his Drupal shop Em Space based in Melbourne, Australia. Specifically, he talks about the shifts in job descriptions and challenges of running a small Drupal development shop. He also talks about the most crucial time of any Drupal project, which he sees as the beginning while the information architecture and module selection decisions are happening. He also talks about some of the crossroads that he's facing of where to focus the energy and growth of his company.
Drupal Voices 71: Joeri Poesen on DrupalCon Paris & the French Drupal scene
Joeri Poesen of AF83 was one of the organizers of DrupalCon Paris, and talks about the process of organizing the conference in coordination with the French Drupal Association.
Joeri talks about the French Drupal community and some of the sites being launched in France by AF83 and some of the other French Drupal companies.
He mentions that some of AF83's contributions include a lot of the core work that Damien Tournoud (aka "DamZ") has been doing, as well as some of the latest Übercart work that has been going on. Back in October Ryan Szrama announced the Ubercore Initiative, which is a combination of Ubercart, Drupal 7 and the influence of #Smallcore, and tagged with D7UC.
Damien has also been involved with this effort as one of the editors and AF83 is also one of the sponsoring companies for the effort due to some of the e-commerce work that they're involved with.
Joeri also talks about the importance of multi-lingual functionality and the i18n suite of modules.
Drupal Voices 70: Jeff Eaton on Token in core
Jeff Eaton talks about the third most popular contributed module in Drupal: the Token module.
Jeff talks about the architectural changes necessary in order for Token to be committed and included into Drupal 7. A lot of the changes will also eventually be backported to the token 2.0 version for Drupal 6.
There's also a pending User Interface issue for token in core that needs some help from someone with some javascript skills and initiative to get a UI into core before December 1st.
The original motivation for token in core was to have pathauto in core, but this did not get in before the API freeze, but the token functionality that made it into D7 will make pathauto's job much cleaner in contrib.
RSS Feed

