Sticky columns module allows you to add table sticky columns for Views table (by admin area) and for any table (by API).
Please report if this looks bad in your theme.
Created by ADCI solutions team
This module provides tabular display for field collections on the entity edit form. It does this by supplying a field widget that can be selected for the field collection on the field ui.
Adding a new field collection item is possible by clicking the last tab that has a '+' text by default.
Sorting of field collections is done via dragging and dropping the tabs.
The settings of the widget are (with default values):
This simple formatter module solves a typical use case in which, when clicking on a preview image (e.g. JPG or PNG file), a PDF file specified as a file field in the same node should be opened.
Provides a field type to define recurrence rules. This field type does not provide any type of recurrence on its own, instead it can be utilized by other modules to define recurrence rules using the RRULE standard.
This module requires the following libraries:
Image formatter for multi-value field for show images use jQuery Tools Scrollable plugin.
Makes themes from the {system} table fieldable via a proxy table with numeric PK.
This is super useful if you need themes to be fieldable.
An image field formatter that integrates Galleriffic plugin.
Galleriffic is a jQuery plugin that provides a rich, post-back free experience optimized to handle high volumes of photos while conserving bandwidth.
Video Embed AOL
===========
This module provides integration for AOL ON video network with "Video Embed Field" module.
USAGE
====
Use this field type as usual video field provided by "Video Embed Field".
Also, you can use video ID instead of URL.
To achieve this, in field settings set 'Use video ID instead of URL' (instance section) to "Yes".
That's it. Now field accepts the video ID instead of video URL.
Body Field Definition is a very simple utility features module. It provides a field base definition for a body field, which can then be used by one or more content types and allows the user to avoid any confusion over which content type should have the field base for the body field. This is particularly relevant for any site or group of sites being built with multiple features based content types to avoid any conflicts with each content type trying to declare it's own field base for the body field.
