FCKeditor is a very nice module, but it did't completely fit my needs. Therefore, I added some extra settings. These are:
- a checkbox to disable fckeditor for user 1
(only user for which fck couldn't be disabled using permissions, and I really don't want fck to load all the time when I'm logged in as admin - I never use it personally)
- Two radio buttons:
- Always use fckeditor (for all textareas)
- Use fckeditor only for the textareas of specified node types
(in this case you can navigate to administer->content->configure->content types, and in the workflow form for each node type, you'll find radio buttons to enable/disable fck for that type
The module is attached completely, I failed to make a patch because of line break problems (Mac line breaks in cvs files?).
fckeditor_textarea() is changed.
2 settings are added to fckeditor_settings()
fckeditor_nodeapi() is added
I hope you find it usefull...
edit: wrong file upload - should be the correct one now
Comments
Comment #1
slower commentedYes, this is very useful! Thank you Dries.
Perhaps it would also be possible to implement the same mechanism that is used for displaying blocks so there could be even finer control over where FCKeditor is used.
Comment #2
kjshaw commentedYes, a text area selector would be a blessing. HTMLArea.module provided an admin>>settings>>HTMLArea page that generated a new line everytime a novel textarea was generated on a page. If you didn't like having HTMLArea show up in that spot, it was simple enough to navigate to the settings page and turn it off. This was especially useful when writing blocks with mixed HTML/PHP. As it is, oftentimes, the entire textarea is taken up with the tinyMCE toolbar and when you click "disable editor" it throws java errors and hangs.
Selecting by node type is OK, but on the admin pages, rsvp config, etc., sometimes you would prefer a WYSIWYG editor on some fields but not others.
I'm liking FCKEditor much better than tinyMCE, which has no colorpicker and nearly invisible and inscrutable icons, but the "infinite" selectivity of HTMLArea is sorely missed.
Thanks for all everyone does to make drupal a fantastic tool!
Kevin
http://www.pafordemocracy.com
Comment #3
mousse-man commentedThere seems to be some problem with the patched version.
The same phenomenon (broken RSS feed for drupal site in question by inserting one spurious LF into the XML file) has been observed, amongst other bug reports, here.
Is there anything one can do against it?
Comment #4
behindthepage commentedSorry I have posted this as a new issue then noticed this thread. So I shall post again.
This patch adds a textarea to the settings page where you can specify which paths not to use fckeditor on. Similar to block visibility settings.
This is my first patch and I am using Winmerge. I don't know whether it conforms to "patch standards" - all feedback welcomed.
Comment #5
behindthepage commentedI have diff working now with cygwin so patch should be acceptable. (please let me know if not)
This patch adds the ability to exclude fckeditor from certain pages that are set on the settings page. Similar to "don't show the block on the following pages" textarea.
Comment #6
behindthepage commentedSorry my patch still has bugs in it. I thought I had it working but not quite. Will do more work on it and get back to you
gpdinoz
Comment #7
ontwerpwerk commented4.7 version has functionality for role based toolsets and exclusion
(user->uid == 1 unfortunately is ignored)
Comment #8
(not verified) commented