Site structure

Display suite add on to output taxonomy terms with all parents, for each taxonomy field you'll find a new field called "Term with parents: vocabulary".

Supported options:

This module allows content creators/maintainers to add maps to content via the addition of a "Google Map Field" field type that can be added to content types.

Drupal 7 version for imagemenu module drupal 6

This module defines a new field type Spotify Play Button, allowing you to embed spotify tracks.

Overview

This module allows you to bypass the default data storage location for fields and entities and instead load the data from a web service.

This is useful when your primary data source is in another system but you want to display/use this data in your Drupal site without the hassle of syncing or importing data.

Web Service Configuration (wsconfig)

Stores information about your web services. This information is used to allow Drupal to make the appropriate CRUD operations on requested data.

Web Service Fields Storage (wsfields_storage)

Defines a field storage controller allowing you to read, write and query fields from a web service. Support for EntityFieldQuery (coming soon) will allow developers to make entity field queries with web service data.

Web Service Fields (wsfields)

Parses data from a web service to be compatible with fields defined by core and some contrib modules. Allows you to use web service data as field data. Thus allowing you to use the same field formatters and standard options defined for the given field.

Web Service Entities (wsentities)

(Coming soon) Define a means to allow Drupal entities to be loaded from a web service instead of the database.

Dependencies

• Entity API

Events as fieldable entities, or eventities as I like to call them. The module's name is actually Event, and I plan on eventually submitting this as a patch for a Drupal 7.x version of Event, but since it's fundamentally different, and the issue queue for Event is the scariest thing I have ever seen, it lives here for now, until it can be feature-matched/completed to the old event.

For when you need an event that's an entity. If you need this, you are probably looking for it. If you want an entity for events, here you go. This is a ready to go out of the box event entity waiting for content. It supports multiple event types (entity bundle), configurable under structure, and adds an 'Events' tab to content administration for adding/removing/lookup of events.

Also works with views, at least for my use cases. Additional features and development to come as needed/requested. I suggest using the Date field module for event time, as it's compatible with pretty much everything else also. If you have a compelling reason to include a date as a property, please feel free to submit a feature request. Plays nicely so far with Registration module if that's your thing.

This whole module is pretty simple but just sort of does what I need it to (meaning I haven't looked over Event in quite some time and it may not meet feature for feature). Enjoy!