multistep 6.x-1.4

• #656588: content type with underscore in name by drenton: Fix the code for content types with underscores in name.
• #622844: After a few steps, previous save and next buttons go to top of page: Increased the weight of the submit buttons.
• #530848: Revisions and Published state: Verify whether the Published checkbox is checked.
• #579126: Multistep module breaks multi-valued fields by garrizaldy: Verify whether there is a step for multigroups.
• #542498: Not working with Content Profile module by drupalprojects: Multistep integration for Content Profile.
• Use $form_state for functions that are called at validation/submission.
• #585610: Make fields (instead of groups) available on different steps by mesh: Make fieldgroup-less fields available on different steps.
• Added a hook to allow third-party modules to override the status of a step.
• #579126: Multistep module breaks multi-valued fields: Added support for multi-value fields and multigroups.
• #555822: split taxanomy into different steps: Allows splitting of taxonomy vocabularies into different steps.
• #530848: Revisions and Published state: Add settings for node revisioning and publishing.
• #560748: Separate 'Hide standard buttons' settings: Removed unsetting the Delete button. Use node permissions instead.
• Fixed misnamed variable and added more information to multistep_help().
• #548114: Support _all_ extra fields (not just Taxonomy) by BWPanda: Support multistep for all extra fields.
• #550982: Enable removal of Ubercart's 'Save and continue' button by BWPanda: Enable removal of Ubercart's "Save and continue" button.
• #551944: Differentiate between normal groups and multistep groups: Allow users to select which groups appear in the menu block.
• #554304: Rename multistep blocks by BWPanda: Rename multistep blocks to make them easier to find.
• #555814: warning: Missing argument 3 for multistep_field_access() in ...modules/multistep/multistep.: Removed unneeded $account argument in multistep_field_access().

This release contains new changes to the database. Don't forget to run update.php after upgrading.

Note: Due to a change in how access is set for each fieldgroup, if you are upgrading from version 6.x-1.3 to 6.x-1.4, you have to go to each fieldgroup settings form and re-submit it. There will also be a new option to decide whether you want that particular fieldgroup to show on the menu block or not.