Different default input formats for different content-types

Since the filters are only role based, and not content based, you'll need to make two roles, each having the the right to make one of the two content types, and configure the content types for those roles accordingly. I don't see any other way.

- Robert Douglass

-----
My sites: HornRoller.com, RobsHouse.net

I have this same issue, but the code has changed since the hack was posted.

Basically, the problem that I am having is caused by my use of two TinyMCE profiles (though this issue applies to many situations where a contributed module doesn't even come into play). I am using TinyMCE's more advanced HTML features for users of a certain role, while anonymous and authenticated users get a stripped down version of TinyMCE that adheres to "Filtered HTML". Obviously, I have to make the lower one the default because I don't want anonymous and authenticated users to have the ability to use "Full HTML".

This becomes a workflow issue because if the user with the higher role forgets to change from filtered to full HTML, he's going to lose formatting detail and worst of all may not even notice it initially. Added to that is the fact that the option is now collapsed on the cluttered node submission page and the reason this is an annoyance becomes apparent.

I'll give a full rundown of how I think this problem can be addressed in a way that makes Drupal more flexible, but to be honest I'll take any hack that'll let me specify an input format for a special role case directly in code.

Addressing the Problem (without a hack)

The reason a system "default" filter must be selected is obvious, Drupal's filtering should work out of the box and it's easy to overlook ticking a box when you're initially creating your site and setting up roles - the "default" feature is definitely an important one. However, I think with a few changes to how it behaves, it can be much more flexible for situations like the one I outlined above. The problem boils down to automatically selecting a default input format (IF) for a role when a role is assigned to multiple IFs. We could take the approach of removing the checkbox disable code for the default IF so we could deselect roles, then force the first IF with that roll checked to act as the default. However, that's undesirable because you may not want the IF it selects to be the default and there may be security implications as well.

To solve this problem, I propose the introduction of a second "default" setting. To the left of each role in each IF would exist a second checkbox, "role default", that would allow the admin to set the current IF to being that role's default. This second checkbox would show up next to all roles in all IFs except those in the system default IF and the "anonymous user" role in all IFs. There's no need to have the second checkbox next to roles in the system default IF because if they are checked then the system default IF is implicitly the role's default IF. The "anonymous user" role should lack this checkbox in all IFs to ensure that the admin realizes he is setting the IF that will always be applied to a visitor that is not authenticated. Since "anonymous user" is the lowest role an admin will configure - as it applies to every visitor to the site - all other roles should default back to the IF you would allow anyone to use; being unable to change the "anonymous user" default IF from the system default IF helps to illustrate this.

The roles in the system default IF should remain disabled at all times, as they currently do. If an admin changes a role's default to another IF, the checkbox for that role should be unchecked but still disabled in the system default IF. Next to the unchecked role, a link labeled "revert" would allow the admin to set the role's default back to the system default IF. The revert link only appears in the system default IF and only when a role's default has been switched to some other IF. It may be nice to have a Javascript popup explain the revert action and confirm that the admin wants to do it, but this is not necessary. If the revert confirmation functionality is to be added, it should have an option to disable the check on the main Input Format settings page.

When in an IF that is not the selected system default, the "role default" box will appear next to every role except "anonymous user" (for reasons explained above). When the admin checks off a box and saves changes, the module should check to see if any other IF that is not the system default IF is already serving as the role's default IF. If it is found that the role already has a default IF (that is not the system default IF), the admin would be informed what the IF was and asked to confirm that they wanted to change it. If the admin confirms or if no other IF is acting as the role's default, the module sets the selection to be the role's default. The check and subsequent prompt should have a setting on the main Input Format settings page to disable it if the admin wishes; by default this option should not be selected so the checks automatically occur.

If a "role default" box is unchecked and the page is submitted (indicating the admin no longer wants that IF to be the role's default), the system default IF should automatically switch back to being the role's default IF and the checkbox should show up as checked the next time the admin views the system default IF configuration page. On the main Input Format settings page, all IFs that are not the system default IF should list "(role default)" next to each role that it is the default for. For example, instead of the "Roles" listing for "Full HTML" showing up as "anonymous user, authenticated user, custom role", it would read "anonymous user, authenticated user (role default), custom role (role default)" if both "authenticated user" and "custom role" had set it as their role default IF.

The last case that requires special handling, that I can think of at this time, is changing system default IF. When changing from an old system default IF to a new one, it should not take over and become the default IF for all roles; instead it should transfer over what roles currently use the system default IF as the role default IF and leave the rest be. It's less likely that somebody will want to reconfigure all the formats than it is that they will want to reconfigure one or two. For the cases where they do want to reset them all, the system default IF configuration page should have a "revert all" option that will make all roles default to the system default IF; for this action, confirmation is required and cannot be disabled via a setting.

I've tried to cover all possible situations, but I may have miss one or two; if so I'd be happy to brainstorm solutions to any issues you may find with the above proposal. I think the UI setup I've laid out is sufficient and pretty easy; though the UI could be made simpler, it would require more recoding of the module than the benefit would be worth. I don't know how hard these changes would be to make, but for whomever may do them, I think it would be a great fix for the filter module and make Drupal just that much more flexible.

Please let me know what you think of the above proposition.

Nick

I am using cck and tinymce in my drupal site. I want to have different default input formats for different content types. Or, also possible, the possibility to define a default input format for the user defined fields in cck.

Here is a way to change the default input format per role:

in filter.module replace this line in function filter_form() (around line 800):

<?php
 $value = filter_resolve_format($value);
?>

with this:

<?php
global $user;
	if (is_array($user->roles) && in_array ('Admin', $user->roles)) {
		$value = 5;
	}else {
  		$value = filter_resolve_format($value);
	}
?>

In the above example I have a role called 'Admin'. Any user who has role 'Admin' will have input formt number 5 selected as the input format. Hover your mouse over 'configure' on this page to see what the number is for your filter: ?q=admin/filters

www.johnstonwebsolutions.com/we_install_modify_and_maintain_drupal_web_s...

filtered HTMl input format and a Liquid Wiki input format. On pages that are using the category container of "Wiki" or have the input format set to Liquid Wiki, I would like to disable TinyMCE.

I've using the "Show if the following PHP code returns TRUE (PHP-mode, experts only)." option to display TinyMCE. What would I use to determine if a node's input format?

I also would like to see a solution on this matter

Watch the Filter default module http://drupal.org/project/filter_default

look at the support requests - http://drupal.org/node/109019 looks like something similar

I poked around in my Drupal admin menus for quite a while, then decided to come look for some help. I'm disappointed this is not possible. I'm concerned mostly because I seem to have gathered from the posts that full HTML is a security risk, but getting my trusted authors to click "full HTML" is just one more thing they forget to do. They can't even remember to choose a menu, so I had to take that out and use the Views module. It needs to be just "title" and "body", and submit.

So, is it true there's no way in 5.1 to restrict anonymous users to filtered HTML (or just basic text), without making the trusted roles have to click Full HTML (which they can't remember to do)? (The module mentioned is only 4.7.)

How much of a security risk is Anonymous Full HTML? Or do I have that wrong, and it's not a risk? Can a nasty anonymous user enter PHP in as full HTML? I can think of irritating things they can do, and nothing really dangerous, but I certainly don't know all the tricks.

Quint

take a look to http://drupal.org/project/filterbynodetype

Sounds like what everybody is looking for here

subscribing.

Subscribing. Setting default input type per role is important for me. Full HTML is needed for editors, Filtered HTML for anonymous and regular users

Subscribing. This would be a valuable addition.

It seems to me like it should be really strait forward.

Full HTML for Authenticated & no HTML for Anonymous

Recently came across the same issue, has anyone figured out a good solution to this?

With a CMS that thrives on different content types as part of its flexibility and power, default input format per content type seems like a no-brainer. Someone please add, module or hack this.

Any solution for Drupal6?

Apparently this will be part of core in D7, but until then there's a very useful D6 module called Better Formats (http://drupal.org/project/better_formats). Completely solved the problem for me.

Note that it didn't work right until I followed the instructions at http://drupal.org/node/360451 about changing the role weights at /admin/settings/filters/defaults.