background preloader

Gallery formatter

Gallery formatter

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

Workbench Workbench provides overall improvements for managing content that Drupal does not provide out of the box. Workbench gives us three important solutions: a unified and simplified user interface for users who ONLY have to work with content. This decreases training and support time.the ability to control who has access to edit any content based on an organization's structure not the web site structurea customizable editorial workflow that integrates with the access control feature described above or works independently on its own These features benefit the end users as well as Drupal Site Administrators and Technical Support. For Drupal Developers and Site Builders, Workbench provides several additional benefits: a modular architecture: only install and enable the modules you wantextensibility: we would love to see more integration with other Drupal modules (in fact we have our eyes on Scheduler and Workflow modules and improvements for Asset Management) Related Modules Workbench Modules Sponsors

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.

SPARQL Views Description SPARQL Views allows you to use Views to access remote and local SPARQL endpoints. In the near future, it will also work for RDFa on Web pages and hopefully microdata. Once the data is in Views, you can use Views style and display plugins to format your data. Requirements Entity API beta9 or later Tutorials Acknowledgements development sponsored by Google Summer of Code and by the LATC Project, support action for Linked Open Data Around-the-ClockDocumentation sponsored in part by Kasabi.Some features sponsored by Oslo Municipality, Centre for Norwegian Popular Music

RealName The RealName module allows the administrator to choose fields from the user profile that will be used to add a "real name" element (method) to a user object. Hook_user is used to automatically add this to any user object that is loaded. It will also optionally set all nodes and comments to show this name. Drupal 7 The module underwent a major rewrite and simplification for Drupal 7 and now depends on the core token API and the Token module for its functionality. Drupal 7 core also now provides a central function that should be used to output a user's name: format_username() thanks to issue #192056: User's raw login name should not be output directly which was accepted into Drupal 7. Drupal 6 The 6.x version of this module supports both the core Profile module and the contributed Content Profile module, and can be extended to other profile providers.

UserDashboard The User Dashboard module forks Drupal 7's awesome Dashboard module to provide an individual dashboard for each user on the site. Users can access their dashboards at the /user/dashboard (or /user/[uid]/dashboard) page, and take advantage of the same drag & drop functionality as in the original Dashboard module. Administrators can configure which blocks can be used on the user dashboard via the settings form at /admin/dashboard/user_dashboard/settings. Release notes: 7.x-1.0 - initial release 7.x-1.0.1 - bug fixes 7.x-1.0.2 - bug fixes 7.x-1.0.3 - bug fixes 7.x-1.1 - added "default blocks" functionality to set the blocks initially shown for new users 7.x-1.1.1 - removed leftover debugging code - added README.txt - added permission handling for user dashboard pages 7.x-1.2 - identical to 7.x-1.1.1, but moved over to Drupal.org; bumped version number to clearly differentiate between the two copies; 7.x-1.3 - Fix bug when moving blocks - Add CSS to match the original dashboard layout Credits

Page Title The word "title" is a bit overloaded. Every piece of content in Drupal has a title, and so does every page. The page title is the one found in the HTML head inside the <title> tag. This module gives you granular control over the page title. Page Title 2 What features are in Page Title 2? Token Integration: This module integrates with the fantastic Token module. Handy modules which work with Page Title There are now a few modules which help you use Page Title to get the best out of your SEO. Content Optimizer - provides you with an inline keyword analysis of your content.SEO Friend - Generate reports of content SEO across the site (eg, which pages are missing Page Titles or Meta Tags) Testing The Drupal 6 and 7 branches now both come equipped with a SimpleTest. Page Title API Introduced in version 2.4, the module now has an API. The 3 hooks are: hook_page_title_pattern_alter(&$pattern, &$types)hook_page_title_alter(&$title)hook_page_title_settings() Drupal version specific notes Drupal 5 Drupal 6

Notifications This is a complete Subscriptions/Notifications Framework aiming at extendability and scalability. It allows any number of plug-ins defining new event types or subscription types or a different user interface. Drupal 7 upgrade A quick D7 upgrade has been done for some limited funcionality. New in 6.x-4.x version Advanced queueing, fine tuning, drush processing.. Other modules using this framework Notifications Files Sends attached files in emails with posts and comments.Views Saved Searches, subscribe to saved searches.Notifications Location, subscribe to content related to your location.Notifications Add-ons, some additional modules (Custom subscriptions, FeedAPI integration, Nice subscription links...)Organic Groups is now using it for notifying users about posts. Features Immediate or digested notifications, allowing multiple digest formats for deferred notifications. Dependencies / Requirements: Looking for professional support for these modules? Sponsored by Development Seed

Fast 404 What and Why Drupal has expensive 404 errors. On an 'average' site with an 'average' module load, you can be looking at 60-100MB of memory being consumed on your server to deliver a 404. Consider a page with a bad .gif link and a missing .css file. That's where Fast 404 comes in. Drupal 7 Core Updates Drupal 7 core has updated to add a rudimentary version of what this module implements. Issue describing: Patch added: New function: Below is a matrix of the difference between this module and the new D7 functionality. Installation and Settings Fast 404 requires some configuration in the settings.php, and the readme.txt file contains a full set of options to enter in your settings.php. If you do not install the module in /sites/all/modules, then you will need to change the include line in the settings.php. White Listing Thanks!

Strongarm Strongarm gives site builders a way to override the default variable values that Drupal core and contributed modules ship with. It is not an end user tool, but a developer and site builder tool which provides an API and a limited UI. An example of such a variable is site_frontpage. Requirements CTools Light reading Strongarm leverages ctools to provide exportables of Drupal variables.

Chaos tool suite 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. Spaces Spaces 3.x Spaces is an API module intended to make configuration options generally avaliable only at the sitewide level to be configurable and overridden by individual "spaces" on a Drupal site. It has been described as: A way to make one Drupal site act like several sitesA way to provide much more configurable, full-feature Organic Groups or user homepagesA generalized API for contextual configuration Requirements & compatibility Use of spaces requires However, you will want the following modules in order to build or use reasonably cool features with Spaces and take advantage of most space types: Out of the box, Spaces provides integration modules for: User: spaces_userTaxonomy: spaces_taxonomyOG: spaces_og Basic usage Spaces is not an end-user module and realistically speaking, there is no such thing as "Basic usage" of Spaces. : ) Please read README.txt before deciding whether Spaces is right for you and your project. Removed strict PURL dependency. Documentation

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. 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. 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 To learn how to add new menu items to the menu, read further on Adding a link to a menu. Enable the menu Specify the menus to use for main and secondary links Renaming menus Removing a menu Drupal 6 and earlier

Related: