
| Line: 1 to 1 | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| TinyMCEPlugin | |||||||||||
| Added: | |||||||||||
| > > |  | ||||||||||
| Integration of the TinyMCE WYSIWYG Editor | |||||||||||
| Deleted: | |||||||||||
| < < |  | ||||||||||
| Added: | |||||||||||
| > > | |||||||||||
| This is an integration of the  WYSIWYG editor. This is great little editor, fast and highly functional, and supporting a wide range of browsers, including Firefox, IE and Safari. At the time of writing it doesn't work with Opera or Konqueror.
The integration uses the TWiki:Plugins.WysiwygPlugin  to translate text to and from a format that TinyMCE can edit. | |||||||||||
| Line: 18 to 22 | |||||||||||
| The editor automatically "switches itself off" (i.e. reverts to the old text-only window) when editing topics that contain TWiki content it can't handle, such as complex TWiki variables. Editor Notes | |||||||||||
| Added: | |||||||||||
| > > | |||||||||||
| The editor uses a translator module to convert from TWiki markup language (TML) to HTML and back. The translator converts special TWiki tags - such as %VARIABLES% - to plain text, and encloses them within HTML spans using a special style called WYSIWYG_PROTECTED. In this way the editor can detect text that is not meant to be HTML formatted. This style is also used to protect special text you enter into the editor from being interpreted when the topic is translated back into TML. If you want to add any special TWiki features that are sensitive to formatting, such asSetstatements, then you have to format those regions using 'Protect on save' or 'Protect forever'.Installation InstructionsNOTES: | |||||||||||
| Changed: | |||||||||||
| < < | 
 | ||||||||||
| > > | 
 | ||||||||||
| 
 | |||||||||||
| Line: 54 to 60 | |||||||||||
| 
 Settings | |||||||||||
| Added: | |||||||||||
| > > | |||||||||||
| You can override this setting by defining TINYMCEPLUGIN_DEBUG to enable some simple debug features. 
 | |||||||||||
| Changed: | |||||||||||
| < < | This setting contains all the options passed to the TinyMCE editor on startup. 
For a full explanation of the available options, and guidance on reconfiguring TinyMCE, see the Moxicode TinyMCE Wiki  . Note the inclusion of the Pattern Skin standard CSS files in the content_csssetting. | ||||||||||
| > > | This setting contains all the options passed to the TinyMCE editor on startup. For a full explanation of the available options, and guidance on reconfiguring TinyMCE, see the Moxicode TinyMCE Wiki  . Note the inclusion of the Pattern Skin standard CSS files in the content_csssetting. | ||||||||||
| * Set INIT = mode:"textareas", editor_selector : "twikiTextarea", | |||||||||||
| Line: 107 to 114 | |||||||||||
| theme_advanced_resizing : true, 
 | |||||||||||
| Changed: | |||||||||||
| < < | content_css : "/pub/TWiki/TinyMCEPlugin/wysiwyg_src.css,/pub/TWiki/TWikiTemplates/base.css,/pub/TWiki/PatternSkin/style.css,/pub/TWiki/PatternSkin/colors.css" | ||||||||||
| > > | content_css : "/pub/TWiki/TinyMCEPlugin/wysiwyg_src.css,/pub/TWiki/TWikiTemplates/base.css,/pub/TWiki/PatternSkin/style.css,/pub/TWiki/PatternSkin/colors.css" | ||||||||||
| 
 | |||||||||||
| Line: 122 to 129 | |||||||||||
| 
 | |||||||||||
| Changed: | |||||||||||
| < < | WYSIWYG_EXCLUDE - Prevent WYSIWYG editingThe global preference settingWYSIWYG_EXCLUDEcan be set to make the plugin sensitive to what is in a topic, before allowing it to be edited. The comma separated list to fall back to text edit can include:
 WYSIWYG_EDITABLE_CALLS - Exceptions to WYSIWYG_EXCLUDEIf you excludedcallsinWYSIWYG_EXCLUDE, you can still define a subset of variables that do not block edits. this is done in the global preference settingWYSIWYG_EDITABLE_CALLS, which should be a list of variable names separated by vertical bars, with no spaces, e.g:* Set WYSIWYG_EDITABLE_CALLS = COMMENT|CALENDAR|INCLUDEYou should setWYSIWYG_EXCLUDEandWYSIWYG_EDITABLE_CALLSin TWikiPreferences, or in WebPreferences for each web.WYSIWYGPLUGIN_PROTECT_EXISTING_TAGS - Protect specific tags originally in the topic textTheWYSIWYGPLUGIN_PROTECT_EXISTING_TAGSpreference tells the translator that certain HTML tags which were originally in the topic text should remain as HTML tags; the translator will not try to convert them to TML.  This protects the tags themselves, and not the contents enclosed between the<tag>and</tag>The default setting for this preference is defined within the plugin. It corresponds todiv, span.
