Integrations

Quick Overview

This module creates a basic widget for displaying all the latest announcements made on the forWhereiAm platform by your organisation (and any of its associated branches) for a given user's location. This module interacts with the forWhereiAm API and implements the client-side flow.

The forWhereiAm platform allows any organisation to target their online and mobile communications from a country wide region, right down to a single postcode. The messages are only seen by users who are in the regions explicitly targeted. Currently forWhereiAm only supports the UK market.

This module adds a jQuery plugin to your site which performs client-side flow requests to forWhereiAm announcements API. It fetches announcements for a given user's location, and displays them in a list form, ordered by the newest announcement at the top. This module can also communicate with the forWhereiAm API to fetch the full details for a given announcement, or optionally rate an announcement where rating of an announcement has been enabled.

This module uses Google Maps v3 API for rendering maps, if enabled.
This module uses AddThis for displaying social sharing buttons for an announcement, if enabled.

Further reading

I currently can not make commits, so I've set up this project to post changes made to the Affiliate module.

Drupal 7.x

Comment sources makes it possible to manage multiple sources (i.e. 3rd party services) of comments on nodes and node types.

Initial contributors:

This project allows external websites to interact with the Achievements module on your Drupal site. It provides a Services API and Javascript library that can be used on any site.

Currently this library exposes the following API to external sites:

• get_all_achievements: Retrieves a list of all possible achievements that can be awarded.
• get_user_achievements: Retrieves a list of all achievements awarded to a given user.
• achievement_trigger: Triggers credit toward an achievement for a user.

Requirements

• Services 3.x
• Achievements

NOTES and WARNINGS

This initial version of the module has been built for a very specific intranet implementation. As such, it may not be appropriate for use on public websites.

• Users on external sites must have an account on the Drupal site.
• The Services API is setup with session authentication, so the users must either already be logged into the Drupal site or the Drupal site must be configured to support an automatic SSO

To determine “popular” content, Gigya offers services via their REST API. We implemented the getTopStreams method to acquire a list of popular content rated based on comment count. Unfortunately the defined maxStreamAge “The number of days. The method retrieves only streams that were created within the past maxStreamAge days. The default is 3 days. The maximum is 7 days.” turned out to be a hard reset on the returned content. Meaning once the time limit was met, items were immediately dropped of the list of returned items. This implementation was a bit jarring, content that had high comment counts were being dropped off the results by time and not based off of their actually popularity.

We decided to implement the algorithm used by Hacker News described in this blog post http://amix.dk/blog/post/19574

To start using the Gigya Top Comments module, add your Gigya API key and Secret key to to the admin screen. Each time cron is run, the module will retrieve the top comment streams from Gigya and display the matching content in the Gigya Top Comments Block. If the block is not displaying content or you see the error message "Content not found. Stream ID does not match any node ID's" then your database may be out of date. Make sure you are working with the latest production copy of your db so that the streams ID's can be correctly match with nodes.

This module has been designed to allow users on your website to display badges that they have grouped in Mozilla Backpack.