Developer tools

Fieldable Fields

As of Drupal 7, the Field API and the Entity concepts open up a world of possibilities for detailed, bespoke cms design.

Almost all the "atomic" components are now implemented as Fieldable EntityTypes:

• Node
• Comment
• Taxonomy Vocabulary
• Taxonomy Term
• User
• OpenGroups Group
• DeveloperDefined EntityTypes
• more...

Each Field itself may have a variety of settings associated with it. These settings are specified using the FAPI and the resulting dict automatically serialised and stored. There are two types of settings: Field Settings, which are settings that apply globally to that Field; Field Instance Settings, which are specific to each FieldInstance (A FieldInstance is created when a Field is added to a Bundle)

It can become a little knotty understanding the terms involved in the Drupal EntityType/Bundle/Field/FieldInstance/Entity ecology. [IS THERE A LINK TO A GOOD PAGE TO PUT HERE?]

Allow administrator to assign different server names to same drupal instance based on server location.

First idea. Allow google plus like access control via Active Tag like audience fields

This module allowes system admins to perform text replacement operation on nodes text fields using regular expressions.

This module is the early stage of development.

This module provides a no-hassle means to remove the most visible instances of the Druplicon from a site, replacing them with a less intrusive alternative. The goal is to reduce the amount of boilerplate configuration (or theming) sitebuilders must do at the beginning of a project to make it presentable to clients.

Warning : This module abuses EntityFieldQuery to return data from your database. It does not work with entities or any modules that build on them.

It allows you to use addField within an EntityFieldQueryExtraFields object (extends EntityFieldQuery objects). Initially EntityFieldQuery only gives you back the entity id, bundle and entity type. This module adds an extra layer on top of that without doing some extra entity_loads! Important if you want to work with massive amounts of data and you want to reduce the sql queries. Since EFQ already queries the database for this information, why not alter that query to also give you some additional fields. This means that not a single extra query will be performed to get that data.

A word of caution, if you rely on some post-formatting/post-loading that happens in entity_load or similar functions, this module won't take care of that. You have to ensure the validity of the retrieved data yourselves.

Example

Fetching the node title


$query = new EntityFieldQueryExtraFields();
$result = $query->entityCondition('entity_type', 'node')
->propertyCondition('type', 'my_bundle_type')
->propertyCondition('status', 1)
->addExtraField('field_myfield', value', value')
->addExtraField('field_mynodereffield', nid', nid')
->addExtraField('', 'title', 'title', 'node')