Actively maintained

This module is to help run a Clan or a Guild website.
The module will give you a roster of your clan/guild members with there rank.

Description

Facebook Authentication provides a light-weight integration with Facebook's Single Sign-on API. It does not register Facebook users as Drupal users and it uses Javascript SDK, so there's no external library to download.

If you need to register Facebook-authenticated users as Drupal users, please take a look at: Drupal for Facebook module by Dave Cohen.

The principal difference between how this module approaches Facebook Single Sign-on integration and Drupal for Facebook one does is that DFF assumes you want to use Facebook as yet-another authentication and authorization mechanism (in addition to DB and OpenID), whereas this module assumes you do not want to authorize Facebook-authenticated users to anything in Drupal, you just want to grab the user's Facebook authentication data to use it for display (e.g. in comments and such things).

This module also exposes Facebook user data to Drupal's theming layer and third-party modules so you can use it wherever and however you need. Facebook Authentication module will soon provide optional default integration with Comments (which can be disabled).

Requirements

#D7CX: I pledge that SimpleWiki Filter will have a full Drupal 7 release on the day that Drupal 7 is released.

SimpleWiki is an easy-to-use input format based on the work done by WikiCreole researching common wiki markup elements. SimpleWiki uses Creole syntax extended with decorators and block declarations for advanced markup.

Authorize.Net integration for the Drupal Commerce payment and checkout system. Currently supports credit card payments on the checkout form via the AIM API using the latest Commerce release. Additionally, integrates with the CIM API to provide Card on File payment support.

Sponsored by Centarro, an Authorize.Net reseller.

Create beautiful gradient images controlled by Bezier control point colors.
The module supports 1-dimensional (1*h or w*1 px width/height) and 2-dimensional (w*h px) images.

Some examples:
http://dqxtech.net/blog/2012-01-30/imagene-sample-images

How it works:

• You edit one of your css files (or play with Firebug), and assign a new background image to something. The image url should be /sites/[sitename]/files/imagene/etc (see below).
• If the image does not exist, imagene will create it, based on parameters from the filename and path.
• The image will be stored in the respective location, so the same image doesn't have to be created again (similar to imagecache). This behaviour is controlled by permissions (see below).
• you can keep the new image where it is, or copy it around to use it somewhere else.

Benefit:

• No more pointless toying around with Gimp/Photoshop, no more pointless copying around of image files, no more pointless copying of color hex codes between css and Gimp/Photoshop.
• Change colors directly from your css file, by changing the url of the background image. Colors and image dimensions are encoded in the url in a transparent way.
  

Whenever the cache is cleared (or "flushed" in Drupal parlance), whether from new content creation of a volundary flush, the burden of caching is moved to the users: files are not actively rebuilt