Site structure

EPSA Crop is a module that allows a user to choose coordinates for different presets on an image.

A catalogue shows items in a category, along with subcategories. With this module, this is a view of nodes that embeds a view of terms, with a taxonomy term argument which affects both: the main view shows nodes for the given term, and the embedded view shows the child terms of the given term.

Examples

This module is a generalization of the code from the image gallery system in Image module. In that module, the gallery view shows the nodes for the current term, and the child terms; or in other words, the nodes in the current gallery and the subgalleries.

For a shop site, suppose vocabulary is product type. For a particular term, say 'bicycles', path at 'catalogue/bicycles' takes this term as its argument, and for that term the output is:

1. the embedded term view showing child terms of 'bicycle', such as:
   • children's bicycles
   • mountain bikes
2. the main node view showing bikes which belong to the term 'bicycle'. These are general bicycle nodes that have not been further categorized.

Further examples and setup instructions are in the README file.

Features

• Embeds the view of child terms above the view of nodes

This is a modification of the taxonomy_menu module which creates the menu from any number of single level vocabularies, which is useful in situations where each category shares the same subcategori

Module info

This is a very simple module that takes the link text of each drupal menu item and adds it as a css class name to the menu's <li> element. Using these class names, each menu item can be styled separately with css. This is also very useful for css sprite techniques.

This module integrates Ubercart with Location. When a user places an order, their addresses go into their user locations.

This module provides an auto-increment (serial) field.

Unlike Drupal's built-in auto-increment node ID, which is global and shared by nodes belonging to all content types, serial fields are managed per content type (D6) / entity (D7). For example, the serial field of an Invoice instance will generate a unique sequential number (starting at 1, then 2, etc.) exclusively for Invoice instances.

The allocation of serial numbers by this module is atomic. In other words, the serial values are unique even when multiple instances of the same content type / entity are created simultaneously.