Menu field
Component type
Categories
Maintenance status
Development status
Component created
Component changed
...
...
This module integrates Drupal Commerce with Secure Hosting's payment services. The module's functional, but needs testing: test thoroughly before using on a live server! It currently only supports off site payments.
For detailed instructions please consult README.txt.
Commerce Contributions provides a way where users can contribute/invest/support a specific Project/Organization/Cause, It works by adding a Commerce Contributions Field that can be added to any content type, and when users view the content page they can see the Contributions Meter and Contribute.
The Commerce Contributions Field can be customized to include a custom button text like "Contribute Now", "Invest Now", "Donate" ...etc
Provides the "glue" for the field created by the Video Embed Field module to be map-able with Feeds module.
Drupal 6
Provides a CCK field to facilitate streaming media. Field can be attached to any content type to store pertinent information about a media stream: stream name, stream location, live or on-demand.
Drupal 7
Provides a new field as part of the Drupal 7 Field API.
This module doesn't provide any display by itself, but is quite useful in conjunction with other modules. Requires custom code to implement the display.
test
This is a contribution from existing usability improvements that I've used for fields. The key concept is to cater for fields with long lists of options such as:
The solution is purely a JS/jQuery solution for hiding and showing relevant information from a filter input.
The user enters a few letters and the options the user is seeking become easier to see from the potential thousands.
Yahoo Weather Forecast module ported to Drupal 7.
Drupal modules to load content asynchronously based on dimensions, context or capabilities. For more information about the project see: http://www.slideshare.net/woeldiche/going-mobile-first-with-drupal
The project is not ready for usage yet.
This module works out of the box for all kind of content entities - no configuration is needed.
Conflicts which will be auto merged:
-changes in translatable fields in non-edited content entity translations
-changes in fields to which the user does not have access
--fields with no edit access
--fields not part of the entity form display
-changes in entity metadata
--revision ID
--changed timestamp