input formats

Hey everyone,

This is my first contribution to the list; i have a
porpostion i want to 
make, it would be nice to have it included..

I think an important feature that should be available, is to
be able to 
assign input formats by node types. Let me give you an
example,

let's say we have a site with a forum section and a stories
section.. 
all members can submit stories and post in the forum.
I want the posts in the forum to have bbcode and other
filters.. let's 
say an input format called "Forum posts"
On the other hands i want the stories to be submitted with
the "Filtered 
HTML" filter..

There currently is no way of assigning input formats to node
types..

It shouldn't be too difficult to implement. Each content
type 
configuration page can have a section with a filter
selection and 
weighting..

and there would be a overall site default that could be
overridden by 
the content type specific filters...

I hope i made my self clear.. waiting for your feedback.

zis

On 10/26/06, zis <zisbeiruter.com> wrote:
> There currently is no way of assigning input formats to
node types..
>
> It shouldn't be too difficult to implement. Each
content type
> configuration page can have a section with a filter
selection and
> weighting..
>
> and there would be a overall site default that could be
overridden by
> the content type specific filters...

I like the idea in principle. However, we'd have to be
careful when
implementing this, for a number of reasons:

1. The filter system is currently independent of the node
system -
filters can be applied to any text (e.g. comment text, block
text,
static text), not just to node text. We want to keep it this
way. So a
'tie input formats to node types' feature would have to be
developed
with this in mind - it should apply only to the use of the
filter
system by the node system, and it should not break the use
of the
filter system by other systems.

2. The filter administration screens are already a
well-known
usability bottleneck in Drupal. Users are already confused
as to the
difference between an input format and a filter, the way in
which
filters can be tied to multiple input formats, and the way
in which
filters can be configured differently per input format. We
don't want
to make this usability bottleneck even worse, by adding yet
another
layer of association and configuration.

If possible, this should be developed as a contrib module
first, and
then considered for addition into core at a later stage. Not
sure how
easy it would be to implement this without hacking core at
all,
though.

Have you written any code or produced any design mockups
yet, and if
so, can you post a link to them?

Cheers,
Jaza.

zis wrote:
> There currently is no way of assigning input formats to
node types..

I coded one of these awhile ago

http://cvs.drupal.org/viewc
vs/drupal/contributions/modules/input_format_restrictions/

Let me know if it is still working.

-- 
Neil Drumm
http://delocalizedham.com/

On Thursday 26 October 2006 00:51, Neil Drumm wrote:
> zis wrote:
> > There currently is no way of assigning input
formats to node types..
>
> I coded one of these awhile ago
>
> http://cvs.drupal.org/viewcvs/drupal/
contributions/modules/input_format_res
>trictions/
>
> Let me know if it is still working.

No wonder I never saw that module.  It doesn't actually show
up on the site, 
even in the CVS version, as far as I can see.

I always wonder how many cool modules that do just what I
need already exist 
that I don't know about because they're not tagged or are
tucked away in 
someone's sandbox.  

I've not tested the module yet, but UI-wise, I'd think the
"obvious" UI would 
be to simply add a node type checkbox list below the role
checkbox list in 
the existing UI, then throw in a "non-node input
fields" checkbox at the 
bottom for good measure.  It would be no worse than the rest
of the filter 
UI, and fits with common convention.  

This is a feature I keep meaning to work on for a project I
am building slowly 
on the side, since I know I'll need it as well.  If it's
already done via 
contrib, that's fine too if it's a stable contrib.  I'll try
and take a look 
at the module soon.

-- 
Larry Garfield			AIM: LOLG42
larrygarfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than
all others of 
exclusive property, it is the action of the thinking power
called an idea, 
which an individual may exclusively possess as long as he
keeps it to 
himself; but the moment it is divulged, it forces itself
into the possession 
of every one, and the receiver cannot dispossess himself of
it."  -- Thomas 
Jefferson

Larry Garfield wrote:
> On Thursday 26 October 2006 00:51, Neil Drumm wrote:
>> zis wrote:
>>> There currently is no way of assigning input
formats to node types..
>> I coded one of these awhile ago
>>
>> http://cvs.drupal.org/viewcvs/drupal/
contributions/modules/input_format_res
>> trictions/
>>
>> Let me know if it is still working.
> 
> No wonder I never saw that module.  It doesn't actually
show up on the site, 
> even in the CVS version, as far as I can see.
> 
> I always wonder how many cool modules that do just what
I need already exist 
> that I don't know about because they're not tagged or
are tucked away in 
> someone's sandbox.  

The plan was to get it into HEAD, but that didn't happen
since I decided
some other things in the content type administration UI
needed
organization and thought. I got some decent ideas on paper,
but never
managed to get those online or anywhere near code.

-- 
Neil Drumm
http://delocalizedham.com/

Op woensdag 25 oktober 2006 22:41, schreef zis:
> let's say we have a site with a forum section and a
stories section..
> all members can submit stories and post in the forum.

There are many more cases and valuable additions, so I
suggest you build this 
as a separate module, If we were to include all
"valuable additions" in core 
the filter system would grow huuuge 

 * certain role getc a certain input format.
 * certain user gets a certain input format (settable in
your profile 
settings)
 * certain node-type gets a certain input, no other choice
possible,
 * certain node-type gets a certain input set to default,
other available 
formats can be chosen instead.

etc.
 

Bčr
-- 
| Bčr Kessels | webschuur.com | Drupal, Joomla and Ruby on
Rails web 
development |
| Jabber & Google Talk: berjabber.webschuur.com |
| http://bler.webschuur.com | http://www.webschuur.com
|

Commentaren en feedback op inhoud:
 http://help.sympal.nl/commentaren_en_feedback_op_inhoud