Actively maintained

In some situations you want to mark an entity field to indicate it should be completed but not enforce its completion at that time. This module extends the choice between Required and Not required to "desirable" completion.

This module overcomes the problems with the (otherwise excellent) Content Complete module which cannot cope with field collections or fields that link to other entities.

When you might want it

The module has two use cases:

Where you might (say) have a score of completeness on a user profile. You don't want to enforce filling in fields with a "required" but just encourage it by having a %age completion. (There's a nifty block that shows the level of completion and what could be filled in next.)

The other use case - and the reason I needed it - was having an absolutely huge application form that could not be filled in in one sitting and which also had all sorts of field collections and links to other content which also had to be filled in correctly.

Everything has to be filled in, but it might take weeks (in this case). So the user needs to be able to save it between times - but the ability to submit the final version does not appear until everything is filled in. (There's a Rules rule - which is in the documentation - to allow actions to take place when the form is finally completed.)

Features

• Works with
  

The Plugin module complements Drupal core's plugin system in several ways.

The fieldset_completion module uses jQuery/javascript to show a completion rate while a user is editing the fields in a fieldset (Drupal 7).

fieldset_completion
===================

The fieldset_completion module (Drupal 7) is an example of how to show a completion rate for all the input fields in a fieldset. It grabs the fieldset span.summary tag (inside the span.fieldset-legend) to display the completion rate.

This is a very small module that adds Delete link as a tab in the node pages.

Provide an alternative Profile2 OG Access to be determined by if the user is a member of a group instead of the profile2 entities being a group post.