Actively maintained

Configurable and simple welcome message. Message will be displayed when a user logs in.

The Entity Fields Builder module enhances Drupal's standard "manage fields" interface, making it possible to quickly add multiple fields to a content type or other fieldable entity, using field templates based on properties of standard content schemas such as the ones available at Schema.org. The advantages of standardized, schema-based field definitions include:

• Better searchability. Using the Schema.org module, you can automatically and easily add markup to web pages that enables search engines to better recognize the semantic meaning of the content on those pages. This provides search engine optimization. Major search engines including Bing, Google and Yahoo! have agreed to recognized Schema.org-based markup in order to improve the display of search results.
• Better interoperability. The Schema.org module provides RDFa markup, which means that the content on web pages can be extracted automatically using the SPARQL query language or as Google Rich Snippets. In effect, other websites and applications can use your Drupal site not just as a source of web pages, but as a sort of database from which information can be queried and programmatically retrieved.

This module is designed to test the development of hook_toolbar() and hook_toolbar_alter() in

Provides feeds integration for entityreference for mapping directly to properties of referenced entities.

• Utilizes Entity API to provide mapping targets for entity properties.
• Will automatically create new referenced entities and update existing ones using a GUID mapping to separate between the two.
• Set default values for required entity properties and avoid being forced to map them in Feeds

Use case

How this module works is perhaps more easily conveyed through a simple example:

Lets say we are importing products, together with product-reviews as XML from a third pary API. This happens to be an ill-designed API, and the reviews are nested in the XML as children of the products they belong to, and cannot be fetched separately.

There are multiple solutions to this problem. One could for example create an API wrapper, preprocessing the file and separate products and reviews in two xml-feeds. This is a bit of work though, comes with additional issues like making sure reviews are imported before products etc.

Local Foodhub defines the commerce functionality to support a foodhub in a community, where producers and consumers attend a regular collection day where ordered products can be collected.