Site structure

In contrast to the other breadcrumb modules this module provides a new, fieldable 'breadcrumb' entity - leverage the power of fields! Some of the code was copied from Profile2 module. Thanks to fago.The module is aimed to provide a simple, but extensible solution providing breadcrumbs.

Idea

1, Breadcrumb is an entity, include:
(1),path, a property, which store the unique internal path, only support specific path such as node/1
(2),link, it is a multi values link field, store trail links.

2,Using rules to generate breadcrumbs for node/taxonomy term etc.

Requirements

• Views 3.7
• Link 1.1
• Entity API 1.1
• Rules 2.3
• Ctools1.2

Installation

1,Install Link module at first.
2,Then install this module.
Otherwise, maybe you will get an error message "FieldException: Attempt to create a field of unknown type link_field"

Document :

Provides a field formatter for image fields that allows configuration of specific image styles (or none) to apply to images at specific breakpoints, and renders field in such a way that only the ap

This module adds a formatter for image fields, that make possible to select a hover image style.

This module is an extension of Drupal Commerce that provides a display formatter for the Commerce Price field in which you can specify the decimal places are displayed.

The sales pitch

Do you use a node for your 404 page?

Do you hate how translating the node behind the 404 page (or 403 page, or front page) doesn't actually work the way you'd think it would? By default, everyone will see the 404 page you configured under Site Information by default. To show translated versions for other languages, you have to turn on the Internationalization Variable submodule from the Internationalization module. You then have to tell it which node to use for each language where it isn't the default-language node.

UNTIL NOW!

Internationalization 404 leaps into action just before your 404 (403, front) page is served and changes it to the translated version instead.

But wait, there's more! It actually checks to see if you have configured a different node with the help of the Internationalization Variable module, and respects that setting.

This module was developed because featurizing variables containing node paths didn't seem like the way to go. If we already have translated content, why should we also have to translate the variables? We only need to know the source node, and there is less chance for human error in configuring that.

Installation

Provide audiojs display formatter, download link and link to audio entity.