more[?] powerful input format concept

First, as there is no Input Format project, I slipped this into User Maintenance.

Currently, input formats are determined by user roles and it is not possible to force or bind a specific input format to a particular content type. That's unfortunate for me, because that is exactly what I need to do. IN fact, it may be a more useful scheme for Drupal overall.

Let's say that I need "stories" to be created using the filtered html input format, and that I need "pages" to be Full HTML.

Under the current scheme it can not be forced.

Once a user role is allowed Full HTML, that user can run with that input format site wide - regardless of content type. In other words, I don't want Full HTML in stories, but by allowing a user role to have that input format they can break my site scheme by entering Full HTML into the stories where i do not want it.

Or, if I have a content type called "group captain pages", where group captains would be allowed PHP input for setting up a few simple, group specific features, I can not bind the input format to the content type - so anyone with the "group captain" role could run with the PHP input format site wide.

Giving these group captains Sole access to the new content type (group_captain_pages) doesn't solve the problem of users with that role potentially using the PHP input in places where it should not be allowed - maybe even my "stories" contnet type where I want nothing but filtered html.

I'm thinking that if this were possible, the overall usefullness of Drupal might be enhanced in certain situations. But, as it is now, I simply can NOT control the input format by content type.

I'm not savvy enough to hack this myself, so I'll have to wait to see what you guys think about this. There is one thread from ancient days where this was almost discussed. It started out as a discussion of managing input format by content type and then quickly lost its focus. There are notes there, however, showing how various people tried to get around this issue. Inevitably, however, the problem I mentioned holds sway: You simply can NOT allow any user role to make use of an input format that you DO NOT want used in some content types, because there is now way to stop them from using that format site wide. [See link bottom]

To me, it seems that one possible extension of Drupal as a CMS framework application interface (fancy way of saying a self-describing CMS) and one great advantage to be had using Drupal, would be allowing input format by content types. There are probably many reasons. I'll give only the 2 that relate to my project:

If input formats were bound to content types rather than user roles:

1. Different content types could actually and in fact be "customized", with some content types running absolutely nothing more than visible text, others including links, images, php snippets or whatever else the site developers deemed necessary for that content type.

2. It is likely in my specific project that the PHP input format would be assigned to at least one content type, whereby the project client could make use of a set of pre-written scripts to help him create reports - generate statistics - whatever.

Only those with the user role "client" would be given access permission to "adminster", "create" "edit" and so on this content type.

Give that some thought. Does that not create an extension of the usefullness of Drupal?

I've already considered the argument that the argument that giving the "client" user role use of the PHP input format and access permissions to "administer", "create" and etc of this new content type does the same thing. It doesn't. Only by binding the input format to the content type can you completely control where and how "special" input formats might be applied. Without that binding by content type can you be certain that PHP isn't run site wide by those with roles given permission to use that format.

That's the key to it for me: The ability to create "special" input formats and assign them to content types. Give that some thought. With custom content types, used with "custom" or "special" input formats (defined by the site administrator and then controlled by user access) isn't Drupal's usefullness as a Self Describing CMS extended greatly?

I mentioned I am not savvy enought to pull this off. Sure would be nice if you guys thought it was worth the doing.

Very interested in the nuts and bolts here.

See http://drupal.org/node/35245