This feature may be disabled by setting the preference to a single comma. This does not guarantee that HTML markup will be removed; the conversion of HTML tags to TML markup remains subject to the other controls provided by the WysiwygPlugin, including theWYSIWYGPLUGIN_STICKYBITSpreference,<sticky>blocks,<literal>blocks and the rules applied to tables and lists.WYSIWYGPLUGIN_PROTECT_TAG_BLOCKS - Protect specific tag blocks originally in the topic textTheWYSIWYGPLUGIN_PROTECT_TAG_BLOCKSpreference tells the translator that certain HTML tag blocks which were originally in the topic text should remain as HTML blocks; the translator will not try to convert them to TML.
The default setting for this preference is defined within the plugin. It corresponds toscript, style.
As an example, individual html tables can be protected by surrounding them with<sticky> .. </sticky> block.  However,if you want to have all =<table> markup preserved as entered into topics by default, rather than subject to WYSIWYG editing,  add =tableto this list, and =<table> markup will become
automatically sticky.
This feature may be disabled by setting the preference to a single comma.WYSIWYGPLUGIN_STICKYBITS - Protect tags based upon their argumentsYou can define the global preferenceWYSIWYGPLUGIN_STICKYBITSto stop the plugin from ever trying to convert specific HTML tags into TML when certain specific attributes are present on the tag. This is most useful when you have styling or alignment information in tags that must be preserved.
This preference setting is used to tell the translator which attributes, when present on a tag, make it "stick" i.e. block conversion back to TML.For example, setting it toThis setting is used only after the page has been processed by the editor. If the editor does not support a particular tag or attribute and the editor corrupts the tag, this setting will not be helpful. It is only used to prevent an HTML tag from being converted back to TML. Format of the setting is tag1=attrib,attrib;tag2=attrib. Attributes delimited by comma, and tags delimited by semicolon.
 .*=id,on.*will ensure that any tag with an id oron*event handler is kept as HTML.   
The default setting for this preference are hard coded in the plugin.  If you wish to change the settings, the following list is the default setting coded in the plugin:
   * Set WYSIWYGPLUGIN_STICKYBITS = 
        (?!IMG).*=id,lang,title,dir,on.*;
        A=accesskey,coords,shape,target;
        BDO=dir;
        BR=clear;
        COL=char,charoff,span,valign,width;
        COLGROUP=align,char,charoff,span,valign,width;
        DIR=compact;
        DIV=align,style;
        DL=compact;
        FONT=size,face;
        H[0-9]=align;
        HR=align,noshade,size,width;
        LEGEND=accesskey,align;
        LI=value;
        OL=compact,start,type;
        P=align;
        PARAM=name,type,value,valuetype;
        PRE=width;
        Q=cite;
        TABLE=align,bgcolor,frame,rules,summary,width;
        TBODY=align,char,charoff,valign;
        TD=abbr,align,axis,bgcolor,char,charoff,headers,height,nowrap,rowspan,scope,valign,width;
        TFOOT=align,char,charoff,valign;
        TH=abbr,align,axis,bgcolor,char,charoff,height,nowrap,rowspan,scope,valign,width,headers;
        THEAD=align,char,charoff,valign;
        TR=bgcolor,char,charoff,valign;
        UL=compact,type
