Seeking co-maintainer(s)

The Active Translation module is designed for internationalized sites where translated versions of content need to be displayed when available but if they're not the original, untranslated content should be displayed. If several regional versions of a language are available these will be used as substitutions.

Oct 12th, 2008: I'm looking for co-maintainer for this module so if you're using this module and have some development experience either open an issue or contact me. I personally have no plans to port this to Drupal 7 so if you're interested please consider taking over the module.

This project uses Nodequeue's Smartqueue API to provide a nodequeue for each organic group, editable by members of that group or the group's administrators. This project was part of the 2008 Google Summer of Code.

Use the dev snapshot release or the latest from CVS HEAD until RC3 is rolled

1) When an OG homepage node is created, a nodequeue that corresponds to that OG homepage node will be created.
2) When an OG homepage node is deleted, the corresponding nodequeue will be deleted
3) Depending on configuration
- a) Members of the Organic Group and site administrators will be able to manipulate the nodequeue for that Organic Group.
- b) Administrators of the Organic Group and site administrators will be able to manipulate that OG's nodequeue.
4) The content of the Organic Group's nodequeue displays in a block defined by a view, provided by this module
- a) Administrators can specify an alternate view that will control the display of OG nodequeues
5) Administrators can specify which node types should be available in OG nodequeues

For the complete project proposal, visit http://groups.drupal.org/node/10067 .

Requirements

- You must install the latest version of Nodequeue.module!
- You must have PHP 5.1.0 or higher to run this module.

Please Note

The Mobile Codes module provides the ability to render Text, URLs or any other form of informaton as a Mobile Code, including but not limited to the QR codes and Datamatrix formats, providing a simple way of transfering said information from the screen to a Mobile phone.

Mobile Codes was written and is maintained by Stuart Clark (deciphered).
- http://stuar.tc/lark

Features:

• User definable and Features exportable Mobile Code Providers and Presets.
  • Defaults provided:
    • Six (6) External Providers.
    • One (1) Internal Provider (see below).
    • Three (3) to five (5) Presets (based on installed modules).
• Render Mobile Codes via:
  • CCK/Fields/Views formatters:
    • CCK/Drupal core Text module.
    • FileField/Drupal core File module.
    • ImageField/Drupal core Image module.
    • Link module.
    • plus an example Custom Formatter for extended support.
  • Input filter.
  • Drupal API Theme() call.
• Blocks:
  • Node URL block - Creates a Mobile Code of the current Node URL.
  • User vCard - Uses the vCard module to provide a vCard Mobile Code from a Nodes Author or a users profile.
  • [D6] Mobile Code generator - An Admin module optimized helper block.
• Support for:
  • [D7-DEV] Drupal core Image module - Use an Image style on the Mobile Codes.
  • [D6] Mobile Tools module - Redirect internal Mobile Code URLs to Mobile site URL.
  • [D6] Redirecting Click Bouncer module - Track URLs accessed via Mobile Codes.
  • Shorten module - Shorten URLs in Mobile Codes.

Streamlines the appearance of the standard Drupal comment form to appear more like WordPress.

Drupal 8 / 9: Consider using https://www.drupal.org/project/convert_bundles

Provide a CCK field type that lets you choose a file with IMCE.
This is not the same as FileField (see below).

Drupal 7

The core files management on D7 is smarter than on D6.
imceimage is designed to circumvent the file_managed table, but in D7 this is no longer necessary. You can use either filefield sources, or (recommended) IMCE Filefield

New maintainer (29 Nov 2011)

This module is no longer "deprecated".
See #703716: Offering to maintain Imce CCK Image

As the new maintainer, I plan to

• Fix any problems I run into myself (update: bad idea, now my use case for this module went to d7).
• Be responsive on the issue queue (update: if people provide me patches and do some debugging on their own.)
• Allow a co-maintainer to jump on the boat, if someone is interested.
• Improve code quality. -> done.
• Recent work will go into a new branch (6.x-2.x). -> done.
• Explain the difference to Filefield sources -> done.

There are no particular bugs I want to fix (yet), I just want this module to be not abandoned.

IMCE CCK Image vs Filefield Sources

There is an alternative to this project,