Feedback on WysiwygPlugin

Please add feedback here. I'm interested in usability and bugs.

PLEASE ADD BUG REPORTS TO Bugs:WysiwygPlugin - THANKS

-- CrawfordCurrie

Since I split KupuContrib out of this package, I archived the current feedback to WysiwygPluginDevArchive

-- CrawfordCurrie - 03 Dec 2006

There's a broken link: TWiki:Plugins.KupuEditorContrib

I think it should be TWiki:Plugins.KupuContrib ...

Cheers,

Carlo

-- CarloSchulz - 12 Mar 2007

I've made a patch to solve a problem related to empty cells on tables. WysiwigPlugin always converts them to a expanded cell. In the patch, empty cells stay as empty cells on view and edit modes. The %SPAN% variable will only be displayed in edit if the cell is really a expanded cell.

-- EzequielConte - 20 Mar 2007

Thanks Ezequiel; I will review as soon as I get a chance.

Moved SashiKanth's question to NoButtonsInKupu

-- CrawfordCurrie - 02 May 2007

Is it possible to only use the Wysiwygplugin in certain topics, and not have the wysiwyg button in the toolbar on all the other topics?

-- JosMaccabiani - 01 Jun 2007

Wysiwygplugin, as it is, is at the same time great but useless because it messes up pages. It needs a little fix:

• Decide on page edit event, if page can be edited with WysiwygPlugin (i.e. it will not render important plugin variables useless).
• If non-standard syntax is found, revert to normal edit.
• Else, use wysiwyg.

-- MikkoLaakso - 05 Jul 2007

Mikko, that's how it works. See the doc, especially for WYSIWYG_EXCLUDE.

-- CrawfordCurrie - 30 Jul 2007

I just uploaded the latest version. I have taken a radical step, and removed most of the fancier bits that tried to do something smart with TML. It was getting it wrong far too often. Instead, the text is protected using entity encoding and spans, so the client editor can recognise text that is "special" to TWiki. Personally I think it gives a much better, more robust and accessible, editing experience for most users.

Kudos to ScottBlack for making it possible for me to pursue this work.

-- CrawfordCurrie - 10 Aug 2007

We are having some success using this plugin but WYSIWYG_EXCLUDE doesn't seem to be working for us. I assume this is to do with our set up rather than a bug. Can anyone confirm that it does work and where I should look to try to sort it out.

• Plugin version 14548.
• WYSIWYG_EXCLUDE set to html,calls in Main.TWikiPreferences.

-- TamsinTweddell - 23 Aug 2007

Tamsin, yes, it works. Use TinyMCEPlugin rather than KupuContrib.

-- CrawfordCurrie - 06 Sep 2007

It looks like an old copy of the Wysiwyg plugin has been uploaded accidently to the Wysiwyg Plugin page - I have downloaded both the zip and tgz files uploaded on Jan 25, 2008 and the downloads contain version 12422, not version 16290. Could someone update the web page. Thanks.

-- RobertgTaylor - 29 Jan 2008

I am sorry but the zip and tgz I uploaded the 25th are 16290 (25 Jan 2008).

I have double checked including comparing files against the subversion repository.

-- KennethLavrsen - 29 Jan 2008

When opening a file with ---## tags, recognised by the ExplicitNumberingPlugin the #'s are converted to +'s, hence effectively removing the numbering.

-- DoaitseSwierstra - 03 Feb 2008

Uploaded a new version of WysiwygPlugin. The one I uploaded last had missed the fix for avoiding a space being appended to each line bullet lists.

-- KennethLavrsen - 05 Feb 2008

I have TWiki 4.02 installed. On my InstalledPlugins? page, in the Plugin Diagnostics section, in the Handler/Plugin list, it says: "startRenderingHandler WysiwygPlugin This handler is deprecated - please check for updated versions of the plugins that use it! " I have the latest version of WysiwygPlugin (16350). Is this a concern?

-- SusanCassidy - 12 Mar 2008

I have just upgraded this plugin to the latest version (6 May) and am now finding that when I create a new topic, the signature at the bottom appears as

%0D%0A%0D%0A%0D%0A%0D%0A--%20Main.TamsinTweddell%20-%2009%20May%202008%0D%0A

-- TamsinTweddell - 09 May 2008

I had exactly the same experience one version or two ago (not this latest one) when I upgraded from the 4.2 shipped version. (Forgive the anecdotal nature of this info, but it may be of vague use if it rings any bells.) There was some odd behaviour. The dev version of the site was fine - the Unicode strings problem went away and all was well. When installed to the prod environment, this entities thing Tamsin mentions above happened. I replaced the new WysiwygPlugin and TinyMCEPlugin files with the original shipped ones, and then it behaved as on dev (unicode probs gone and no wacky strings), but of course it didn't last, and we went back to unicode strings. Of course I'm going to test the latest version and try again, but what could be causing the conversions immediately above? It's apparently happening with more than one version. Couldn't be caching, could it?

-- MarcusLeonard - 12 May 2008

On both WysiwygPlugin and TinyMCEPlugin, there is an error about the INCLUDED WysiwygPluginSettings? topic missing. Should this be fixed, or should they INCLUDE instead from the 4.2 web?

-- DavidWolfe - 13 May 2008

The easiest way to contribute code back is to attach a patch to this topic. You can either generate a proper patch using 'diff', or simply attach a zip of any new files you create. Please don't just dump a changed version here; I will simply ignore it.