Contrib

From Things and Stuff Wiki
Jump to navigation Jump to search


todo; split out d6. write section intros.

General

Core non-core

Admin

Management

admin of submitted unpublished nodes, updating coordinator contact info, etc

Layout

Spaces

Blocks

Views

Views is used to display bits of content in various fashions.

  • How to display content nodes using Views 3: *to source again*

API

Modules

Nodequeue

Manual list of content items, can be used in Views.

Path

Title

Links

Content

Entities

  • http://drupal.org/project/entity - "extends the entity API of Drupal core in order to provide a unified way to deal with entities and their properties. Additionally, it provides an entity CRUD controller, which helps simplifying the creation of new entity types."
  • http://drupal.org/project/file_entity - makes the file entity full fledged, allowing for fields, display formatters, and more.

Fields

Bundles

Nodes

Books

Audio

  • http://drupal.org/project/audio - allows users with proper permissions to upload audio files into drupal. Each audio item is created as its own individual audio node. The audio module uses the getID3 library to read and write ID3 meta-tag information to and from the audio file. Pages that display the most recent audio files submitted to the site, as well as the most recent audio files uploaded by individual users are also generated. Feeds from these pages are 'podcast friendly'. The module also comes with the handy XSPF Flash player that is (by default) embedded in your site.
  • http://drupal.org/project/filefield_audio_insert - extends the functionality of the cck filefield module. It allows you to insert flash playable audio into textareas/body's of nodes. It works in conjunction with the mp3player module for audio playback.
  • http://drupal.org/project/debut_audio - A baseline embedded audio feature.Audio content type with embedded audio field supporting multiple external providers. Audio view with page listing, recent audio files block, and RSS feed. etc.
  • http://drupal.org/project/audiofield - allows you to upload audio files and automatically displays them in a selected audio player. Currently it supports 6 players and it provides API for easy addition of new players.
  • http://drupal.org/project/audioconverter - converts audio files from supported CCK fields (AudioField, AudioRecorderField) to the mp3 format using FFMPEG. Depending on the need, files can be converted on cron or whenever new audio content is submitted.
  • http://drupal.org/project/jplayer - provides a wrapper around the jPlayer JavaScript library. This library provides an HTML5-based player, that uses a Flash fallback for browsers that do not yet support it. This module provides a default presentation for the player, as well as integration with CCK file fields and a display style for Views.
  • http://drupal.org/project/mp3player - WordPress Audio Player to Drupal. Easily enable the MP3 Player on a CCK FileField. Setup multiple players each with their own settings and appearance. FileField and Views support.

Media

  • http://drupal.org/project/emfield - create fields for content types that can be used to display video, image, and audio files from various third party providers. When entering the content, the user will simply paste the URL or embed code from the third party, and the module will automatically determine which content provider is being used. When displaying the content, the proper embedding format will be used.
  • http://drupal.org/project/media - provides an extensible framework for managing files and multimedia assets, regardless of whether they are hosted on your own site or a 3rd party site - it is commonly referred to as a 'file browser to the internet'. Media is a drop-in replacement for the Drupal core upload field with a unified User Interface where editors and administrators can upload, manage, and reuse files and multimedia assets. Any files uploaded before Media was enabled will automatically take advantage of for many of the features it comes with.

etc

Flickr

  • http://drupal.org/project/flickr - Access photos on Flickr's site via their API. The module provides a filter for inserting photos and photosets and allows the creation of blocks for rendering a user's recent photos and photosets. The filter format is: [flickr-photo:id=230452326,size=s] and [flickr-photoset:id=72157594262419167,size=m]
    • doesn't use image styles
  • http://drupal.org/project/flickrgallery - This module will show all your sets and pictures from your Flickr account. There's no need to create extra content types or feeds. Just fill in your settings and your gallery is done. views??
  • http://drupal.org/project/media_flickr - The Media: Flickr project currently offers Flickr Photoset capabilities to the Embedded Media Field module, upon which this module is dependent. To use it, enable the Embedded Video Field module, and add a Third Party Video field to a content type.

Attachments

Extras

Search

Editing

Importing

Antispam

Other

Attention

Taxonomy

  • http://drupal.org/project/content_taxonomy - D6, This module provides a CCK field type for referencing taxonomy terms. The fields are independent from vocabulary settings. For every field you can specify settings. D7,

Organic Groups

