Integrations

Google Gears is an open source project that enables more powerful web applications, by adding new features to web browsers.
This gears.modulo integrates with drupal part of the functionalities of google gears

The LocalServer module allows a web application to cache and server its HTTP resources locally, without a network connection.

The LocalServer module is a specialized URL cache that the web application controls.
Requests for URLs in the LocalServer's cache are intercepted and served locally from the user's disk.

The WebPurify module provides developers an easy to use interface to the WebPurify REST API.

The Domain GeoLocalization module is a submodule for the Domain Access module that allows domains to have associated locative information.

A library that relies on the stock PHP library and provides IMAP integration with Mail API.

This module provides a block allowing users to spread the word about your website. Think of it as Forward module but as simple as it could be! The goal was to a have a simplier user experience than Forward. You can also check Tell a friend.

Since 6.x-1.4 mollom integration must be re-configured at the mollom level.

What it does?

User on your website gives a number of email adresses and his own. When user submit, each adresses (if valid) that was filled receive an email (that you can configure) from his friend advicing he/she to check the web page the sender was!

Additionnaly, a watchdog entrie is added logging who sent and who received.

Version 6.x-1.0 brings CAPTCHA & Mollom integration.

Differences with Tellafriend and Forward

• User doesn't need to fill a message (action for spreading is faster)
• Provides a block, which mean your not limited to node pages
• Sent email contains the user current url, (same as forward but only for nodes a guess?, Tellafriend doesn't)
• Submission of the form is proceed through Ajax when possible. If no JavaScript is present, then it will degrade gracefully.

This module attempts to provide a compatibility layer between the old CiviCRM 1.0 API and the new CiviCRM 2.0/3.0 API.

Only install this module if you are using CiviCRM 2.0+ and if a CiviCRM module depends on it.

The module is currently seeking a maintainer who can bring it to a stable release (see below). As I have outlined in #816366: Seeking new maintainer, I am not certain it is still necessary.

It is being used by the civinode (see #230103) module. It was also being used by the send module, but, to the best of my knowledge, it is not anymore. It is not used by the new 6.x version of the CiviCRM Subscribe module.

If you know of other modules depending on this module, please add them to this list: #922748: Create complete list of modules depending on this module (both in 5.x & 6.x), and I will add them to the project page, and advise them to upgrade their code to use the new CiviCRM API.

Seeking new maintainer

Since this module will no longer be needed by the 6.x branch of the CiviCRM Subscribe, and I no longer have any sites running 5.x, I don't have a compelling personal reason for working on it, and thus am seeking a maintainer who needs to use it for compatibility with CiviNode or another module, and so is in a better position to test patches.