Table of Contents
Compatible with DokuWiki
This extension is marked as obsoleted. Therefore it is hidden in the Extension Manager and the extension listing. Furthermore, it is candidate for removal.
This extension has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues.
Similar to aceeditor, fckw, grensladawritezor, prosemirror, skydoku, wysiwyg_nicedit
Recent alternative: ckgedit plugin
Conflicts with: Monobook template — Editing box hides under left side logo in Monobook.
What You See Is What You Get (WYSIWYG) editors run against the grain of DokuWiki markup. On the other hand, they are sometimes exactly what you need.
In the DokuWiki editor, use the following syntax:
<wysiwyg name /> <code>Regular DokuWiki markup.... <wysiwyg name />
More regular DokuWiki markup
<wysiwyg anothername /> </code>
and so forth. After saving this gives you something like:
Click on one of the edit buttons, and:
That's pretty much all there is to it. See below for admin details.
- You can override the “Create Page” behaviour for particular users by adding them to the 'wysiwyg' group. When they create a page now, they get an entire wysiwyg page.
- It's a good idea to disable section edit if you're using WYSIWYG. (Set “Maximum section edit level” to 0.)
The first time a browser loads a page with WYSIWYG in it is slow. FCKeditor is big. But it does get cached, so subsequent pages should be quick.
- Firefox 22.214.171.124
- IE6 (Uses old-style toolbar.)
- Safari 3.0.3 (on pc)
- Google Chrome 2.0
- Opera 11.1
The editable portions are stored within the DokuWiki *.txt file, in /data/pages. The reason it is stored here rather than metadata is so that if (read: 'when') files get moved about and renamed, the data won't get destroyed.
The editable portions are hidden from the user when editing from within the DokuWiki editor.1
Please report all bugs to me at Luke Howson
Client side editor
The client side editor used is FCKeditor.
WYSIWYG boxes are searchable.
Locking works at page-level granularity.
These work as expected.
Why doesn't WYSIWYG read and write DokuWiki syntax?
The design philosophy of this plugin is to separate the “expert” DokuWiki syntax from the “basic” WYSIWYG editor. Lots of third party plugins can be used recursively, or require complicated or low level concepts that cannot be easily represented in a WYSIWYG editor. Further, I don't think there is a general way to allow such an editor to use arbitrary plugins.
There are several drawbacks to this separation:
- users are unlikely to learn DokuWiki syntax. There is no simple path from “basic” to “advanced” use.
- a few things don't work as expected. (Search currently shows unrendered HTML in its output);
- uninstall will be difficult.
I just updated the translation file for Spanish speaking people here it is.
Please use the discussion page for general discussion.