Modules

What modules are currently supported? | What modules have already been requested?
How do I request a new module?

Currently Supported Modules:

• Content Construction Kit (CCK)
  • Content
  • Date
  • Embeded Image Field
  • Embeded Media Field
  • Embeded Video Field
  • Fieldgroup
  • FileField
  • Image
  • Link
  • Node Reference
  • Number
  • Option Widgets
  • Text
  • User Reference
• Category
  • Category display
  • Category legacy
  • Category menu
  • Category pathauto
  • Category views
• Core - optional
  • Color
  • Help
  • Menu
  • Path
  • Profile
• Input helpers
  • TinyMCE
• Other
  • Date API
  • Glossary
  • IMCE
  • Panels
  • Path FIlter
  • Path Redirect
  • Pathauto
  • Path Filter
  • Site map
• Views
  • Views RSS
  • Views Theme Wizard
  • Views UI

Past Requested Modules

• Forms
  • Did not satisfy criteria #6. This module is very buggy. We understand there is a large need for this and will review it again in Drupal 6.
• Theme Settings API
  • Did not satisfy criteria #1 and #4. This module may be included in Drupal 6. Will revisit after release.
• Blog
  • Did not satisfy criteria #1. The features can be reproduced using the supported Views and CCK modules.
• Comment
  • Did not satisfy criteria #6. It introduces a high risk of exploitation.
• Internationalization
  • Did not satisfy criteria #1 and #4. Drupal 6, which is nearing a testing phase, will offer new language features which may overlap, or even conflict with, those in this Drupal 5 module.
• Epublish
  • Did not satisfy criteria #1. Most features can be replicated using Categories module and Custom content types.
• Poll
  • Did not satisfy criteria #1 and #6. OSU already offers Surveys. Also, it introduces too much risk of exploitation.
• Search
  • Did not satisfy criteria #1. OSU already offers Nutch for searching sites. By using only one search solution, we can better ensure consistent results for everyone.
  • How to get Nutch to display its results within your Drupal theme.

Requesting New Modules

Central Web Sevices has very high expectations for the modules we provide to Drupal users. Here are the criteria considered in the process of approving new modules:

1. Redundancy
   
   Does OSU already provide this service? Is this capability already planned for an upcoming Drupal release or update of a currently supported module? For example, we can leverage our preexisting service rather than support the built-in Drupal search feature.
2. Lifespan/Activity
   
   Is the module under active development? And how long can we rely on that development to continue?
3. Cost/Benefit
   
   Does the module provide a significant benefit to a large number of users? And does the benefit outweigh the time/effort to configure and support it?
4. Compatibility
   
   Does the module interfere with the functionality of currently supported modules? Might it interfere with an upcoming Drupal version or update of a currently supported module?
5. Support
   
   Will the module pose support challenges? For example, can we depend on preexisting documentation and other Drupal community resources in order to offer expert advice in the future? Are a significant number of our users already familiar with the module, and can we depend on them as a community resource?
6. Code Review
   
   Is the code behind the module well-written? Are there any possible security risks associated with enabling this module? For example, we will not enable the Comments module and allow anonymous users to post content. While that public feedback may be desirable at times, the risk of public exploitation (e.g. spam or hacking) outweighs it.

Clearly these requirements do not encourage casual requests. However, they do encourage high standards for module-provided services which will affect the entire OSU Drupal community.

To request a new module, please let us know how the candidate meets these standards.

Submit Request