editing1Add my vote for this tag wysiwyg1Add my vote for this tag create new tag
, view all tags

WysiwygPluginDev Discussion: Page for developer collaboration, enhancement requests, patches and improved versions on WysiwygPlugin contributed by the TWikiCommunity.
• Please let us know what you think of this extension.
• For support, check the existing questions, or ask a new support question in the Support web!
• Please file bug reports in the WysiwygPlugin bug database.
• See WysiwygPluginDevArchive for older discussions.

Feedback on WysiwygPlugin

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


-- 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 ...



-- 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.
Is this feasible?

-- 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


-- 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

I have a client who is very eager to cut and paste images from a word processor into the WYSIWYG editor. I've found two (commercial) HTML editors (EditLive and eWebEditPro) that appear to support this.

Any ideas as to how difficult it would be to integrate them with WysiwygPlugin, or to extend TinyMCE? Anyone willing to help make this happen?

-- ClifKussmaul - 19 May 2008

When trying to run "perl WysiwygPlugin_installer" I receive this error: Could not load installer script from tools/extender.pl. If this is a TWiki release prior to 4.2, please download the latest version of the script from: http://twiki.org/cgi-bin/view/Codev/ExtenderScript and place it in the 'tools' directory below your installation root (create the directory if necessary). If this is TWiki 4.2 or later, the script is missing from your installation, or may be broken.

I'm running version 4.1.2 of TWiki, I have installed the latest version of extender.pl in the tools directory, and the permissions are correct, but I keep receiving this error. Any ideas what the problem might be?

-- VictoriaScallan - 07 Jul 2008

I found in the sub afterEditHandler, the following lines processing the utf8 output will give wrong message of "could not processing wide string". If ($Twiki::cfg{Site}{CharSet}=~/^utf-?8$/i) { $text = Encode::decode_utf8($text); }

The reason is perl processing the string as bytes stream, so it must be encode as utf8 before output. i modified it as follows, it works! If ($Twiki::cfg{Site}{CharSet}=~/^utf-?8$/i) { $text = Encode::decode_utf8($text);

$text = Encode::encode(‘utf-8’,$text); }

YanDongdong from paraEngine.com

-- YanDongdong - 29 Sep 2008

Trying to edit tables within WYSIWIG. Setting row colors looks great in the editor, but all color attributes are lost when I save (and when I look in the raw editor, there are not color tags). Everything reverts to the default table row colors. Is it something I'm doing wrong or do I need to report a bug?

-- PaulOpitz - 01 Dec 2008

Just to confirm that this isn't a site-specific issue, I tried this using the TWiki.org SandBox. Same thing happens, there. So, either I'm doing the same wrong thing both places or this is a bug.

-- PaulOpitz - 02 Dec 2008

We have plenty of topics where users are putting in custom html tags, so we've set WYSIWYG_EXCLUDE to calls,html. This works great, with one exception that I've noted. The indent feature of the editor uses the <blockquote> tag, which then causes the editor to revert to raw edit on subsequent edits.

Is there an easy way to add <blockquote> to the list of tags that don't revert to raw edit?

The doc has the line:

HTML tags (e.g. <div>, not including <br>), or 

Does this mean that <br> is the only tag that doesn't cause the wysiwyg to revert to the raw editor?

-- MatthewCardozo - 02 Apr 2009

This plugin stopped working for me at about the same time that I upgraded Firefox from 3.5.5 to 3.5.6 on my computer. Basically it just displays what you would see in Raw Edit, except without any carriage returns or linefeeds.

It works fine in IE8. Is anyone else having this problem?

-- TimJacob - 2009-12-22

TimJacob - did you try the same topics in IE and Firefox, if the sytax is complicated in the topic, twiki giveup on wysiwyg and throws normal TML/Raw Edit.

-- SopanShewale - 2009-12-23

Yes, I did try the exact same topic, and earlier versions of Firefox work also.

-- TimJacob - 2009-12-23

If you create a link using anchors, for example Do Something, the WYSIWYG Editor converts it to This Page#ThatSpot. It strips off the human readable portion

-- Tim Jacob - 2014-09-17

Tim, I created TWikibug:Item7551 to track this. Please add TWiki version you are using.

-- Peter Thoeny - 2014-09-18


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.

Topic attachments
I Attachment History Action Size Date Who Comment
Unknown file formatpatch WysiwygPlugin-expanded-cells.patch r1 manage 0.8 K 2007-03-20 - 14:50 EzequielConte This patch avoids empty cells to become expanded cells
Edit | Attach | Watch | Print version | History: r185 < r184 < r183 < r182 < r181 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r185 - 2014-09-18 - PeterThoeny
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2015 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.