| Project: | Drupal core |
| Version: | 6.x-dev |
| Component: | documentation |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Relevant portion of O Govinda's commentary from http://drupal.org/node/101090:
-----------------------------------------------------------------------------
Home » Administer » Help » Filter
The filter module allows you to configure formats for text input for your site. For example, you may want a filter to strip out malicious HTML from users' comments.
Despite the name "filter," the module not only lets you keep out text you don't want but also lets you enhance the text you let in. So, for example, you can use the filter module to make URLs linkable even if users enter them in an unlinked format.
When users create or edit content, they can choose between the available input formats. You can configure which formats are available to which user roles, as well as choose a default input format. You can also create new input formats. And you can configure each input format with use your choice of filters.
For more information please read the configuration and customization handbook Filter page.
Filter administration pages
Configure permissions
Input formats
Comments
#1
I did this very hurriedly, and had some problems with it. But, it is about the last one on my stack of todos!
#2
Also, there were some strings underneath this section that included p tags in their text, so I broke those out into smaller units and did a few small tweaks there.
#3
yeah, that's no good.
#4
And, another version, which contains a few tweaks to the help text and a couple of things Gabor noticed and reported on #drupal.
#5
Did some IRC review:
goba: keithsmith: "converted in a clickable link" looks wrong
goba: also a sentence ends in "filters get executed" the next starts with "Filters are executed"
goba: "adds elements to text before it is displayed" => "adds elements to *the* text before it is displayed"?
goba: keithsmith: I don't find other problems
#6
And another one, cleaning up some "execute" over use in legacy text (which is more pronounced now).
#7
Thanks, this looks great now, committed.
#8
Automatically closed -- issue fixed for two weeks with no activity.