Drupal modules

Get flash to fully experience Pearltrees

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, and comments is included - it can easily be extended for migrating other kinds of content. Content is imported and rolled back using Drush commands. Requirements

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. The following instructions describe the steps necessary to migrate CCK for a site that was upgraded from Drupal 6 to Drupal 7. Learn more on upgrading from Drupal 6 to Drupal 7. Download latest 7.x CCK module

Migrating D6 (CCK) to D7 Fields

Wordpress Import

Security issue : All versions of this module prior to 6.x-2.1 are affected by an access bypass vulnerability . If you use version 6.x-1.x or 6.x-2.0, please either upgrade to the latest version or simply deactivate the module if the import functionality isn't needed anymore. User passwords aren't transferred from WordPress, a password for new users must be set after importing.

Import an old existing, static HTML site structure into the Drupal CMS as structured nodes! Allows an admin to define a source directory of an existing traditional static HTML website, and import (as much as possible) the content and structure into a drupal site. Update: there is now an automatic installer for HTMLTidy bundled in for Linux hosts. There are at least three flavours of tidy extensions for PHP , not including the commandline alternative. The PHP5 binary distributed version has been targeted, the PECL one can be made to work with some tweaks . See the help document for details.

Import HTML

Node Convert adds a menu tab "Convert" on the node view page, i.e. node/1/convert, which gives the ability of converting the node from its current node type to another node type. Also it gives the ability of transfering all the custom CCK field values of the current node type to the destination CCK fields, or discard them. As of 5.x-1.4 you can bulk convert many nodes of the same type, to another one that can be accesed in Administer → Content → Convert Nodes.

Node Convert

Node export

This module allows users to export nodes and then import it into another Drupal installation, or on the same site. Using this module you can save yourself a lot of time setting up new websites that have similar nodes to websites you've already made, migrating nodes to new Drupal versions, or between development/staging/production sites. You will need the same content types for the imports to work (unless using Feeds to import), and ideally relevant compatibility with fields, and modules. To migrate nodes from Drupal 6 to Drupal 7 use latest versions of 6.x-3.x and 7.x-3.x. To import; you must enable Node export feeds and import via the Feeds interface.

Taxonomy

What is seriously missing is a way to enforce these relationships at node creation, especially if you need to be able to add child terms at node creation.

This module makes it possible to import and export vocabularies and taxonomy terms via XML, CSV, RDF and other formats. If you want to just import a flat list of terms, or terms structured in various columns to represent heirarchy, Taxonomy CSV offers a number of CSV-style formats and the ability to just paste the list straight in. Try that for simpler jobs. CSV support in taxonomy_xml is limited to a specific (ISO 2788 - triples) format Work is currently being done in the Drupal 6 branch to extend support for remote services - online vocabulary, glossary, thesaurus and taxonomy resources - so libraries of structured terms can be imported directly. A goal is to get the taxonomy import/export to a point where a Drupal site can become a taxonomy server of its own, providing realtime vocabulary sharing.

Taxonomy import/export

http://drupal.org/documentation/modules/node

All content on a Drupal website is stored and treated as "nodes." A node is any posting, such as a page, poll, article, forum topic, or blog entry. Comments are not stored as nodes but are always tied to one. Treating all content as nodes allows the flexibility of creating new types of content.

About nodes

This handbook is about customizing the look and feel of a Drupal site. We'll show you how you can modify the appearance of your Drupal site without requiring expert knowledge of programming. And if you wish to go further, we cover that too. This guide assumes some knowledge of HTML and CSS but no PHP programming knowledge is necessary.

Theming Guide

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. Similarly, a ddebug_backtrace() is offerred.

Blocks

Blocks are the boxes visible in the sidebar(s) of your Drupal website. Most blocks (e.g., recent forum topics) are generated on-the-fly by various Drupal modules, but they can be created in the administer blocks area of a Drupal site. Whether, and where, a given block will appear on a page depends on both the theme enabled and on administrative block settings. Block settings are controlled from the block administration screen, reachable by clicking administer » site building » blocks . From this screen, it is possible to control whether each block is enabled where it will be placed on the page, and control the visibility of blocks on each page.

Menu block

So… have you ever used the Main and Secondary menu links feature on your theme and wondered “how the hell do I display any menu items deeper than that?” Well, that’s what this module does. It provides configurable blocks of menu trees starting with any level of any menu. And more! So if you’re only using your theme’s Main menu links feature, you can add and configure a “Main menu (levels 2+)” block. That block would appear once you were on one of the Main menu’s pages and would show the menu tree for the 2nd level (and deeper) of your Main menu and would expand as you traversed down the tree.

Menus

Menus are a collection of links (menu items) used to navigate a website. The Menu module provides an interface to control and customize the powerful menu system that comes with Drupal. Menus are primarily displayed as a hierarchical list of links using Drupal's highly flexible blocks feature. Each menu automatically creates a block of the same name. By default, new menu items are placed inside a built-in menu labeled Navigation, but administrators can also create custom menus.

Menu Settings per Content Type

example1 : I want that the menu-settings just show up on content-type "page" and not on other content-types. so that users wont be confused to have these settings where they dont make sense. example2 : for the "Images" content Type I want to have only "Images" Menu available for "images" content. Once installed the Menu Settings will not available in Node Edit Form until you set the Menus we want in the Content Type Settings (Administer > Content management > Content types > TheContentType edit)