Minimally maintained

Provides integration with Libraries API (2.x) and a Drush [Make] script to download the Namecheap SDK for use with the Namecheap API.

The NameCheap API allows you to build web and desktop applications that integrate with your NameCheap account. It allows you to programmatically perform operations like domain search, domain register, purchase SSL etc., from within your application.

Place the appropriate version of the Namecheap SDK in the libraries directory within the site you are working. That may be 'default' or 'all' like the following: sites/all/libraries or sites/default/libraries. The end result after extracting the library should be sites/.../libraries/namecheap/registrars/namecheap/namecheap.php.

Configuration can be performed either using variables hardcoded into settings.php or the UI. If you want to hardcode them then look at the UI for the variable names.

$conf['namecheap_username'] = '...';
$conf['namecheap_password'] = '...'; // API key, but SDK did not rename it.
$conf['namecheap_testmod'] = '...';

The following is an example of how to use the API inside of Drupal.

<?php

At the moment oAuth2 Connect allows you to authenticate with different 3rd party oAuth2 providers and maintains association between drupal uid and provider uid.

It's currently available for Drupal 6 only.

Here is the link which summarizes differences between oAuth1.0 and 2.0

http://blog.apigee.com/detail/oauth_differences/

The module provides an abstraction layer with pluggable components for different oAuth2 providers. Currently it doesn't have an UI and all oAuth2 configuration is done with plugins ( and plugins are just classes extending an abstract class ).

The goal was to allow the plugin to handle the dirty work ( dialog url creation, tokens manipulation, user data retrieval ), because each provider implements the protocol a little differently. Most notably Facebook requires post request to get the access token.

We tested the module with the following oauth2 providers:
- Twitter
- Facebook
- Yammer

The main ideas behind this module were simplicity and extensibility. Before creating this module I evaluated different options including oauth and oauthconnector but at the moment there was no Drupal 6 version with oAuth 2.0 support, only 1.0. There were also many dependencies to consider - oauth, connector, http_client, chaos tools.

Sandboxin og_services

DESCRIPTION:
Disclaimer Acknowledgment module module can be used to define the disclaimer message that is shown before user is allowed to enter the site.

Light-weight integration between Drupal Commerce and Campaign Monitor, allowing users to subscri

Target of the project:

List team information:

• Players
• Contributers
• Games (schedules, results and reports)
• Training schedules