Actively maintained

This module extends the entity API of Drupal core in order to provide a unified way to deal with entities and their properties. Additionally, it provides an entity CRUD controller, which helps simplifying the creation of new entity types.

Requirements

• Drupal 7.2 or later; suggested Drupal >= 7.15

Documentation

You can find documentation in the handbooks. Also check the README and the provided API docs in entity.api.php.

Overview

For site-builders

This is an API module, so it doesn't provide any end-user features. However, it provides some entity generic functionality to other modules that site-builders may leverage:

• A Views display plugin and field to render or link to any entity (by view-mode)
• A CTools content plugin to render any entity (by view-mode)

This module aims to utilize Google Closure Compiler API/application to optimize your cached JavaScript files.

More info about the application/service:
http://code.google.com/closure/compiler/

Closure Compiler module looks at the cached JavaScript folder (sites/default/files/js) and processes files on cron run. It basically supports 3 different modes:

1) Compile locally via Java based compiler
2) Send JavaScript file contents to the API
3) Send JavaScript file paths to the API (Requires your site to be publicly accessible by Google)

Iframe Filter allows to embed content into an iframe. Normally externally loaded content like website widgets can slow down the loading of your website or making it crash if the page from where the content is loaded fails.

Iframe Filter provides a simply solution for fixing this, you just need to add this filter to an input format and the content you create using that format will be displayed inside an iframe created dynamically.

Designed to be the successor of the core profile module, which is deprecated for Drupal 7. In contrast to the deprecated module this module provides a new, fieldable 'profile' entity - leverage the power of fields!

Requirements

• Entity API - Version 1.0 beta 9 or later!

Comparison to user account fields

As described in the documentation Drupal 7 allows adding fields to user account pages - what serves as simple way for building user profiles. The main differences between that and profile2 are:

• With profile2 user account settings and user profiles are conceptually different things, e.g. with the "Profile pages" module enabled users get two separate menu links "My account" and "My profile".
• Profile2 allows for creating multiple profile types, which may be assigned to roles via permissions (e.g. a general profile + a customer profile)
• Profile2 supports private profile fields, which are only shown to the user owning the profile and to administrators.

Relationship to content profile

Multi-path autocomplete (formely known as Menu path autocomplete) changes some input field for entering paths to an autocomplete text field so users do not need to know the internal system path but simply can enter the title of the page to link to.

Taxonomy Single Tag improves core's taxonomy autocomplete by allowing commas to be used as part of the taxonomy term. To do this, TST limits autocomplete taxonomy fields to a single term.