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!
Superfish integrates jQuery Superfish plugin with your Drupal menus.
- Touch-screen compatible. (Equipped with window width and HTTP UA string settings.)
- Small-screen compatible. (drop-down turns into a
<select>list. Equipped with window width and HTTP UA string settings.)
- Keyboard-accessible, screen reader friendly.
- Multi-column sub-menus. (Megamenus)
- Easing effects, automatic sub-menu width calculation (Supersubs plugin), automatic sub-menu placement (Supposition plugin; prevents sub-menus from appearing off-screen.)
- RTL (Right-to-left) language support.
- Plenty of built-in options for designers.
- And a whole lot more...
The modules list page can become quite big when dealing with a fairly large site or even just a dev site meant for testing new and various modules being considered. What this module aims to accomplish is the ability to quickly find the module you are looking for without having to rely on the browsers search feature which more times than not shows you the module name in the 'Required by' or 'Depends on' sections of the various modules or even some other location on the page like a menu item.
When tabs is enabled via the Module Filter's settings page, a new module layout theme is implemented. This tab layout provides a tab for each package as well as a tab that will show every module alphabetically. The filter textfield is available on each tab but currently doesn't support autocomplete.
Skinr's main purpose is to allow the theme to define a set of reusable and modular CSS styles, and to make those styles available in Drupal's UI. Skinr was developed for themers to allow them to tap into the power of Drupal's modularity and apply those same principals to theme development. It does not provide any styles of its own. These styles are defined in the .info file of the theme (or subtheme), by the themer and end up in various places in Drupal's UI, such as:
It also provides a CSS class field, where you can manually add custom classes.
DISCLAIMER: Do not use Omega Tools with the 4.x version of Omega. While it might work it is not tested and possibly incompatible. Please create your 4.x subthemes using Drush! The Drush integration for Omega 4.x comes as part of the theme itself and does NOT require Omega Tools. Please uninstall Omega Tools if you are building a site with Omega 4.x
The Omega Tools module is a set of helper functions and custom functionality intended for use with the Omega Theme. However, the functions this module provides could be used with any theme.
This module is currently only being updated for the Drupal 7 branch, and for integrations with Drupal 7 Omega theme. Just sayin'.
The following features are provided by the Omega Tools module. Some features are Drupal 7 only, some are for Drupal 6 and 7 versions.
#D7CX This module got into core and will only be available as a back-port version for Drupal 6.
Provides vertical tabs like http://drupal.geek.nz/static/node-form/default/summaries2.html on the node add form.
This module provides the following features:
- Vertical tabifying all node forms.
- Vertical tabifying the content type forms.
- Vertical tabifying the block forms.
- Specialized CSS for Garland, as well as generic CSS for other themes
- Color module support when both Garland and color.module are used
- Vertical tabbed forms and fieldsets are over-ridable by using your site's settings.php and $conf. For more information see #644790-7: Simplify the module and integrate with form_controller to allow customizations.
- When used in combination with Form module allows you to configure vertical tabs on all possible forms.
Gallery formatter provides a CCK formatter for image fields, which will turn any image field into a jQuery Gallery.
- Two imagecache presets which will work out of the box beautifully.
- The thumbnails run under an infinite carousel.
- Degrades gracefully without JS enabled, the gallery still works.
- Integrated out of the box with thickbox, colorbox (recommended as the thickbox upgrade path), shadowbox and lightbox2 for the view full links.
- Works with the swfupload, image_fupload, and imagefield_crop widgets.
- A hook for modules to provide styles for the galleries.
- Two options for styles, no style and a green arrows style. No style should be used for developing your own styles.
Ordinarily in Drupal, in order to see the sub-items in a menu, you need to click the link of this item and wait for a full page load. After enabling DHTML Menu, clicking a menu link once will expand it to reveal its sub-items without reloading the page. A double-click on the item will load the page normally. Additionally, a cookie stores which menus are open and which are closed, so that the state of the menus remain consistent as you navigate around the site.
Note: In 6.x-3.0 and all later versions, DHTML Menu starts working as soon as the module is enabled. There are no blocks to replace and no block options to enable.
#D7CX: DHTML Menu has a D7 test version and will have a stable release for Drupal 7 the day Drupal 7 is released.
Provides a quick and easy way to replace any text on the site.
- Easily replace anything that's passed through t()
- Locale support, allowing you to override strings in any language
- Ability to import/export *.po files, for easy migration from the Locale module
- Note that this is not a replacement to Locale as having thousands of overrides can cause more pain then benefit. Use this only if you need a few easy text changes.
What is Delta?
Delta allows you, via the Context module to make duplicates of your theme settings for any context on your site. This gives you the ability for alternative layouts as a reaction in Context... </awesomesauce>
Delta by definition: (Greek letters in mathmatics)
- a finite difference
- a difference operator
- a symmetric difference
- the difference or change in a given variable
Currently no status messages of great importance other than the fact that there IS finally a release of Delta... ;)
For Drupal 7 the module integrates the jQuery UI Accordion plugin as a views style plugin. You can configure the options provided by the jQuery UI plugin. For Drupal 6 the module used it's own jQuery code, so a different set of features is available for D6.
- Works with field grouping and relationships.
- Option to use the field grouping headers as the headers for the accordion items. (yay!)
- Configure settings for jQuery UI Accordion through the views interface.
Features only for Drupal 6 only:
- Option to Auto cycle items (which pauses on mouse over)
- Option to add Open All - Close All links.
- Configure whether or not you'd like to keep one item opened. (Ej. the user clicks on an opened item, whether you want it to close or not)
- Option to allow more than one row to be open
Image Assist allows users to upload and insert images inline into content. It automatically generates an "Add image" link under fields of your choice. Clicking the link opens an image browser, displaying all images that have been uploaded via the Image module.
Images can be filtered by ownership or taxonomy terms (categories). New images can be uploaded through Image Assist's dialog. Clicking on an image displays a properties page where attributes such as caption, size, and alignment can be set before the image is inserted into the post.
Image Assist is especially useful when using a client-side editor/WYSIWYG editor. Currently, it can be used with TinyMCE via Wysiwyg API - support for other editors is right on the way.
Allows administrators to inject CSS into the page output based on configurable rules. It's useful for adding simple CSS tweaks without modifying a site's official theme -- for example, a 'nighttime' color scheme could be added during certain hours. The CSS is added using Drupal's standard drupal_add_css() function and respects page caching, etc.
Internet Explorer implements a proprietary technology called Conditional Comments. While web developers frown upon technologies that aren't cross-browser supported, many CSS developers have found Conditional Comments very useful. They can have cleaner CSS in their normal stylesheets and can fix the broken rendering in IE by placing IE-only CSS inside conditional comments; this technique is even recommended by Microsoft.
Without this module, the only way to have IE conditional stylesheets was to add 37 lines of code (more if you want to add more than one stylesheet) in four horribly-difficult-to-remember function calls to your theme's template.php. Blech. Who wants that?
This module allows Drupal 7 themes to easily add conditional stylesheets to the theme's .info file.
; Set the conditional stylesheets that are processed by IE.
stylesheets-conditional[lt IE 7][all] = ie6-and-below.css
stylesheets-conditional[IE 9][all] = ie9.css
stylesheets-conditional[IE][print] = ie-print.css
This module adds some common-sense usability to Drupal's menu system
- Menu Trails implements primary/secondary links which keep the current menu trail "active" or highlighted. A handy snippet ready to go into your template.php is included.
- The module provides a means of broadly categorizing nodes (by type or taxonomy) as falling "under" a known menu item. These nodes are not added to the menu tree (keeping the menu admin system sane) but they will trigger the functionality above -- preserving navigation state for the user -- when viewed.
- New for 6.0: Menu Trails can also set breadcrumbs for nodes, keeping them in sync with the trail.
- New for 6.0: Menu Trails is now Organic Groups aware, so nodes can be designated to fall "under" the first group node they belong to.
- New for 6.0: A token is exposed to pathauto (and other token-aware modules) allowing for the menu trail to be used in automatic path alias creation.
ThemeKey allows you to define simple or sophisticated theme-switching rules which allow automatic selection of a theme depending on current path, taxonomy terms, language, node-type, and many, many other properties. It can also be easily extended to support additional properties exposed by other modules. In combination with Drupal's theme inheritance and ThemeKey Properties you can easily achieve features like:
- individually-styled channels
- a front-page / "splash" screen
- a date/time-selected Christmas theme
- mobile themes for different auto-detected mobile devices
- special themes for "limited" or "old" browsers
- content, user, or role -specific themes
- indicating your environment (production, staging, testing, sandbox, … )
- testing your redesign safely on a live server
And unlike other theme switching modules, ThemeKey should play well with internal and external page caches, like Boost or Varnish, even for anonymous users.
Feedback is welcome!
Damn, ThemeKey ... ROCKS! Really appreciate the kick ass work you did on this :) mortendk
Drupal allows you to define a different theme for administration pages (Administer -> Site configuration -> Administration theme). By default this only applies to pages with a path starting with 'admin' and content editing pages.
The Administration theme module allows you to use this theme on more pages like :
- batch processing pages
- devel node load and render pages
- coder code review pages
- pages you define yourself in the provided textarea
The Drupal 5 version adds the option "Use administration theme for content editing" available in Drupal 6 core.
Some of these options will only be available to you if they apply to your installation, i.e. you have the module installed which generates these pages.
Use default theme (not administration theme) for anonymous users on admin/*
This is possible using this module. See issue http://drupal.org/node/372156 for more details.
You can add extra pages by implementing
hook_admin_theme_options in a module.
For Drupal 7 the hooks are
How can you get involved?
- Help write or improve the documentation.
Separates the node forms into two columns and a footer.
This module alleviates some of the problems with the mile-long node forms in Drupal. Other than that it gives you the possibility to use different weights and collapsed states for your forms than for your presentation.
To get started, go to "admin/content/node-type/page" (or whatever content type you want to configure) and you should see the "Manage form" option that points to "admin/content/node-type/page/form". If not, clear your cache.
Take a look at the GitHub page for more information: http://hugowetterberg.github.com/nodeformcols/
Development sponsored by Good Old.
On 404 Not Found error pages, Drupal will skip rendering of several pieces of your website for performance reasons. Some of these include:
- The "Left" and "Right" regions of your theme.
- The "Primary links" block and any other menu links block.*
- The Primary links and Secondary links of your theme.*
* Unless you have configured a "Default 404 (not found) page" on admin/settings/error-reporting.
But many websites find those items invaluable. Especially on 404 pages, when they want to show lost users how to get to real pages.
So this module simply revives those features on 404 pages. Simply install and enable the module. No configuration needed.
This module allows you to move the "Read more" link from the node's links area to the end of the teaser text.
Often times site builders want certain types of content to appear in a specific position in the navigational menu. The simplest solution, adding all of that content individually to the menu system, has performance and usability issues. (Imagine hundreds of menu items added to one spot in the menu.)
This module allows for the creation of rules that will dynamically add the current page into the menu system at the requested spots.
This includes affecting:
- The main links of the theme
- The secondary links of the theme
- The breadcrumb trail
- Menu blocks provided by core's Menu module
- Menu blocks provided by the Menu Block module
#D7CX: I pledge that BlockTheme will have a full Drupal 7 release on the day that Drupal 7 is released.
BlockTheme allows an admin to define tpl files for standard block templates and provides a select box on the block configure form so the user can select a tpl file to use as opposed to having to override the templates by block ID.
Widgets enables you to centrally manage and configure code snippets on your site such as share and follow buttons or Twitter updates and Facebook like boxes. It implements a user interface that allows you to easily organize and configure various widget elements. Using a UI similar to core’s image styles, elements can be assembled into widget sets which can be reused throughout the site via blocks and other render displays.
The Widgets module is primarily a user interface API and as such includes only generic markup widgets. You can add new custom widgets using the widget definition admin or enable modules that provide widgets. There are several dozen widgets available through the Social media and Service links modules.
- Installation. Use standard methods to install the Widgets archive files into your Drupal site. Then go to admin > modules and enable the Widgets module. You will want to install the Social media and/or Service links modules also to provide widget sources.
- To display widget sets on your site use the blocks admin at admin > structure > blocks or other method for managing blocks such as Context or Panels. Look for blocks that start with the label "Widgets:" Several pre-built widget sets are provided by the Social media module.
The Mobile Tools module provides Drupal developers with some tools to assist in making adjustments to your site based on the visitor's device.
- Contextual switching of content and layout
- Exportable configurations using Spaces and Features
- Define your sites via domain, sub domain, path, path pairs and query string
- Server side feature detection using Browscap
- Automatic redirection to a site based on device group
- Mobile bookmark popup/Add to home screen notification
- Media Query builder
- anything else we can think of!
Mobile Tools integrates with the following modules to enable the described functionality
- Context HTTP Headers
Mobile Tools 3.x