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 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 also includes simpler applications of the drag and drop system. Panels can also be used for items smaller than pages. Other Features of Panels Panels supports styles, which can control how individual content panes, regions within a panel, and the entire panel will be rendered. Known Issues Status of Panels
Weight This module adds a weight option to enabled node types. Nodes with lower weight will float to the top of lists, while heavier items will sink. You might be interested in reading Comparison of Node Ordering Modules. This is useful for sorting non-chronological nodes like bios, e-commerce products, or whatever you would like. Nodes will be sorted first by stickiness, then by weight, then by creation date. With support for 7.x, the support for 5.x ends. Version 7.x-2.x is currently the recommended and supported release for Drupal 7. Issues As with all contributed modules, when considering submitting an issue: Read the documentation (two or three times is better). Development version status The development versions (-dev, which rolls up at Noon and Midnight GMT) are where the newest stuff is, including any bug fixes and new features.
Devel A suite of modules containing fun for module developers and themers ... Devel Helper functions for Drupal developers and inquisitive admins. This module can print a summary of all database queries for each page request at the bottom of each page. The summary includes how many times each query was executed on a page (shouldn't run same query multiple times), and how long each query took (short is good - use cache for complex queries).Also a dprint_r($array) function is provided, which pretty prints arrays. Useful during development. Generate content Accelerate development of your site or module by quickly generating nodes, comments, terms, users, and more. Devel Node Access (DNA) View the node access entries for the node(s) that are shown on a page.
Chaos tool suite (ctools) This suite is primarily a set of APIs and tools to improve the developer experience. It also contains a module called the Page Manager whose job is to manage pages. In particular it manages panel pages, but as it grows it will be able to manage far more than just Panels. For the moment, it includes the following tools: Plugins -- tools to make it easy for modules to let other modules implement plugins from .inc files. Exportables -- tools to make it easier for modules to have objects that live in database or live in code, such as 'default views'.
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:
Entity API This module extends the entity API of Drupal core in order to provide a unified way to deal with entities and their properties. Additionally, it provides an entity CRUD controller, which helps simplifying the creation of new entity types. Requirements Drupal 7.2 or later; suggested Drupal >= 7.15 Documentation You can find documentation in the handbooks. Overview For site-builders This is an API module, so it doesn't provide any end-user features. A Views display plugin and field to render or link to any entity (by view-mode)A CTools content plugin to render any entity (by view-mode)It ships with the Entity tokens module which makes sure there are tokens for most entity properties and fields, i.e. it provides token replacements for all entity properties (or fields) that have no tokens and are known to the entity module (read about the entity property info API below). For developers Changes Credits The project has been sponsored by Maintainer Wolfgang Ziegler (fago)
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.
Content Access What is Content Access? Yet another content access module. This module allows you to manage permissions for content types by role and author. Features It comes with sensible defaults, so you need not configure anything and everything stays workingIt is as flexible as you want. So the module is simple to use, but can be configured to provide really fine-grained permissions! How To? Itangalo (Johan Falk) has recorded a great Learn Content Access series.The online handbook documentation.If you are interested in the Drupal 6 version, you can read more about it in its introductionary blog post. Notes {*style:<ul>*}{*style:<li>*}Content access makes use of Drupal's node access API.
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. Several features require the installation of new, dedicated 7.x modules. 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?
simplehtmldom API What this module is and what it does This is a bridge between the latest version of the PHP Simple HTML DOM Parser (simplehtmldom) library - so that Drupal developers can easily write their modules using its API. What the library does is that it gives you the simplest way to parse the html DOM tree whenever you need to parse html: in your drupal input filtersin hook_alter();when migrating html sites to drupal Easy html parsing Have you ever wanted to do some str_replace (or maybe just extract it) only over the plaintext part of a html document? Installation and Usage For 7.x-2.x and 6.x-2.x please download simplehtmldom library (README.txt) Download and enable the module. Usage example for Drupal 7: (use in your module's code) <? Here are the docs: Modules using it: Authors and maintainers: Versions 6.x-2.x and 7.x-2.x:
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. 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. The 7.x-2.x version is very compatible with feature exports created from the 7.x-1.x version. There are currently no plans to port this new interface or new functionality to Drupal 6. Drupal 8 Documentation Related Modules Other resources
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. 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.