Frequently Asked Questions of the TinyMCEPlugin integration.
A: There are several ways to disable the WYSIWYG editor; the first option is preferred:
EDITMETHOD
preferences setting: wysiwyg
to use the WYSIWYG editor (default), or raw
to use the raw text editor.
TINYMCEPLUGIN_DISABLE
preferences setting: NOWYSIWYG
preferences setting: WYSIWYG_EXCLUDE
setting as described in WysiwygPlugin to disable the editor subject to certain content in the page, such as TWikiVariables or pure HTML. This can also be set on a web, topic, or personal basis.
;nowysiwyg=1
to the end of the edit URL to disable it for a single edit.
Regardless of the setting, you can invoke either editor:
A:
Protect on save
format.
A:
A: Just type it in. When the topic is saved, what you type will be saved just as you wrote it. If any part of your variable parameters is sensitive to spacing, then select the entire TWiki variable and assign the Protect on save
style to it.
A: It does, but you have probably got your security settings in IE set up to disable it. In IE got to Tools->Security->Internet->Custom Level->Allow paste operations via script. If this is set to 'Disable', then all internet applications are blocked from pasting using Javascript. Either enable this option, or add your TWiki site to the list of Tools->Security->Trusted Sites.
A: You probably have your file extensions set up in Apache so that .htm
files are treated as plain text. Look through your Apache config (including .htaccess
for the pub
directory) for a line that says something like: AddType text/plain .htm
(probably with a bunch of other extensions). You can either remove .htm
from that list, or you can add a .htaccess for the pub/TWiki/TinyMCEPlugin directory that contains the line AddType text/html .htm
A: It's impossible to be 100% certain that the use of a WYSIWYG editor will not change existing content such that TWiki Applications no longer work. The WysiwygPlugin is set up by default to make it as easy as possible to create new content and import content from other applications. However some TWiki applications are written such a way that they "just work" - they take silent advantage of the sloppy parser used in TML rendering. Sloppy syntax can break the rules that WYSWYG relies on to be able to interpret TML and present it for editing.
Unfortunately there is no simple way to describe what will, and what won't, work with WYSIWYG. The best tactic is to use the <sticky> tag to protect such content (this tag is automatically applied by the "Protect forever" format).
Related Topics: TinyMCEPlugin, TinyMCEQuickHelp, WysiwygPlugin