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.
Content Templates (Contemplate) NOTE: This module *may* be deprecated in Drupal 7 ! Here's your reason, basically the theming changes in D7 mean the field theming gets bound a lot lot later in the process, so it's not possible to generate the output into a Textarea for you to edit - that said, it is possible that we can come at this from another angle and use tokens instead BUT it means what you see in contemplate admin page will be nothing at all similar to the output. You can view more on taking this module forwards here The Content Template (a.k.a. This module was written to solve a need with the Content Construction Kit (CCK), where it had a tendency toward outputting content in a not-very-pretty way. But Content Template can actually be used on any node type and allows modification of the teaser and body properties before they go out in an RSS feed, search index, or are handed off to the theme.
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.
CCK List This module adds a CCK list field type, that lets you add a list display to any content type, without having to manually enter HTML. To be more specific, it adds a textarea field. Every row in the textarea will be a list point. The output is generated by the theme system, so you don't have to worry about forming valid HTML or adding all those little classes yourself. Under the cck(d6)/fields(d7) display option you can choose to display the list as an ordered or unordered list. This module behaves like CCK Table. This module is sponsored by Themes 24/7 and is developed by Tyler Struyk 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. 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.
CCK Select Other CCK Select Other introduces an alternative select list widget that provides a user with either a select list or text input. Features Supports most list_type fields except boolean, which allows to swap out the select widget at any time.Provides field formatterDrupal 6/7: Removes the need to use "Allowed Values" text area. It is supported, but not recommended.Supports Field CollectionViews filter and field support Known issues i18n is not supported because i18n does not support form element children correctly. Release status 8.x-1.x: Initial development completed (from the last 6 months of struggling with figuring out how to override core's Constraint validator).7.x-2.x: Better support for field collection, list_integer.7.x-1.x: 1.1 stable released. Drupal 8: How it works The decoupling of fields and widgets caused much issue with this module as a field no longer understands what widget a value came from. Drupal 6: How it works CCK renders the form element as fieldset with multiple elements.
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.
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:
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. 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?