Seeking co-maintainer(s)

Notice: Twitpic recently changed their API, breaking the module. I have not yet had time to fix it, but patches from anyone are welcome.

This module allows Twitpic images to be displayed directly on a Drupal site, allowing Twitter and Twitpic to be used as a mobile engine for a photo-rich blog.

Twitpic allows images to be posted to Twitter, appearing as URLs in a Twitter feed. Pulling Twitter feeds into Drupal is a great way to get easy mobile micro-blogging, and some mobile Twitter apps include photo upload capability.

The problem is that the feed only shows URLs, not the images. The Twitpic API allows thumbnails to be displayed in a browser, but makes the full images available only as downloadable files. This module uses an Input Filter to intercept Twitpic URLs, download their originals to the Drupal filesystem, and display the images instead of the URLs to the end user.

Activity Stream for http://Identi.ca, a micro-blogging service.

An extended ImageField widget that adds new form fields to a Image field. It provides the framework to associate new data with an image.

All processing, including storage, is done via ImageField. This module simply allows you to easily extend the currently available form fields; alt, description, title, etc.

A very simple admin interface provides a way of adding textfields, textareas, WYSIWYG textareas and checkboxes. Once defined here, each new form field can be enabled on each widget separately.

Of interest to developers will be a new hook "hook_imagefield_extended_widget" that provides a programmatic way of adding any FAPI elements to the ImageField data form element. This '#tree' element has all of its data automatically saved by the FileField field.

New to the 6.x-4.x Branch

Significant change to the way the module works. This now "extends" the base FileField widget using the new CCK 2.5 alter hooks, which is also a requirement. The update script should convert all of your existing fields. All FileFields and ImageFields can be extended, as can any widgets from other modules that provide additional functionality to FileField. REQUIRES CCK 2.5+

Drupal 7

Due to the refactored nature of file and images in Drupal 7, there will be no D7 port. Recommended replacements include either:

a) File entity and File entity inline
http://drupal.org/project/file_entity
http://drupal.org/project/file_entity_inline

b) Field collection
http://drupal.org/project/field_collection

This module enhances the standard Drupal comment module's API by providing hooks in comment_render(), which allow you to manipulate comment threads in your own way.

It also provides a better comment-wrapper template with the ability to place form on top of comments and other useful stuff (like in Drupal 7). Since this module is not used in the Drupal 7 version of ajax_comments, it will not be ported unless someone identifies a need.

You need this module if:

• You use the Drupal 6 version of the Ajax Comments module. This module is a prerequisite. Drupal 7 ajax_comments does not require this module.
• You wish to use some of the more advanced custom rendering of comments. This is excellent for additional theme enhancements with more control provided by comment-wrapper.tpl.php.

The module is well-tested and in wide use, however there may be an issue with Panels. Patches and fixes are welcome.
#672722: Add compatibility with panels

7.x Version

The 7.x version is under development. It currently supports settings for content types to change the sort order of comments on nodes. The currently supported sorts are by Newest, Oldest, Most replies, and there is a submodule that sorts by most votes using Voting API and supported through Vote Up / Down.

This module allows you to define Webform nodes as checkout/order panes in Ubercart.

This is useful if you want to collect additional information during the checkout process. For example, you may want a quick survey or require additional fields that apply to the entire order.

Using the Webform module allows for many advantages: the forms/fields can easily be modified by an end-user; less development time is required to create database tables and code to store/retrieve the data; and the form will remember the user's previous answers.

Furthermore, this module now provides tokens for every field in each of your enabled webforms, making it easy for you to insert the submitted values into confirmation emails, invoices, etc.

NB! You must update to Ubercart Webform Checkout Pane 3.7 for Webform 3.16+ compatibility.

Notes

• Fieldsets are not supported.
• Saving drafts and multi-page webforms are not supported.
• Views integration still not available in Webform 3, see #680386: Views integration for the webform_submitted_data table.
• Checkout pane webforms are now governed by Ubercart permissions.

Maintainers

The Own Term module grew out of the need to create blogs that were more flexible than the standard blog that comes out of the box with Drupal, particularly:

1. We wanted blogs to have a name different than the user who wrote them.
2. We wanted to include other things than blog nodes in a blog stream, such as polls.
3. We wanted a blog that more than one person could contribute posts to.

After some thought, it occurred to us that really, all a blog is is a collection of nodes. And if you want to collect a bunch of nodes together, then taxonomy seems to be the best way to start. They've even got taxonomy out of the box.

When you enable ownterm you need to set up a vocabulary which is set up for ownterm by clicking on the 'Enable Ownterm' checkbox in the vocabulary's edit page, and this should be an empty vocabulary to start with. After that you need to give at least the 'create and edit term' permission to authenticated users.