Fields

Allows any entities that are referenced on a deleted entity's fields to also be deleted. This is the converse of Field reference delete whose purpose is to remove any references to a deleted entity from all your other entities (if I delete a taxonomy term, remove all the references to that term from my other content's fields).

The module also takes into account checking if a referenced entity is a default value for any field, and will not delete it in that case.

Dependencies

• Entity API

Supported field types

• Entity reference
• Commerce product reference and line item reference
• Core taxonomy term, file, and image
• Any field module which references an entity table and ID column in it's hook_field_schema() 'foreign keys' array.

Examples

An Entity reference field that is using the Inline entity form widget so that users can only create new referenced entities. If you delete an entity that has this field, then this can leave 'abandoned' entities that can no longer be referenced.

A taxonomy term field called 'Tags' which is free-form and allows users to add whatever tags they want. If you get a bunch of spam entries, you want to ensure that the tags the spammer used are also removed if no other content is tagged with those terms.

Similar modules

• Entity Reference Cascade Delete: pretty much a duplicate of this but only works for entity reference fields.
• Inline entity form contains this functionality but it is set to be removed. #1969122: Remove auto-deleting of child entities
• Delete orphaned terms. Our module does not bulk process existing entities to see if they are orphaned or not, which this module does do.

See Node display fields module

See Node display fields module

Module provides Node Display Field field type, that displays various information about the node depending on type of widget that has been selected.

Allowed widgets:

• Text slider
• Сomments count
• Author
• Created date
• Changed date
• Submitted by (to do)
• Links (to do)
• Read more (to do)
• User picture (to do)
• Title (to do)

Each widget has Format settings popup on Manage Display page, where you can change in what format the data will be dispayed.

You can use these fields in Panels and transfer through Features.

Module is very similar with the Display suite but Node Display Fields uses the Core fields, much more lighter and easier to use out-of-box.

This modules introduces fields containing many boxes, each box representing a column of the field in database.

On settings.php you define what kind of fields you require, eg: Text field with 4 boxes, Text field with 30 boxes, int field with 8 boxes
Then in hook_schema does field were going to be defined, In hook_field_info made available to Drupal.

All of them shared the same widget, widget has this settings:
Caption of every box (If they had any), Validations such as number range, text length,

It's also a nice future to make some of those boxes auto complete, or a select list.

Right now there is only a very limited widget that accepts some captions. There is no display formatter! Nothing will be displayed.
Inspired by "address field" I wanted to make it plugable using ctools, integrated with views, (rules if needed), And feeds.
The bigger problem is need of settings.php
The biggest problem is that Indexes (on database tables) are not customization through module, or maybe not, It would be better done by hand in database.

A simple module that handles allowing any file type to be uploaded but still showing images in a reasonable manner.