Closed (duplicate)
Project:
TinyMCE
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Reporter:
Created:
20 Jul 2006 at 15:20 UTC
Updated:
1 Apr 2007 at 22:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
tones commentedA simple patch, working on my sandbox and so probably ready to be commited.
I used '#notinymce' instead of 'DisableTinyMCE'.
Comment #2
harry slaughterI haven't tested this patch, but wanted to add a ++ for the idea.
We need more ways to turn TinyMCE off :)
It's wonderful for a lot of users, but it gets in the way for the rest of us.
Comment #3
Tobias Maier commentedI think it is better to introduce a "wysiwyg" variable
which is an boolean (TRUE or FALSE default is FALSE) or an array which offers more functionality
we should replace the current behaviour which shows the editor by path with a version which only looks for this variable.
tinymce forms alter adds this to the specific textareas
Benifit:
* other modules (FCKeditor etc.) could use it too
--> we could put the function of adding this variable to a textarea in a seperate module (maybe called "WYSIWYG Helper Module")
so that no module has to code it twice
Comment #4
kreynen commentedComment #5
kreynen commentedhttp://drupal.org/node/130309
Comment #6
nathanraft commented#1 seems like a good short term solution. Can someone send on instructions for using the hook_form_alter for a standard page or cck input form?
Comment #7
nathanraft commentedUsing #1 above I did the following for a module that creates its own node type. Not sure how to do this for CCK nodes. While this is not the best approach for long term it works for now.
Has anyone started working on a content type settings approach, a minimum textarea size, or any thing else?