The features module enables the capture and management of features in Drupal. A feature is a collection of Drupal entities which taken together satisfy a certain use-case. Features provides a UI and API for taking different site building components from modules with exportables and bundling them together in a single feature module. A feature module is like any other Drupal module except that it declares its components (e.g. views, contexts, CCK fields, etc.) in its .info file so that it can be checked, updated, or reverted programmatically. Examples of features might be: A blogA pressroomAn image galleryAn e-commerce t-shirt store Compatibility Issues The 7.x-2.x version The 2.x branch greatly changes (and hopefully improves) the user interface of the Create/Recreate Features screen. Ability to write your feature export directly to the Drupal file system (like drush fu).Ability to remove auto-detected items from your export.Ability to work with conflicting features. Drupal 8 Documentation
Related: Drupal 7 Modules
Migrate | drupal.orgThe migrate module provides a flexible framework for migrating content into Drupal from other sources (e.g., when converting a web site from another CMS to Drupal). Out-of-the-box, support for creating core Drupal objects such as nodes, users, files, terms, and comments are included - it can easily be extended for migrating other kinds of content. Content is imported and rolled back using a bundled web interface (Migrate UI module) or included Drush commands (strongly recommended). Status I'm afraid I've been very busy with project work and the Migrate in 8 effort and haven't been able to put Migrate 2.6 to bed yet. Migrate 2.6 Release Candidate 1 is available. The most significant changes in Migrate 2.6: For a more complete list of changes, see the issues tagged as Migrate 2.6. Besides the UI changes, there are significant changes around migration registration and construction that are somewhat risky - before upgrading to the latest -dev or git code, be sure you backup your database.
Field PermissionsThe Field Permissions module allows site administrators to set field-level permissions to edit, view and create fields on any entity. Features Enable field permissions on any entity, not just nodes.Role-based field permissions allowing different viewing patterned based on what access the user has.Author-level permissions allow viewing and editing of fields based on who the entity owner is.Permissions for each field are not enabled by default. Requirements CCK (Drupal 6 only) Instructions Once Field Permissions module is installed, you need to edit the field settings form to enable permissions for each field where you need this feature. Create own value for the fieldEdit own value for the fieldEdit anyone's value for the fieldView own value for the fieldView anyone's value for the field Use these options to enable role based permissions for each field. Upgrade path from Content Permissions (D6) Get Involved Notable Credits
DiffThis module adds a tab for sufficiently permissioned users. The tab shows all revisions like standard Drupal but it also allows pretty viewing of all added/changed/deleted words between revisions. Active maintainer/s Brian Gilbert (realityloop)Alan Davison (Alan D.)Lucian Hangea (lhangea) - Drupal 8 Port Inactive maintainer/s Young Hahn (yhahn)Tim Altman (Junyor)Derek Wright (dww)rötzi Previous maintainers Moshe Weitzman (moshe) Refer to the readme.txt for configuration options.CMIS APIThe CMIS API project aims to provide a generic API for integrating with CMIS compliant Enterprise CMS (ECM) systems. This is a joint effort between Optaros, Acquia, and Alfresco. What This Module Package Does The CMIS API package of modules primarily provides an API for connecting to CMIS compliant systems to bi-directionally synchronize content between the CMIS ECM system and Drupal. While this module does provide interfaces and functionality out of the box, most developers doing advanced integrations will want to create custom modules that invoke the included API for custom authentication, sync, content type extension, etc. What's Included The CMIS Module Package includes the following modules: Dependencies (7.x-2.x) The 7.x-2.x branch no longer has the PHP CMIS Library included in the distribution, it's loaded using the Libraries API module, please download from Apache Chemistry When to Use This Module Resources Getting Started with CMIS - Credits
Creating an image gallery in Drupal 7 | MegaDrupalCreate an image gallery in Drupal is not difficult, you can use some modules but they're often more than you need and sometime difficult to tweak. I will show you how to create a gallery page that you could easily modify or customize. Overview Through the tutorial I'm going to show you how to create an image gallery page on Bartik (Drupal's default theme) theme. Yes, you can use any theme you want. Demo for this tutorial here. Requirements For this tutorial you will need to install Drupal 7 (because this tutorial for Drupal 7. Step 1: Create custom content type Go to Structure -> Content Types (/admin/structure/types) and add a new content type called Gallery (remember this machine name for step 5). Step 2: Create image style From admin toolbar, go to Configuration -> Image Styles (your_site/admin/config/media/image-styles), add new style name "gallery-thumb". Step 3: Manage fields Delete body field and add new "Image Gallery" field. Next, click to "manage display" next Gallery content type
Migrating D6 (CCK) to D7 FieldsLast updated December 26, 2013. Created on May 1, 2011.Edited by flaviovs, LWVMD, colan, Edgar Saumell. Log in to edit this page. Data must be migrated to upgrade Content Construction Kit (CCK) in Drupal 6 to Drupal 7 core fields. Node Reference and User Reference are replaced by either the References module or the Entity Reference module. The following instructions describe the steps necessary to migrate CCK for a site that was upgraded from Drupal 6 to Drupal 7. Browse to Structure > Migrate Fields or Check the box next to all fields you would like to migrate in the Available fields section. Press the Migrate selected fields button. If the migration process is successful you should receive a message detailing that each field was created. Looking for support?
Style GuideProvides a visual testing page for Drupal themes. Quickly compare the display of common elements across your themes, and verify that your new theme addresses all common style elements. The Style Guide module creates a preview page for displaying common theme elements in all active themes for your Drupal site. Demo site You can see the module in action at the demo site built by davidneedham. Usage example By placing common elements outside their normal context, developers and themers can quickly scan HTML output for design consistency. When displayed within the Style Guide, catching such inconsistencies in your theme(s) becomes easier. Color Palette An editable color palette is now available for color swatches to manually be added per theme. Extensibility Themers and module developers may extend the module by using hook_styleguide() to add new elements to the preview display. hook_styleguide_alter() can be used to change the behavior of existing preview elements. Sample API usage