• 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.
I just did a quick Wysiwyg test.

And the first topic I tried was a test topic with this

%SEARCH{ "This2IsAWikiWord" regex="off" format="%CALC{$IF(0 != 1, <nop>, | $summary |)}%" }%

and after opening the topic and saving it the NOP is gone.

%SEARCH{ "This2IsAWikiWord" regex="off" format="%CALC{$IF(0 != 1, , | $summary |)}%" }%

Too many topics get "molested" just by opening and saving. This is the main reason why many people incl myself have stopped using Wysiwyg. It would be really nice if we could make Wyiswyg able to preserve the advanced Twiki vars people have made in topics.

The plugin should encapsulate anything inside TWikiVariables and never ever touch it and alter it. No matter what is inside.


+1 for integrating CraigMeyers patch at TWiki:Plugins.WysiwygPluginDev (05 Jul 2006).

-- SP

Craig's patch was integrated quite some time ago.

I can change the defaults for the plugin to make it refuse to edit topics with TML or HTML in it. That's probably the best thing to do. Done.


That is not a solution to the problem. Making Wysiwyg refuse topics with TML or HTML is the same as uninstalling it. There is at least TML is the major bulk of our topics. Our entire ISO9000 system cannot be edited with this limitation. And it is very confusing that a user clicks Wysiwyg and is then refused or given the normal editor.

The plugin needs to totally not touch anything inside a Twiki variable. And if Craig's patch was integrated then it is just not good enough.

We need to get our Wysiwyg working now. Our competitors are getting better and better Wysiwyg.


Indeed. However the structure of TML makes it next to impossible to do anything better. There is an approach where you cache the contents of the variables server-side, and expand on topic save, but it's a lot of work to get right.

However it could be done, so marking as Actioning in the hope that someone will pick it up and do it. The author of TWiki:Plugins.XinhaPlugin has been talking about it.


"in the hope that someone will pick it up"... That means NEW. Not actioning.

As agreed in recent discussion on twiki-dev. Bugs marked as Actioning will not even be opened by anyone because we all think someone else is working on it.


Reverting to Actioning, as per the state descriptions. Please read http://twiki.org/cgi-bin/view/Codev/Post4Point1BugDBImprovements.


I finally bit the bullet and stopped trying to be clever. All of a sudden everything works a lot better....,.


Summary WysiwygPlugin alters things inside complex twiki vars so they break
ReportedBy TWiki:Main.KennethLavrsen
Codebase 4.0.5, ~twiki4
SVN Range TWiki-4.1, Tue, 28 Nov 2006, build 12081
AppliesTo Extension
Component WysiwygPlugin
Priority Normal
CurrentState Closed

Checkins TWikirev:12153 TWikirev:14501 TWikirev:14502
TargetRelease minor
ReleasedIn 4.2.0
Edit | Attach | Watch | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r14 - 2008-01-22 - KennethLavrsen
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback