Actively maintained

Latest: I've come back to using Drupal after a long break and am now maintaining this module again.

Ever felt existing roles/permissions weren't right for controlling access to your new view? Given the choice of compromising or defining a new permission in code, you may well have compromised. I generally did.

Using this module you can quickly define new permissions through the UI. Great for controlling access to views. If you decide to refactor your roles, you won't have to edit a bunch of views whose access is controlled by role. Just add and remove the user defined permission from the relevant roles in a single step.

This module would be even more useful if Rules were to get a "User has permission" condition. I think this condition is just in the bonus pack at the moment #1338768: Condition: "User has permission" but I could be wrong.

Help: What about permission renaming? Should this be allowed? The initial ID of the permission is just its title converted to all lower case. If we allow the title to change then the ID (which might be used by a custom module) will "drift" from the the title. Changing the ID of a permission that has already been assigned to a role would be all kinds of badness.

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')

For now it uses exiftool to fetch exif data from images. But I want to build a plugin structure with providers so multiple sources can be used to fetch exif data.

Webform component clone (WFCC) is a webform module widget, it provides a clone across the different webforms component

This module provides a simple redirect to the newest instance of a particular entity type. Optionally you can also specify a bundle type as well.

Provides a very basic search function for your site.