Site structure

Swipht technologies developed a set of security modules with sponsorship from Portland State University. The modules provide roles and user specific security permissions for menus, menu items, nodes, and security integration into the administration and help systems. We would like to provide this suite of modules back to the community to share the usefulness of the suite and involve the community to provide additional support, testing, and moderation. Special care was taken to ensure the usability of permission management was consistent across all sections of the system (nodes, menus, menu items). Also each security module uses a cascading security scheme to allow global security and the option to override or define exceptions to the security model for individual items.

For example, defining global node access rights by role will dynamically apply the security scheme to all content types and nodes created. However the user can override the global security scheme for an individual content type, and override the permissions for a given content type by setting permissions on an individual node.

Please Note!!

By default, Drupal displays free tags in alphabetical order. Sometimes, however, the order that tags have been entered per node is important. Perhaps more relevant tags are entered first.

The ImageField Tokens module extends the default functionality of Image fields adding the ability to specify default values and use entity tokens in the Alt and Title text.

This module provides a new Views argument plugin for date fields that allows for arbitrary date ranges in summary views. If you need to generate a listing of nodes by quarter, academic term, or some other site-specific date range then this is the module for you.

Note: This module has only been tested on MySQL 5.x and I'm fairly sure it will not work on PostgreSQL. Unfortunately it requires doing seriously bizarre things in SQL that are not at all portable.

Once this module is enabled, you will find a new Views Argument handler under the "Date" group called "Date: Date range". It works in the same way as the normal "Date: Date" argument, except that instead of setting a granularity for the summary view you may configure your own arbitrary set of date ranges at the bottom of the configuration form.

These date ranges should be in the order you wish them displayed, and together should cover the entire year. They may be given any label you wish.

When the view is displayed, if no date is given then a summary view will be generated that uses the specified date ranges rather than more common ranges like a summary by month or by year. Each date range will be within a given calendar year, so will be along the lines of "Quarter 3 2008", "Quarter 1 2009", etc.

Description

Provides an alternative, user friendly interface to multiple select input box for selected taxonomies on node creation.

Designed specifically for 2-tier hierarchical classification systems, the module creates tabs for the root elements. Each tab contains the corresponding children, which are click to select and click to remove. It also add an area to display the selected terms and ability to remove them without searching through the tabs for the undesired terms. The module will also allow you to target specific taxonomies to act on, while leaving other taxonomy interfaces unaltered.

Allows you to add nodes to the menu (under some parent item) without making it appear in the menu.

Adds an option "Node Trail parent" in the node edit form. There is no settings page.

Some examples

- To some nodes you get through a View or Search, or from an external link or external search engine.
- If this node is not a child in a hierarchic menu structure, nothing in the menu would show as active.
- If the user wants to continue navigating on your site, it would help if the current node shows up associated to somewhere in the menu, or some other navigation indication.

(Thx porg for these examples)

How can you get involved?

• Help write or improve the documentation.
• Write a review for this module on drupalmodules.com.
• Help translate this module at http://localize.drupal.org/translate/projects/admin_theme.
• Report any bugs, feature requests, etc. in the issue tracker.

How can you be kept up to date?

• Enable the updates module.
• Read my Drupal blog.