Token Tokens are small bits of text that can be placed into larger documents via simple placeholders, like %site-name or [user]. The Token module provides a central API for modules to use these tokens, and expose their own token values. Note that Token module doesn't provide any visible functions to the user on its own, it just provides token handling services for other modules. For Drupal 6, the Token module provides a "Token Actions" module which can be enabled separately. This provides several "actions" for the Drupal core Actions/Trigger modules to use that take advantage of the Token replacement functionality. Modules that use the Token module and provide tokens via the API include Organic Groups, Pathauto, Comment Notify, and Commerce. Pledges #D7CX: The basic token API is now a part of Drupal 7! #D7AX - I pledge to make this module as accessible as it can be.
Panels An Overview of Panels The Panels module allows a site administrator to create customized layouts for multiple uses. At its core it is a drag and drop content manager that lets you visually design a layout and place content within that layout. Integration with other systems allows you to create nodes that use this, landing pages that use this, and even override system pages such as taxonomy and the node page so that you can customize the layout of your site with very fine grained permissions. Integration with CTools module Panels 3 utilizes the CTools' system of "context" so that the content you place on the page can be aware of what is being displayed. Panels uses Contexts - What are they? In a Panel, you can create contexts, which represent the objects being displayed. In addition, these contexts can be checked for information and use that not only to make content available to be displayed, but to choose which layout to display! Panels can also be used for items smaller than pages.
References This project provides D7 versions of the 'node_reference' and 'user_reference' field types, that were part of the CCK package in D6, at functional parity with the D6 counterparts. See for details. Note for users upgrading from References 7.x-2.0-beta3 There were a couple changes in the way 'References' views are handled ("referenceable nodes/users defined by a view"), which might require double-checking those existing on your site: The 'label' (node title or user name) is no longer automatically added if not included in the view. Note for users upgrading from CCK D6 The References project integrates with the content_migrate module present in CCK 7.x-2.x-dev to allow the migration of field definitions and field values from D6 nodereference and userreference fields. Similar modules:
CCK Blocks Field Visibility and Display Modes: Since version 6.x-1.1 , the module does not hide the field in the node's content area anymore. You can do that for yourself in the display settings for your content type. CCK blocks will define a display mode named "CCK Blocks", which you can use to configure the display of fields when they are appearing as blocks. This allows you show the field both in the node's content area and in the CCK block, with different display settings. IMPORTANT: Before any of your CCK blocks will show up, you need to set the field in question to be visible in the CCK blocks display mode! Performance and Caching: Since many users have experienced tremendous problems when block caching is activated (#400858: CCK Blocks appears to be incompatible with block caching), we decided to disable block caching for cck blocks. If you wish to have block caching, please use the Block Cache Alter module to activate block caching for individual cck blocks. Tokens [node:field_yourfieldname] 1.
Migrating D6 (CCK) to D7 Fields Last 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. Much but not all of CCK functionality is now part of Drupal 7 core. 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?
Field Permissions The 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. Instead, administrators can enable these permissions explicitly for the fields where this feature is needed.Field permissions overview 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.
Features 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
Migrate The 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. I am starting to catch up on the issue queue, aiming to answer a few issues at a time, a few times a week, prioritizing bugs>support requests>tasks/feature requests. 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. Requirements Support for contributed modules
Post It Everywhere Now you don't need login to different social networks to post status updates. Just one click and your content will be posted to Facebook Twitter LinkedIn FriendFeed The most common way to make your site popular is by posting your content to different social networks. Here is a new and simple way for publishing content to different social networks. Features: The link "Post it Everywhere!" We would love to hear if you used this module in your application. Requirements: Developed By: Confiz Solutions Location Module maintainer @podarok The Location module allows real-world geographic locations to be associated with Drupal nodes, including people, places, and other content. The Location module allows admins to collect addresses, geocode them (translate addresses to lattitude/longitude), and associate locations with Drupal nodes and users. We need help from developers with #1931088: [META] Fixing tests #1940818: [META] Location 7.x-3.2 release roadmap#2127933: [META][SPRINT][Location] Documentation sprint At present, it is the only module that provides the views integration necessary for implementing location-based searches and is designed for the purpose of finding points on a map within a vicinity of a user-supplied location. If updating from earlier versions and using location search, make sure to check these permissions. We need help from developers with #1931088: [META] Fixing tests #1940818: [META] Location 7.x-3.2 release roadmap Location now includes the following modules: Drupal 8 porting
CCK field with Views Sometimes in Drupal you’d like a field that pulls data from other fields, possibly other content types or who knows. If it’s relatively simple, you can use the Computed Field module to pull data straight from the database. But if you want to get really tricky, you can use the Node Reference Views module. For example, let’s say you want to include the weights of individual components of an item, so you get a dropdown list of components to choose from, then once you’ve chosen them, they will be displayed in your field formatted as you’ve selected in your View. In other words, imagine that you’re formatting a list of components using Views as you might normally do, but now you insert that in your node as a field. So in short you use Node Reference to set the source of the data and you use Node Reference Views to set the format of the data. Enable both modules. Now, add a new field to your content type. Choose your content types This field name must be your view name as well (click to enlarge)
Family Tree Please note: This module currently has no way of outputting GEDCOM compliant data. The Family Tree module is for recording, displaying and analyzing genealogical data. It allows for the creation of things (nodes), such as Individual peopleFamily "groups" (marriages, unions, parents, children, etc.)Customized locations (e.g. place of union, etc.), events (e.g. divorce, etc.), artifact data records and linkingA lot more Dependencies: 6.x-1.x is the current new feature branch of Family Tree. Here is a more in-depth feature list: Node types for individuals, family groups, and locations.Views integration and Token support.Relationship assignment.Link users to individualsGraphs for ascendancy and descendancy.Full support for access control by Drupal roles and permissions.GED file import. Proposed future feature additions in no particular order: The Family Tree module is now maintained by jerdiggity, and was previously maintained by Pyutaros' with extensive co-maintainership by Microbe.
Diff This 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. Drupal Charting I needed to find a way to create nice charts from Views data so that end users could adapt them to selected date ranges or categories, but I found that this is not as easy as it ought to be. It took quite a bit of time just to figure out what the options were, let alone decide which were the most promising solutions for my situation. Since this turned into such a time-consuming project, I've documented the steps I took and what I found to make things easier for anyone else looking for solutions like this. I investigated several Drupal 6x modules to see which ones might be ready for prime time. I checked a few statistics to evaluate how useful, popular, and well maintained each module is. The names and dependencies are especially confusing. I created some numeric and text data using CCK fields and auto-filled them using the Devel Generate module, then tried to chart my data in various modules. The end result in Google Charts looked like the following: Charts