Integrations

This module displays a block showing the number of times anonymous users and authenticated users have viewed a node.

Original Project by kreynen http://drupal.org/project/merci_email

Need git access to be able to push back changes

Other FB modules now available.

This module provides an integration with Omniture's Web Services API, for pulling site statistics and data into your own database on a regular schedule. It provides:

- Node edit level stats on specific node performance
- Site overview stats under the reports tab

It is capable of breaking out data based on user, node, and taxonomy pages, as well as general site overview data.

This module is behind the "views" count feature on the site FastCoDesign.com, and also serves as a useful resource for editors to keep track of top stories, and top-referrers for stories.

There are many caveats to using this, as the Omniture API, and data structure in general is quite tricky. It presumes that you have chosen to name your pages, for Omniture reporting, with the full URL path minus the server name. For instance http://site.com/article/how-to-build-a-website would be "/article/how-to-build-a-website" in Omniture.

I will take suggestions for enhancements to the entire scheme, as use cases come up.

Dependencies:

- Drupal Queue module (a backport of 7.x Queue feature).
- NuSOAP library, expanded in a "nusoap" directory within the module directory.
- An OmnitureAdminServices.wdsl file, from your Omniture admin.
- A valid Omniture account, with Web Services enabled.

This is a module to interact with TheTVDB.com. This will attempt to duplicate the functionality provided by the Amazon modules, though ofcourse more limited since purchases cannot be made through this source. Right now this is only conceptual.

I am looking to include links and a basic image for TV shows and movies, ideally with only a title being entered on the Drupal site (autocomplete will, theoretically include the years to help clarify which series it is). I noticed on someone's website (huge in drupal land) that she has currently reading, currently playing and currently watching. When attempting to reproduce those on my site, it was simple enough using the Amazon module for reading (and the use case I saw uses Amazon for all of it). The downside is that unless you're willing to go and get the numeric code for a specific item, the autocomplete title field is not enough to select an item (often enough, the specific item isn't in the list). That and I'd rather honestly link to IMDB for all of this, but they don't seem all that friendly to external use of resources.

Anyway, integrating a Drupal site with TheTVDB just makes sense to me (potentially, I'll be doing a similar thing with themoviedb.com; if the module hosted on github and posted about in the news section of the forums doesn't suit my needs).

Working on improving New Relic RPM integration.

Original project