Actively maintained

This module does what I thought the Placeholder module (http://drupal.org/project/placeholder) did.

This is a relatively simple help popup module that provides either:

Allows file tokens to be used as attributes in theme_image_formatter()

A simple module that allows you to disable Javascript and CSS aggregation on specific modules, themes, /misc and libraries.

BUEditor Plus provides you with better control over BUEditor and where it appears. By default BUEditor displays on most textareas. You can control which editor appears via roles, paths and element IDs. BUEditor Plus overrides that default behavior and gives you better control over which textareas the editor appears on. Now you create profiles and assign those profiles to text fields in Drupal's field system. Not only that, but BUEditor Plus allows you to assign different editors based upon text format. You can create a "Full HTML" editor and a "Filtered HTML" editor in BUEditor. Then in your profile assign those editors to their associated input format. Now when you change input formats for a textarea the editor will automatically change to the proper one for that format. You can even set a format to "none" to not have an editor appear with that input format.

Description

This module lets you hide fieldsets that you don't want to be available on the node create/edit form, configurable by content type. For example you could use it to hide the URL path settings fieldset for content type Story.

Versions

It's for Drupal 6 only.

Installation & Use

• Install as normal.
• Go to Content management -> Content types -> Edit [content type]
• Under Fieldset settings there are checkboxes for the different fieldsets available on the nodeform for that content type. By default they're all active. Deselect those you don't want to be shown.
• Click Save content type.
• If you want any roles to be able to see hidden fieldsets, then give them the see hidden fieldsets permission.

Notes

The module doesn't alter permissions, only which fieldsets are usable from the node create/edit form. It's possible that users will still be able to accomplish some of the actions via other admin screens. (For example, if you hide the Menu settings fieldset, a user with administer menu would still be able to change the weight of a node's menu item from the menu admin screens.)

Exportability