Modules

Adds an AJAX Login/Registration page to any node/add form(s).

Users can login using their email address or username, depending on cofiguration, without having to leave the creation form. If the username or email address is not found in the database, a registration form is presented that may optionally include a username. If the username is not part of the registration process, the email address is used as username.

The server may be polled for account information when the user types a valid email address and a set time interval passes, whenever the user stops typing and a set time interval passes or whenever the user chooses to click a provided next button.

The login can also selectively 'refresh' fields within the node creation form.

Thanks to Greg Mckeen for co-authoring and helping to bring the module thus far.

Update: This module is being deleted in favour of a Feeds-based client (see http://drupal.org/node/318579#comment-2376534)

A FeedAPI-based client for the clients module. This project is in a very early pre-alpha state and shouldn't be used on a live site.

Features yet implemented

• You get tag suggestions based on your current content!*
• Adding a suggestion using one-click
• Tagging using a 'nicer' and easier visual interface.
• No comma-seperated lists anymore!
• Using mouse to one-click-remove assigned tags.
• Supports several tagging-vocabularies on one node-edit form
• Use the simple suggestion-API or the alter methods to add new suggestions
• Theme the whole output
• Reuse the form-element 'tagging_widget'

You can see how the plugin works - just look into this video-podcast

Compatibility / Dependencies

Server Dependencies

none (optional extractor)

Client Browser Dependencies

- Javascript
- This plugin works in: IE6, IE7, IE8, FF(3.0.x - 3.5.x), Safari, Opera(9.63)

Installation

You need JQuery and taxonomy, which are both in the Drupal-Core.

1. Just activate the module and then create or edit a tag-Vocabulary.
2. Now check the checkbox "Tagggin Widget" in the vocabulary settings

The Accessible Content module helps content authors create and manage content in a way that ensures that the content meets accessibility standards, and lets site administrators build and customize the standards the site should adhere to. When the module is enabled, it creates two kinds of nodes, a collection of Accessibility Tests, and a group of these tests called Accessibility Guidelines.

The module can test the accessibility of content in both the node body and also any CCK Text field with input filtering (not plain text).

Requirements

• Most current release of the QUAIL project
• PHP 5
• DOMDocument
• cURL

An optional feature to improve the usability of the highlighted view of accessibility problems requires the BeautyTips module; however, this module is not required for Accessible Content to function.

Important Notes

This module installs two node types: Accessibility Tests and Accessibility Guidelines. In addition, it will create around 200 Accessibility Test nodes and the following Guidelines:

• Section 508
• WCAG 1.0 (A)
• WCAG 1.0 (AA)
• WCAG 1.0 (AAA)
• WCAG 2.0 (A)

This module will migrate the core profile fields to nodes for use with the Content Profile module.

Go to the User Administration area to see a place where the migration can be configured. You can choose which content type should be the profile and whether each profile category will become a fieldgroup on a single content type or a separate, new, content type. Do not add new fields to your content type for the profile fields, the fields will be added automatically. It is fine to have other, unrelated, fields on the main profile content type, they will not be affected by this processing.

The core profile fields will be analyzed and they will automatically added to the profile content type. If you choose the option to treat each category as a separate content type, the additional content types and their fields will also be created.

Once all the fields have been created, the data will be migrated to the new locations in a batch process that will display the name of the user being migrated.

The original profile tables are not deleted by this processing, so the original data remains where it can be used by other modules. The tables will be deleted when the profile module is uninstalled.

As always making changes like this, be sure to create a good backup first.

Full featured stand-alone Drupal module to accept Perfect Money SCI payments on your website.
Supports payments both directly via embedded payment form and using internal API & hooks.

Features:

• embedded payment form for manual payments
• supports API & hooks to interact with other modules
• adjustable list of currencies
• sample settings page for easy tuning Perfect Money to enable SCI
• all payments are stored in stand-alone table
• ability to browse payments in admin interface and taking actions on them (deleting and enrolling)
• ability to hide result url (path module required)
• themeable "Payment success" and "Payment failed" pages
• supports passing additional payment fields (via API)
• MySQL and PostgreSQL support

Suggestions and bug reports are welcome. Support in module installation and integration is possible.

My Perfect Money accounts for donations:

• U1166931
• E1913425
• G2256135

Please send any donation (for instance 10$).

My other module like this one: Webmoney Merchant Interface