Seeking new maintainer

Overview

This module accelerates the time to implement Janrain Registration into your Drupal web sites, helping you to improve your registration conversion rates by allowing your customers to register and sign-in through their Social Network of choice.

Janrain Capture is a hosted registration and authentication system that allows site owners to provide a central repository for user information, that can be deployed on one or more web sites. Registration and authentication can be done through connection to a social network identity provider such as Facebook, Google, Yahoo!, OpenID, LinkedIn, Twitter and many others or through traditional form field methods.

Features

• Social and form based registration
• Social and form based login and authentication
• Central data store for one or more sites
• Single Sign On to federate identity across multiple domains

Requirements

This module is available both for Drupal 6 & 7, so please install the appropriate version. A PHP version of 5.2.x or above is required.

Library dependencies:

• Fancybox
• json2.js

Module Dependencies

Summary

A simple module to encompass updates to Drupal to satisfy vulnerabilities reported by Approved Scan Vendors (ASV), often as a result of the PCI DSS compliance processes.

This module pulls statistics from piwik and stores them to fields of any entity

(eg. nodes, users, ..).

Features

• Statistical information is stored in fields you can attach to any fieldable entity
• Dynamic formatters to show statistical information on entities
• Configurable 'period' parameter for each field
• Full Views integration to build things like "Top5 Viewed Nodes"
• Statistics summary tab on nodes and users
• Refresh statistics on cron (queued) run or on demand (batch)
• Currently tested with latest Version of Piwik (1.8)

Requested data

• Unique entity page views.
• Overall entity page views.
• Number of visits that started on an entity.
• Number of page views for visits that started on that entity.
• Time spend, in seconds, by visits that started on this entity.
• Number of visits that started on this entity and bounced (viewed only one page).
• Number of visits that finished on this entity.
• Total time spent viewing this entity, in seconds.
• Ratio of visitors leaving the website after landing on this entity (in percent).
• Ratio of visitors that do not view any other page after this entity (in percent).

Usage

Per Page Queue provides a nodequeue service that can display a different subqueue for each page, based on that page's path.

It allows users with permission to create, edit and delete subqueues based on path aliases; By adding the provided block to the site, visitors can view these subqueues when visiting these paths.

Screencast: http://www.youtube.com/watch?v=6a6WbDQHEvE

This module provides integration between the Openlayers module (http://drupal.org/project/openlayers) and apachsolr (http://drupal.org/project/apachesolr) with local solr integartion. This provides a map, layer, layer type and block for openlayers. The block renders the map by the module and can be overridden by setting the 'openlayers_solr_map' variable.

The real strength of this module is when it's used with geofield (http://drupal.org/project/geofield) and geocode (http://drupal.org/project/geocoder).

Note: Currently the module assumes WKT codes are stored in the ss_geo_wkt fields in solr. This is because of the http://drupal.org/project/geofield.

Drupal 7

The 7.x-1.x-dev branch has been developed and tested using:

• Apache Solr version 7.x-1.1
• Openlayers version 7.x-2.0-beta5
• Geofield version 7.x-1.x (requires projection patch fix #1942826: Projection incompatibility with openlayers.)

Tutorials

• Video of Integrating Openlayers with Solr