Maintenance fixes only

Allows you to set different field labels for singular and plural, depending on the number of values.

For each step you can define which fields should be included in this step. "Fields" includes core-fields like "Title", "Body" or "Authoring information" as well as fields defined by other modules (e.g. Date).

Dependencies

Drupal 7

• ctools: http://drupal.org/project/ctools
• "Field UI" (core module): optional / should be enabled to configure steps manually

Drupal 6

None (though CCK is highly recommended).

Known problems

Drupal 7

Hierarchical select

Hierarchical select is not working at the moment if you get back to a step with a hierarchical select element (the element is not restored properly). This can be solved by applying the patch attached to #1585824-3: when editing node HS forgets taxonomy term path.

Pathauto

Pathauto currently exposes a field named "URL path settings" on the "Manage fields" tab. Unfortunately this field does nothing (the field itself remains within the vertical tabs) and should not be attached to a step.
See #1244470: "Path module form elements" as an "extra field" on "Manage fields" page makes no sense for the issue in the pathauto issue queue or #1894468-6: Step label appearing at bottom of each form step for an in-depth description of the problem in Multistep Nodeform.

Provides a field type that can reference arbitrary entities:

• A generic entity reference field
• Four widgets:
  • Two implemented on top of the Options module (Select and Radios/Checkboxes),
  • Two autocomplete widgets (one with one text field per entry, one tag-style with comma-separated entries in the same text field)
• Two formatters:
  • A "Label" formatter, with optional link that displays the label of the referenced entity (the node title, the user name, etc.)
  • A "Rendered entity" formatter, that renders the references entity using a configurable view mode
• Integration with Views (for both forward and backward references)
• Integration with Entity Metadata (and as a consequence with Search API and the like)
• Integration with Devel generate
• Integration with Feeds and Migrate (>= 2.3) for painless data import

This modules depends on Entity API and CTools.

Modules extending Entity reference functionality:

• Entityreference view widget
• Entityreference prepopulate

This module allows users with the appropriate permissions to edit the allowed values of a CCK field from the node create/edit form itself. This is much more convenient for the site developers, and as it has its own permissions you can also open it up to the client^*. There are two permissions: users with Edit CCK allowed values will be able to edit the allowed values of fields which have been explicitly configured to allow it; users with Edit any CCK allowed values can edit the allowed values of any appropriate field.

Instructions

1. Download and enable the module as usual.
2. Set up permissions as you'd like.
3. If you're using the Edit CCK allowed values permission then you need to explicitly configure the fields you'd like to be edited by users in that role. If you go to the field edit screen you should see a new checkbox titled Edit allowed values. Check that and save, and the link should appear on the node form for users with the right permission. This setting is configured per content type and not per field.

Warning if opening up to clients

Allows block visibility conditions to use 'OR' conditions rather than 'AND' which is the default for core.

This module adds a filter for hyphenating input using phpHyphenator.