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.
Feeds Import or aggregate data as nodes, users, taxonomy terms or simple database records. One-off imports and periodic aggregation of contentImport or aggregate RSS/Atom feedsImport or aggregate CSV filesImport or aggregate OPML filesPubSubHubbub supportCreate nodes, users, taxonomy terms or simple database records from importExtensible to import any other kind of contentGranular mapping of input elements to Drupal content elementsExportable configurationsBatched import for large files Installation For requirements and installation instructions, refer to the included README.txt file. Documentation For a guide to using Feeds in site builds or how to develop for Feeds, see the Feeds documentation. 8.x It's not ready yet. Addendum: There's 500 people using 8.x. 7.x This should be very stable. 6.x We (me twistor) have closed out all of the 6.x issues. Feeds powers the news tracker Managing News.
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.
Megamenu Notes: This module is in beta and under active development. Use on production sites at your own risk, and use caution when upgrading.7.x-2.x is the active development branch--new features go here6.x and 7.x-1.x branches are now bugfix only. Overview Mega menus are a type of drop-down, which seeks to overcome some of the usability drawbacks to traditional style drop-downs. The information architecture of your navigation is made clearer and is visible all at onceThe amount of clicking, searching, and navigating is reduced This module allows you to build mega menus by leveraging jQuery and the existing Drupal menu system. Shown to the right is an example of a mega menu taken from actionenvelope.com. What's the deal with Megas? What does this module do? This module takes any existing Drupal menu and produces the markup for a megamenu. Features Who is this module for? Who is using this module? Here are a few examples of what people are doing with this module. How can I contribute? Update notes: 7.x-2.x
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
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:
SimpleMenu Description This module creates a menu bar that is displayed at the top of every page. The menu bar is fixed in place and uses jQuery to position the bar, along with handling menu effects and adding IE compatibility. Very useful for themes that don't have a good place to put the navigation menu (although it can be used with any menu.) Documentation direct links SimpleMenu settings SimpleMenu Documentation & Known Issues I removed the upgrade information as it shouldn't matter as much now. Related Modules (if you have a module that you think is related, submit an issue and I will add it here) Cute Menu — Cute Menu is also a drop down featured menu. Mini-features modules — gives you some extra features not otherwise found in any module because those are so... mini! Nice menus — gives you a set of drop-down menus in a block for each one of your menus. Floating Manager Menu — gives you a nice little vertical menu window that you can drag anywhere you want on your page. Known issues Sponsor
stickynote | drupal.org - (Private Browsing) This module is meant to be a utility module for content admins. It could be useful for content authors/admins to communicate with one another about their content or keep a todo list on pages, thus the name stickynote. How it works This module simply creates a block with the ability to add, delete, and edit notes (ajaxified). Notes are stored on a per path basis and the block can be made visible to certain roles/paths etc... like any other block. Demo Try out the stickynote module now at the demo site. Differences from sticky_notes module: This module creates a block and allows adding/editing/deleting in the block rather than using the modal frame api and jquery ui to display the note. Please see the sticky_notes module (d6 only) to decide which solution meets your needs as they are very different approaches. Future plans: Drupal 8 can do this in core! Views + Content + Edit = Stickynotes! Note: A D6 Backport is not planned. Security Update:
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?
LESS CSS Preprocessor This is a preprocessor for LESS files. Built using the lessphp library by Leaf Corcoran. This module will automatically process any LESS files that are added using drupal_add_css or added through your theme's .info file. Add your files just like any other css file, just with .less as the extension, and they will be automatically processed. 7.x-3.0 New Features There are several new features: Live style reloadVariables editable in UI per themeCustom LESS functionsCorrect relative path @import'sDemo module included The included less_demo module should provide API demonstration for new features. Installation Download & Install Libraries API.Download lessphp and unpack it so that 'lessc.inc.php' is located at 'sites/all/libraries/lessphp/lessc.inc.php'.Download and install (this) module. Compatibility: Fully compatible with CSS aggregation: Drupal 6 "Optimize CSS files" setting under "Administer→Site configuration→Performance" (admin/settings/performance). LESS Development: Syntax File placement Apido
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.