Skip to content

Contributed modules

zzolo edited this page Nov 28, 2011 · 11 revisions

This page is focused on giving a brief description on why and how contributed modules are used on the application. Most modules are installed with a pretty specific purpose in mind (or hopefully they are).

Keeping track of this is important to undersand the application as a whole, and to get a view of possible performance or functional issues.

DFP = Disable for Production. There are a number of modules that can be disabled for production. This is not currently done, but could be. This might be depending on the Development Workflow and Configuration Management.

  • Block Class: (??)
  • Add Another: Used so that users can easily create more nodes (specific content types?) of the same type by choosing "Save and Add".
  • Address Field: (??)
  • Add to Any: Used so that (specific) content can be "socialized" with the Add-to-Any/Lockerz service.
  • Admin Menu: Creates a helpful administration menu to get to almost all configuration pages of the site. Only for administrators. (DFP)
  • Advanced Help: Provides an interface for modules that provide integration (help text). This is most often for site building help. (DFP)
  • Auto Node Title: Based on fields or other node data, create a title automatically. (where specifically used?)
  • Backup and Migrate: Used to export the database easily through the interface without having to log into the server. (this could be used to set up regular backups too)
  • Book Made Simple: (??)
  • CCK Phone: Provides a field (was CCK in D6) for phone numbers. (specific content?)
  • Corresponding Node References: Creates a link from a referenced node to the referring node. (specific content?)
  • Conditional Fields: Provides an abstracted way of having fields depend on other fields (this value is needed for this other field to be available). (Is there a specific reason this is installed?)
Clone this wiki locally