background preloader

Drupal 6 Modules

Facebook Twitter

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.

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. To use Entity Reference (as it's better maintained and more sustainable), it's necessary to migrate to References first, and then use the Reference to Entity Reference Field Migration module.Content permissions require the Field Permissions module ( Groups require the Field Group ( module.

The following instructions describe the steps necessary to migrate CCK for a site that was upgraded from Drupal 6 to Drupal 7. Wordpress Import. Import HTML. Node Convert. Node Convert adds a menu tab "Convert" on the node view page, i.e. node/1/convert, which gives the ability to convert the node from its current node type to another node type. The module provides the means to transfer all the field values of the current node type into fields on the destination node type, or discard them. The module integrates with Actions, Rules, Views Bulk Operations and Admin Views nicely. It has support for exporting templates into Features using CTools Exportables. It also provides a hook that enables developers to execute additional code on conversion. Currently the module provides additional behavior for properly converting nodes for the following modules: - XMLSitemap Patches for additional behaviors are welcome.

The module has been tested on converting node types with the following field types: TextNumberImageFileNode referenceUser referenceTerm referenceEntity referenceLinkDateDatestampEmail. 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. How to use Node export There are several ways to use Node export: Through a tab that appears on the node page.Using update options on the Content page.In a command line using Drush.Using the Features module.Using the Views Bulk Operations module. Nodes exported with Node export can be imported: Node export formats The format to export with is configurable, and the Node export package comes with the following formats: JSON - JavaScript Object Notation code which is known for being security friendly. Taxonomy. Taxonomy import/export. 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. Examples include taxonomy structures of: Hierarchical Countries and states The Dewey Decimal system Library of Congress classification scheme IPTC press topic catalog Encyclopedia of Life organism database Background on recent motivations that have moved this forward a bit. Documentation distributed with the module includes:

About nodes. 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. It also allows you to painlessly apply new features or changes to all content. Behind the scenes, the Node module manages these nodes. List, sort through, and manage all the content on your site.Set defaults for how all posts are displayed.List and configure the "content types" for your site, and create new ones. Offering "content types" is a way Drupal allows you to have different kinds of nodes for different purposes.

The Node module manages the creation, editing, deletion, settings, and display of the main site content. Each node has an unique ID. Creating content Creating custom content types Administering content Creating revisions User permissions. Theming Guide. Last updated November 4, 2015. Created on August 2, 2012.Edited by reendeer, chriscerk, ashish_nirmohi, mh9. Log in to edit this page. This community documentation guide is about changing the look and feel of a Drupal site.

The guide covers Drupal 6 & 7 and Drupal 8. Changing Site Appearance In the administrative settings you can modify the appearance of the theme in 3 ways. Simply find a prefabricated provided by Drupal or get one on a third party website and modify the theme settings Copy an existing theme and then change or extend the codeBuild a complete theme from scratch (For doing this you need to copy files from core theme and place it under sites/all/themes and do the necessary changes on .info, template, tpl and css files.)

What else can you do? You can do more with a theme than change the appearance of an entire site. Some other things that you can also do with a theme are: Other Places to Explore Looking for support? Blocks. 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.

Pretty simple, eh? #D7AX/#DAX - I pledge to make this module as accessible as it can be. Related modules DHTML menu: Makes any of Drupal's standard menu trees have dynamically expanding menu items. Nice menus: Provides blocks of fly-out expandable menu trees. 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. Drupal 7 Uses In Drupal 7, you can add, remove and rename menus and menu items/tabs.

In many themes there are at least two menus, the Main (or primary) menu, and a secondary menu. When adding or editing site content, you can also specify the content's menu item. Each default or custom menu has a corresponding block. Configuration Creating a menu Navigate to the Menus page (Structure > Menus or Enable the menu Specify the menus to use for main and secondary links Renaming menus. Menu Settings per Content Type. Custom breadcrumbs. Custom Breadcrumbs 2 (6.x-2.x and 7.x-2.x) Many new features have been added including support for Views, Panels, Taxonomy vocabularies and terms, paths, and a simple API that allows contributed modules to enable custom breadcrumbs for module pages and theme templates.

These are implemented using optional, independent submodules that depend on the main Custom Breadcrumbs module. In addition to breadcrumb visibility, this version provides an option permitting PHP code snippets to be used in forming the breadcrumb titles and paths. Multiple languages are also supported. Any changes must go in the 7.x version first. Custom Breadcrumbs 1 (6.x-1.x and 7.x-1.x) Allows administrators to set up parametrized breadcrumb trails for any node type. There are no maintainers doing any work on these branches, so please switch to version 2! Similar Modules There is also the Path Breadcrumbs (PB) module. Dynamic display block. 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. Similarly, a ddebug_backtrace() is offerred.much more. See this helpful demo 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. Content types and fields. In Drupal, a Content Type is a pre-defined collection of data types (Fields) which relate to each other by an informational context. In this sense, "context" means "parts that should be considered as a correlated whole.

" Content Types are how site editors can input original content on a Drupal site, and are the building blocks for structured authoring and content. Content types often work in conjunction with Views, which is one way you can serve up content to your end users; you can control the content types that appear and the order in which they appear.

Developers can also customize the authoring experience in the same way. One way to think of content types is to visualize the contacts on your mobile phone. If you were to duplicate this on a Drupal site you would create a Content Type. The Field UI module provides an administrative user interface (UI) for attaching and managing fields. Managing fields with the Field UI Uses Planning fields Reusing fields Remove field Versions Drupal 7. About content types. In Drupal, a Content Type is a pre-defined collection of data types (Fields) which relate to each other by an informational context. In this sense, "context" means "parts that should be considered as a correlated whole. " Content Types are how site editors can input original content on a Drupal site; while Views, for example, is one way you can serve up content to your end users.

A developer (or an administrator, with the help of CCK) can add new Content Types to collect specific information for display. Also, existing Content Types can be "extended" by adding additional Fields. Drupal 6 "ships" with two initial Content Types (Page and Story). All posts that exist on the site are instances of a content type: Each time you create a post (page, story etc.), a content type is being used to hold and form the items you enter. Drupal core content types: Drupal comes with two pre-configured default content types with different default configured behaviors.

Identification: Workflow settings: <? Wikitools. 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. While the 4.7 and 5.x-1.x branches are stable release branches at this point, only 5.x-3.x included node creation AND node relationships.

The entire database and module structure was scrapped after 5.x-1.4 for a complete redesign. Here is a more in-depth feature list: Proposed future feature additions in no particular order: Export to GED file.Make module fields available to Views and CCK.Date and Calendar integration.Family record privacy.Tighter relationship integration with nodes and users. Bible. Files and Multimedia. Media. The Media module provides an extensible framework for managing files and multimedia assets, regardless of whether they are hosted on your own site or a 3rd party site - it is commonly referred to as a 'file browser to the internet'. Media is a drop-in replacement for the Drupal core upload field with a unified User Interface where editors and administrators can upload, manage, and reuse files and multimedia assets.

Any files uploaded before Media was enabled will automatically take advantage of the many of the features it comes with. Media's aim is to solve Drupal's long standing media handling problem. Drupal 7 installation Quick install: Follow this recipe, or see online installation documentation. Drupal 8 Media for Drupal 8 is undergoing a re-architecture to individual components. Thank you Aaron Without his kindness, generosity, humility, and dedication, this module and many many others would not have been possible. You will be missed, friend. What is the difference between 1.x and 2.x? Video. Post It Everywhere. SexyBookmarks. Flickr Sync. Drupal Photo Gallery Using Flickr. Gallery formatter. Facebook Connect. Better Formats. Charts. Drupal Charting. Data Visualization Demo. Google chart API. Wysiwyg. Node form columns. Page Title. Automatic Nodetitles. Drag'n'Drop Uploads.

Diff. Revisioning. RealName. Organic groups. CCK. Field API. Viewfield. Compound Field. Computed Field. Field Permissions. CCK Blocks. Token. References. Block reference. Panels. Views. View reference. CCK field with Views. Views attach.

Chaos tool suite. Strongarm. String Overrides. SPARQL Views. Views Slideshow. Users. User Points. User Badges. LoginToboggan. UserDashboard. Notifications. Workbench. Flag. Nodequeue. Publish Content. Services documentation. Services. Ubercart. Rooms. Securing your site. Mollom. New York State Senate. Whitehouse.gov Modules. Storm. Features. Location. GMap Module. Spaces. Spaces: A Paradigm. Fast 404.