D6

  • http://drupal.org/project/og_subgroups - enables a user with the proper permissions to build group hierarchies (or tree) by nesting groups under other groups. Simple or complex group hierarchies can be easily created.
  • http://drupal.org/project/og_features - allow group owners and site administrators to disable certain features/functionality within a given group (without the use of the Spaces module).
  • http://drupal.org/project/og_privacy - define the rules by which organic groups posts will be visible to non-group members. It is an API module which allows developers to create access policies which override the default behavior of OG Access and Spaces OG.
  • http://drupal.org/project/og_invite_link - OG Invite Link overrides the user invitation form that comes with OG - used to invite non-members to a given group. The key difference is that invitation emails contains a special tokenized invitation link, meant specifically for that user.
  • http://drupal.org/project/og_titles - extends group membership to include arbitrary titles with which you can add to Organic groups views. Titles are per member and arbitrary strings. Examples of titles are strings such as "Chairman", "Secretary", or "Really Cool Dude". These can be accessed via Views.
  • http://drupal.org/project/og_access_roles - extends the reach of Organic Groups' bundled Organic groups access control module by allowing node authors finer control over who can see their posts. Organic groups access control gives node authors the option of making their posts Public, meaning anyone can view the node, even anonymous users; or Private, meaning only group members can view the node. For Private posts, OG Access Roles gives node authors the ability to let users in selected roles view nodes even if those users are not in the group (or groups) where the node is posted.
  • http://drupal.org/project/og_perm - In the OG module all group admins currently have the same set of capabilities within their group. They can add/ remove members, broadcast messages, and create/remove group admins. This module requires that group admins also have a certain permission to get those capabilities.
  • http://drupal.org/project/og_massadd - Overrides the internal "add users" page of Organic Groups with a more powerful alternative. Takes a list where each row can be either: username - mail address - firstname, lastname, mail address - firstname, lastname, mail address, desired username.
    • In case 1 or if there is an mail address provided, the module first checks if it matches an existing user, and adds that user to the group.
    • In case 2-4, if there is no matching user, the user will be created (as long as the person submitting the form has permissions to do so). Newly created users will also have a content profile node created for them if enabled (has a settings page).
  • http://drupal.org/project/og_read_only - allow group administrators to set some content types as "read-only". Read only types can't be posted by simple group members, but still can be posted by group managers and users with "administer nodes" permission. Wiki group types can't be set to read only.
  • http://drupal.org/project/og_node_approval - offers content review between group members allowing them to approve or reject content. When creating or updating content simply choose the audience for the content (including multiple groups), save the node, and the module will insert group members from those respective audiences into the a node approval table.
  • http://drupal.org/project/og_audience - allows Organic Groups (OG) users to change a node's audience without having to edit the node. This module works by providing a new change audience permission, and an Audience tab and/or block on node pages that allows users to change the audience of existing content. A user can add any node to one or more of the groups he/she has subscribed to. A group manager can remove a node from his/her group(s). A node's author can remove the node from one or more of the groups he/she has subscribed to.
  • http://drupal.org/project/og_teams - create groups of users (teams) that can be subscribed to organic groups just like regular users. Teams are like user roles, you can create new teams and you can assign multiple users to any team.
  • http://drupal.org/project/og_mandatory_group - makes one group mandatory for all new users and/or requires new users to pick a group. Choose one group that all new users will be put into. You can chose either an open or a closed group. Any new user will be auto-approved as member of the group. The group manager(s) of groups that a new user joins will get an automatic e-mail notice.
  • http://drupal.org/project/og_manage - added tab to user account where administranor can select groups user belong to and make user of this groups or remove membership on one page.
  • http://drupal.org/project/ctog - Running Case Tracker and Organic Groups on the same site raises some questions - but CTOG helps solving them by utilizing some rules to tie them together in a way which makes them easier to use.
  • http://drupal.org/project/og_mailinglist - OG Mailinglist allows users to start new discussions by email and post comments on existing discussions by simply replying to emails. You get the best of both worlds: a browser-based discussion site and an email-based list.

Users

Context

Project

  • http://drupal.org/project/merci - can extend any content type into a list of unique reservable items (like studios) or buckets of interchangeable items (like DV cameras). We followed the approach used by Organic Groups, Feed API, and Scheduler and added MERCI's configuration to the Edit tab of those content types.


Social

  • http://drupal.org/project/privatemsg - allows your site's visitors to send private messages to each other. Perfect for community oriented sites, such as forums and social networking sites. Many additional features are available as separate modules.

D7

Other

Eye candy

Search

Aggregation

Feeds

Views owner node title - http://drupal.org/node/1257170

OpenCalais

Analytics

Retrieved from "https://wiki.thingsandstuff.org/index.php?title=Contrib&oldid=5976"