Minimally maintained

Typical Entity Examples

This module provides a pack of typical example entities.

First entity created in this module is the smallest possible entity. Every next entity is gradually improved version of the previous one. The last entity from this module is the rather complex entity with the user interface for creating entity bundles.

This module can be useful for people who want to learn how to develop entities step-by-step.

Development of this module was sponsored by the OITS Co. Ltd.

How to use

Sub-modules typical_entity_example_1, typical_entity_example_2 and typical_entity_example_3 don't have user interface, but they can be tested with "Testing" module.

Sub-modules typical_entity_example_4 and typical_entity_example_5 available at the following pathes:

  • /typical_entity_4
  • /typical_entity_5

Sub-module typical_entity_example_6 provides the following URIs:

  • Manage typical_entity_6 bundles:/admin/structure/typical_entity_6
  • Manage typical_entity_6 entities: /typical_entity_6

Field Collection Workbench Moderation


This module provides better support for Workbench Moderation on nodes containing Field Collections:

Correctly sets the default revision status for Field Collection items to match the moderation status (published or otherwise) of the host node. This ensures that any Views using relationships to access Field Collection item fields will display fields from the published node, instead of using fields from the latest revision. See Most recent Field Collection revision always appears in View when using Workbench Moderation for more detail.

A patch to Field Collection has been provided in the issue linked above which. If that and the required patch below are both committed, this module will no longer be needed.

Requirements

Workbench Moderation
Field Collection

If you are using multi-value Field Collection fields, you will also need to apply the patch at Field collection doesn't play nice with workbench moderation (patch).

EXIF Scrub

Removes EXIF metadata from uploaded images. In future versions I hope to have options to allow either the system or an individual user (with proper permissions) to re-add geotags to the image.

Ideally, the module could have configurable which metadata values to strip and which to keep.

How it works:
On file upload, it checks to see if the file has a mimetype of "image/jpeg". If it does, it uses ImageMagick to strip the metadata and resave.

Requires: ImageMagick

Hours of Operation

CCK field for storing and displaying hours of operation for businesses, etc. Allows division of days into segments (for example morning hours, evening hours). Requires Date and CCK modules.

Google App Email

This module can display gmail unread count and email title.
This module use the Google Token Management module.

Flattr block

provides a simple flattr block

Subscribe with RSS Syndicate content