<-- %JQREQUIRE{"chili"}%
        (?!IMG).*=id,lang,title,dir,on.*;
        A=accesskey,coords,shape,target;
        BDO=dir;
        BR=clear;
        COL=char,charoff,span,valign,width;
        COLGROUP=align,char,charoff,span,valign,width;
        DIR=compact;
        DIV=align,style;
        DL=compact;
        FONT=size,face;
        H[0-9]=align;
        HR=align,noshade,size,width;
        LEGEND=accesskey,align;
        LI=value;
        OL=compact,start,type;
        P=align;
        PARAM=name,type,value,valuetype;
        PRE=width;
        Q=cite;
        TABLE=align,bgcolor,frame,rules,summary,width;
        TBODY=align,char,charoff,valign;
        TD=abbr,align,axis,bgcolor,char,charoff,headers,height,nowrap,rowspan,scope,valign,width;
        TFOOT=align,char,charoff,valign;
        TH=abbr,align,axis,bgcolor,char,charoff,height,nowrap,rowspan,scope,valign,width,headers;
        THEAD=align,char,charoff,valign;
        TR=bgcolor,char,charoff,valign;
        UL=compact,type
-->If you edit using the plain-text editor, you can use the <sticky>..</sticky> tags to delimit HTML (or TML) that you do not want to be WYSIWYG edited. | ||||||||||
| > > | WYSIWYG_EXCLUDE - Prevent WYSIWYG editingThe global preference settingWYSIWYG_EXCLUDEcan be set to make the plugin sensitive to what is in a topic, before allowing it to be edited. The comma separated list to fall back to text edit can include:
 WYSIWYG_EDITABLE_CALLS - Exceptions to WYSIWYG_EXCLUDEIf you excludedcallsinWYSIWYG_EXCLUDE, you can still define a subset of variables that do not block edits. this is done in the global preference settingWYSIWYG_EDITABLE_CALLS, which should be a list of variable names separated by vertical bars, with no spaces, e.g:* Set WYSIWYG_EDITABLE_CALLS = COMMENT|CALENDAR|INCLUDEYou should setWYSIWYG_EXCLUDEandWYSIWYG_EDITABLE_CALLSin TWikiPreferences, or in WebPreferences for each web.WYSIWYGPLUGIN_PROTECT_EXISTING_TAGS - Protect specific tags originally in the topic textTheWYSIWYGPLUGIN_PROTECT_EXISTING_TAGSpreference tells the translator that certain HTML tags which were originally in the topic text should remain as HTML tags; the translator will not try to convert them to TML.  This protects the tags themselves, and not the contents enclosed between the<tag>and</tag>The default setting for this preference is defined within the plugin. It corresponds todiv, span.
This feature may be disabled by setting the preference to a single comma. This does not guarantee that HTML markup will be removed; the conversion of HTML tags to TML markup remains subject to the other controls provided by the WysiwygPlugin, including theWYSIWYGPLUGIN_STICKYBITSpreference,<sticky>blocks,<literal>blocks and the rules applied to tables and lists.WYSIWYGPLUGIN_PROTECT_TAG_BLOCKS - Protect specific tag blocks originally in the topic textTheWYSIWYGPLUGIN_PROTECT_TAG_BLOCKSpreference tells the translator that certain HTML tag blocks which were originally in the topic text should remain as HTML blocks; the translator will not try to convert them to TML.
The default setting for this preference is defined within the plugin. It corresponds toscript, style.
As an example, individual html tables can be protected by surrounding them with<sticky> .. </sticky> block.  However,if you want to have all =<table> markup preserved as entered into topics by default, rather than subject to WYSIWYG editing,  add =tableto this list, and =<table> markup will become
automatically sticky.
This feature may be disabled by setting the preference to a single comma.WYSIWYGPLUGIN_STICKYBITS - Protect tags based upon their argumentsYou can define the global preferenceWYSIWYGPLUGIN_STICKYBITSto stop the plugin from ever trying to convert specific HTML tags into TML when certain specific attributes are present on the tag. This is most useful when you have styling or alignment information in tags that must be preserved.
This preference setting is used to tell the translator which attributes, when present on a tag, make it "stick" i.e. block conversion back to TML.For example, setting it toThis setting is used only after the page has been processed by the editor. If the editor does not support a particular tag or attribute and the editor corrupts the tag, this setting will not be helpful. It is only used to prevent an HTML tag from being converted back to TML. Format of the setting is tag1=attrib,attrib;tag2=attrib. Attributes delimited by comma, and tags delimited by semicolon.
 .*=id,on.*will ensure that any tag with an id oron*event handler is kept as HTML.   
