Releases for Node and Comments Form Settings

Release notes

This is the same version of 6.x-2.0-beta2 but since no one has reported bugs, I consider it stable enough.

The main change is that the 6.x-2.x will make a less intense use of the variable table by storing all settings in just one variable per content type.

UPGRADING FROM 6.x-1.x

If you're upgrading, chances are you have all your content types configured. I added a new module to handle the migration, you should install it after you update your files.

The main reason for the migration module is because NFS and CFS have been separated into 2 different modules and now instead of creating several variables they use one per content type (nodeformsettings_content_type and commentformsettings_content_type) so your old variables won't work.

You can see a list of some of the changes made visiting http://drupal.org/node/1077760

The migration module will recreate the variables for you, but I must warn you that you should review this since your configuration could be lost. Please make a backup of your database before you do anything. To use the new Features bundled with 6.x-2.x you'll still have to edit your content type.

Release notes

THE FOLLOWING IS A LIST OF CHANGES FROM THE PREVIOUS VERSION 6.x-1.x

I. The most important change is that now this module instead of creating a thousand variables, now uses an array keyed variable to save all the settings, this will reduce the intense use of the {variables} table.

II. All alters are made in a separated include file, the module will auto detect the file and the function. Follow this three steps to create a new alter functionality.

1. Define the key and a default value in nodeformsettings_elements_default() or commentformsettings_elements_default(). Starting with nfs_ (for nodeformsettings) or cfs_ (for commentformsettings). Example:

In this case we define the key 'cfs_title' with a default value of 0 (Enabled).

This step is mandatory since it will be used by the hook_form_alter() implementation. If you don't define a key in the form of 'cfs_something' or 'nfs_something' the module will not recognize the alter.

2. Create a file in the includes directory in the form of _option_cfs_something.inc
Again, the _option_cfs_ or _option_nfs_ are mandatory. Take a look at the include directory in each module to see some examples.

Release notes

added german translation #695318: German translation. Thanks to @dddave
added new feature #630452: Disable Name, Email & Homepage for Anonymous Users
fixed #590566: Comments form settings doesn't work when using Content Profile and Advanced Profile Kit. Thanks to @mattiasj
fixed half of #709262: Validate to ensure buttons are not removed altogether

Release notes

Added feature to remove revision log field. Thanks to @jjeff #646282: Option to remove revision log field

Release notes

Stable enough. Released with the following functionality:

* Hide the "Split summary at cursor" button
* Hide the Input Format fieldset
* Change the default value of the Submit button
* Hide the preview button
* Hide the node title, useful when you're showing the node title on the breadcrumb or if you want to hide it for any other reason. The title needs to be set, if you want to auto generate it, use Automatic Nodetitles since this will not hide the title on the form, just when viewing the node.
* Hide the author of the comment on the comment form
* Hide the preview button
* Hide the word 'Comment' or title
* Hide the Input Format fieldset
* Change the default value of the Submit button to whatever you like
* Change the size of the comment text area