Drupal Commons module listing & discussion
Release 1.1 of Drupal Commons contains the following non-core ("contributed") modules, for the indicated reasons. The Drupal 7 status of those modules is shown here.
Module (set) nameWhy included in CommonsEnabled by defaultAcquia Network ConnectorEnabling these modules makes it easy for users to quickly set up a 30-day free trial of an Acquia Network subscription. (Also included because Acquia NoAdministration MenuProvides a popular, simplified user interface for Drupal site administrationYesApache SolrCan provide faceted search, content suggestions, and spelling corrections for site search when used with a Solr-based search server (which is provided by the Acquia Network; so therefore these are required if/when the Acquia Network Connector modules are enabled.)NoCCK (set)Provides extensive capabilities for creating custom content types beyond those included with Drupal Core; this is used to create, for example, the Event content type, Notice content type, and many others.All except include Node or User Reference or NumberChaos Tool SuiteProvides a library of helpful tools. This is a prerequisite for various other modules used in Drupal Commons.Chaos Tools, Page Manager & Views Content panesChartingUses the Google Charts API to create the graphs generated by Quant.Chart APICommonsAll of Drupal Commons is bundled into the Feature called Commons, which functionally appears as a module in the site. Note that there is also a Commons Notifications (for email notifications).YesContextProvides a method for Drupal Commons to have different page layouts at various places on the site.AllOptional core modules usedAggregator (for Group RSS feeds), Blog, Book (though not used in V1.1), Color (though not used in V1.1), Comment, Contact, Database logging, Help, Menu, Path, PHP filter (though probably shouldn't be in V1.1..), Poll, Profile, Search (required by Acquia search, and used if Acquia search isn't enabled), Taxonomy, Tracker, Update statusVariousDate/TimeVarious specific modules used for several date-oriented functionsVariousDevelIncluded so that new site owners can use its features during initial deployment. Likely best to disable it on production sites.Devel (only)WikitoolsUses the Tagging module form this for "folksonomy" style taggingTagging (only)FlagsFlag module used for HeartbeatFlag (only)HeartbeatUsed for various recent activity listings. Enabled by default: Flag heartbeat, friendlist activity, heartbeat activity, heartbeat rules, heartbeat views, and organic group activity components.VariousImageCacheUsed for image handling. Enabled by default: ImageAPI, ImageAPI GD2, ImageCache, Imagecache Canvas Actions, Imagecache Profile Pictures, and ImageCache UIVariousMessagingUses the Messaging framework. Enabled by default: Messaging, Simple Mail, Simple messaging.VariousNotificationsProvides notifications for site activity. Enabled by default: Content Notifications, Notifications, Notifications Autosubscribe, Notifications UI, Notifications Views.VariousOrganic GroupsForms the core for the Group organization used in Commons. Enabled by default: Organic groups, Organic groups access control, Organic groups aggregator, Organic groups statistics, Organic groups Views integration.VariousOtherBetter Formats (enabled) (supporting WYSIWYG capabilities), Diff (enabled) (used by Wiki), Encrypt (not enabled) (used by password setup), getID3() (enabled) (for images), Insert (enabled) (for images), Mollom (not enabled, but turned on when the Acquia Network Connector is enabled) (for controlling comment spam), Panels Stylizer (not enabled (part of the panels package?)), Password Policy (enabled) (sets strictness of passwords required), Pathauto (enabled if host system configured to support it during install) (for SEO-friendly URLs), Shoutbox (enabled), Shoutbox Group (enabled), Shoutbox points (enabled), SiteQuant (enabled), Skinr (enabled), Strongarm (enabled), Token (enabled), Token Actions (not enabled), Transliteration (enabled), User Terms (enabled), Wikitools (enabled)VariousPanelsFor page layout. Panels enabled by default; Mini-panels and Panel Nodes not enabled by default.VariousRulesFor conditionally-executed actions. Rules & Rules Admin UI enabled by default; Rules Forms, Rules Scheduler, and Rules Simpletest not enabled.VariousTaxonomyFor content tagging.Tagadelic enabled by default; the rest of the package not enabled.TestingFeatures Tests and Mollom Test included, but not enabledNoUser RelationshipsFor creating "Friend" relationships between users. Lots of modules included in package; only the ones listed to the right are enabled by default.Enabled: UR-API, UR_Blocks, UR-Elaborations, UR-Mailer, UR-Rules, UR-UI, UR-Views.User InterfaceEnabled: Ajax Load, jQuery UI, Vertical Tabs, WYSIWYG. Not enabled: Ajax load example, elFinder, SweaverVariousUserpointsFor enabling users to earn points for contributions. Enabled: Userpoints, Userpoints nodes and comments, Userpoints User Picture. Not enabled: Userpoints rules integration, Userpoints serviceVariousViewsFor creating table-style (and other) "views" of structured content in the Drupal database. NOT enabled: Views exporter.Tagadelic views, Views, Views UI


Comments
New OG change a lot in Drupal7
Very interesting presentation of the new maintner http://www.archive.org/details/GrouptheNewOrganicGroups-BuildingSocialNe...
In pratique for the web builder http://www.youtube.com/watch?v=ajkrSyREjrs&feature=player_embedded
Outdates
This page is outdates, and it doesn't look ok.
Turns out that..
.. there was some pilot error on my part. I used the Full HTML input format, and nobody but me could use that. And only the Full HTML format could use table/tr/td/th. So when other people saved the page, the input format turned back to Filtered, and the table stuff got eaten.
I added table block elements to filtered html. This should be globally editable now - and the format should look good.
Missing the border right in Table
IMHO would look a bit more over-viewable!
I think that Wiki related
I think that Wiki related modules and Userpoints shouldn't be enabled by default, they are VERY optional.
In general, I found with Drupal and DC in particular, one of the development tasks is finding and disabling/hiding functionality which isn't required, to simplify UI and make user experiense easier. It should be other way around.
Could/should we update this wiki?
Commons is now on version 1.6. I updated the module list again a few days ago, then wondered how relevant the list is to the current version. What do you think?
Yes - a basic part of documentation
I think with the modular, extensible approach of drupal and commons such a list is indeed essential. Commons has to be seen as a shop window for drupal to some extent doesn't it? And assuming that people come with different degrees of awareness of the drupal way, a page that shows them how the site is built up from standard components could offer them an important insight into the drupal platform in general.
One particular aspect that deserves consideration is that people may want to extend the functionality of Commons with contrib modules, which they will place in sites/all/modules or some such place. If those contrib modules are subsequently included in Commons as default, perhaps problems will arise if another version is sitting in sites/all/modules as it will take precedence over the one in the main Commons modules directory. Having a list of modules, with perhaps further columns to indicate when the module was introduced, with new modules in the latest release highlighted could avoid such a problem.
Another aspect is whether modules are included but not enabled. For example, with 1.6 forum was included but not enabled ((not included in the list of modules, I notice). Potentially you may need to know whether the status of a module has changed.
PS since realised that forum is in core and so wouldn't logically belong in the list....
Great points and
.. worthy of us marking as a documentation issue. I'm going to tag this post appropriately.
Thanks