The default setting for this preference are hard coded in the plugin.  If you wish to change the settings, the following list is the default setting coded in the plugin:
   * Set WYSIWYGPLUGIN_STICKYBITS = 
        (?!IMG).*=id,lang,title,dir,on.*;
        A=accesskey,coords,shape,target;
        BDO=dir;
        BR=clear;
        COL=char,charoff,span,valign,width;
        COLGROUP=align,char,charoff,span,valign,width;
        DIR=compact;
        DIV=align,style;
        DL=compact;
        FONT=size,face;
        H[0-9]=align;
        HR=align,noshade,size,width;
        LEGEND=accesskey,align;
        LI=value;
        OL=compact,start,type;
        P=align;
        PARAM=name,type,value,valuetype;
        PRE=width;
        Q=cite;
        TABLE=align,bgcolor,frame,rules,summary,width;
        TBODY=align,char,charoff,valign;
        TD=abbr,align,axis,bgcolor,char,charoff,headers,height,nowrap,rowspan,scope,valign,width;
        TFOOT=align,char,charoff,valign;
        TH=abbr,align,axis,bgcolor,char,charoff,height,nowrap,rowspan,scope,valign,width,headers;
        THEAD=align,char,charoff,valign;
        TR=bgcolor,char,charoff,valign;
        UL=compact,type
<-- %JQREQUIRE{"chili"}%
        (?!IMG).*=id,lang,title,dir,on.*;
        A=accesskey,coords,shape,target;
        BDO=dir;
        BR=clear;
        COL=char,charoff,span,valign,width;
        COLGROUP=align,char,charoff,span,valign,width;
        DIR=compact;
        DIV=align,style;
        DL=compact;
        FONT=size,face;
        H[0-9]=align;
        HR=align,noshade,size,width;
        LEGEND=accesskey,align;
        LI=value;
        OL=compact,start,type;
        P=align;
        PARAM=name,type,value,valuetype;
        PRE=width;
        Q=cite;
        TABLE=align,bgcolor,frame,rules,summary,width;
        TBODY=align,char,charoff,valign;
        TD=abbr,align,axis,bgcolor,char,charoff,headers,height,nowrap,rowspan,scope,valign,width;
        TFOOT=align,char,charoff,valign;
        TH=abbr,align,axis,bgcolor,char,charoff,height,nowrap,rowspan,scope,valign,width,headers;
        THEAD=align,char,charoff,valign;
        TR=bgcolor,char,charoff,valign;
        UL=compact,type
-->If you edit using the plain-text editor, you can use the <sticky>..</sticky> tags to delimit HTML (or TML) that you do not want to be WYSIWYG edited. | ||||||||||
| Configuring the buttons on TWiki < 4.2.0 | |||||||||||
| Line: 126 to 133 | |||||||||||
| Configuring the buttons on TWiki < 4.2.0 | |||||||||||
| Added: | |||||||||||
| > > | |||||||||||
| When installed on TWiki versions before 4.2.0, this plugin replaces the old textarea editor with the TinyMCE editor. The shock of this change can be too much for some older contributors, so we have written instructions for reconfiguring your templates in TWiki:Plugins.TinyMCEFrequentlyAskedQuestions  . Plugin Info | |||||||||||
| Changed: | |||||||||||
| < < | 
 | ||||||||||
| > > | Many thanks to the following sponsors for supporting this work: 
 | ||||||||||
| 
 | |||||||||||
| Added: | |||||||||||
| > > | 
 | ||||||||||
| 
 | |||||||||||
| Changed: | |||||||||||
| < < | 
 | ||||||||||
| > > | 
 | ||||||||||
| 
 | |||||||||||
| Line: 150 to 161 | |||||||||||
| 
 | |||||||||||
| Changed: | |||||||||||
| < < | 
 | ||||||||||
| > > | 
 | ||||||||||
| 
 | |||||||||||
| Line: 165 to 176 | |||||||||||
| 
 | |||||||||||
| Changed: | |||||||||||
| < < | Many thanks to the following sponsors for supporting this work: <-- Do not attempt to edit this topic; it is auto-generated. Please add comments/questions/remarks to the Dev topic instead. --> 
 | ||||||||||
| > > | 
 | ||||||||||
| 
 | |||||||||||
 
  Copyright © 1999-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Copyright © 1999-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.