• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

In reference to Item1972 which discusses how to enable WysiwygPlugin under NatSkin...

Once enabled, all edits will take place under Kupu. There are known problems with such an arrangement, however: http://twiki.org/cgi-bin/view/Support/WYSIWYGEditorBreaksSystemTopics

It would be much better to offer a choice of editors like PatternSkin does. I would have offered a patch myself, except that the relevant HTML is being generated by Perl code rather than by a template.

If you want to prevent a topic from being edited using Kupu under NatSkin then add

   * Set USEWYSIGYG = off

to it ... in theory. Oh, but I just found out that the NatSkinPlugin does not check that correctly. Will be fixed.

Generally speaking, offering the raw edit and the wysiwyg edit option on every page is not a good idea for several reasons.

First, as you said, there are issues editing the same topic in different modes, i.e. system topics or similar special topics. Using PatternSkin the users still gets the choice to edit in one or the other mode without any means to protect special topics from being corrupted, afaik.

Second, with regards to usability having two different buttons where one is called "Wysiwyg" and the other "Edit" has potential to confuse more than it helps. I think, most users will be very confused by a string of chars such as "W Y S I W Y G" not being a proper word anyway. You can't assume that everybody knows what that is referring to. So NatSkin takes the stance to make it configurable on different levels -- site,web,user,topic -- which edit mode is used.

Last not least, wysiwyg editing is overrated wink .


Fixed the USEWYSIWYG bug mentioned above. If you still think that the NatSkin way of integrating Kupu is wrong then reopen this bug please. Or comment on TWiki:Plugins.NatSkinDev.


After installing the "-pre1" release of NatSkin and NatSkinPlugin, I am unable to get WYSIWYG editing at all under NatSkin. (Kupu still works in my installation under PatternSkin.) Using %ALLVARIABLES%, I confirmed that the "USEWYSIWYG" setting is being set to "on" in both my personal topic and Main.TWikiPreferences. Have I missed something?


Fixed (again). Grr.

Note, that you have to install the WysiwygPlugin and enable it using configure


Summary WysiwygPlugin, if enabled, should be optional
ReportedBy TWiki:Main.ScottBarnes
Codebase 4.0.4
SVN Range

AppliesTo Extension
Component NatSkinPlugin
Priority Normal
CurrentState Closed

Checkins 11216
TargetRelease n/a
Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r7 - 2006-08-15 - MichaelDaum
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback