Tiny MCEPlugin integration.
On this page:
- Q: The editor takes over the standard edit screen. That's OK, but how do I get access to the old (textarea) editor?
- Q: How do I set a Foswiki macro inside TinyMCE?
- Q: How can I protect content from TinyMCE?
- Q: How do I use a Foswiki macro inside TinyMCE?
- Q: Why doesn't copy-paste work on Internet Explorer?
- Q: Why do all my popups contain raw HTML?
- Q: I write Foswiki applications. What is safe to edit?
Q: The editor takes over the standard edit screen. That's OK, but how do I get access to the old (textarea) editor?A: Foswiki has a 'Edit Wiki Text' link on most screens that gives you access to the plain text editor, so this question is moot. In addition to this there are three ways to temporarily disable TinyMCE:
- Add=;nowysiwyg=1= to the end of the edit URL to disable it for a single edit,
Set NOWYSIWYG = 1in a web, topic, or personal preferences page to disable the editor for a web, topic or user,
Set WYSIWYG_EXCLUDEas described in Wysiwyg Plugin to disable the editor subject to certain content (e.g. Foswiki macros, pure Code.HTML etc) being in the page. This can also be set on a web, topic, or personal basis.
- Create a list item using the toolbar button
- In the list item, type Set NAME = value
- (Optional) Select the value, and format it using
Protect on saveformat.
- Select the content and select the "Protect forever" format. This will add <sticky>..</sticky> tags around the content, which don't interfere with display but do prevent WYSIWYG editors from trying to interpret the content as HTML.
Protect on savestyle to it.
.htmfiles are treated as plain text. Look through your Apache config (including
pubdirectory) for a line that says something like:
AddType text/plain .htm(probably with a bunch of other extensions). You can either remove
.htmfrom that list, or you can add a .htaccess for the pub/System/TinyMCEPlugin directory that contains the line
AddType text/html .htm