Escaping headings from a TOC results in corruption when edited with the WysiwygPlugin. We often use the 'pling pling' syntax to stop headings from appearing in a TOC. Wysiwyg seems to corrupt this.

Before WYSIWYG editing:

---+!!%TOPIC%

After WYSIWYG editing:

---+ !%<nop>TOPIC%   

You can see a space is added, and the second exclamation mark is replaced with a <nop> tag. This makes the topic look really ugly.

-- TWiki:Main/SteveJonesST - 22 Aug 2007

OK, let's try it:

Flibble

Hmmm. Looks OK to me. Can you reproduce in an example LitterTray web? I suspect you are testing using an old version of WysiwygPlugin.... CC Reproduced at TestTopic8, and also on my own installation with the latest WysiwygPlugin. Let me know if you need more, Steve.

-- TWiki:Main.SteveJonesST - 04 Sep 2007

Some more info - this syntax is OK:

---+!! %TOPIC%

But this is not:

---+!!%TOPIC%

So, the lack of space between the exclamation marks and the % causes incorrect translation to TML, even though it is valid syntax. Hope this is helpful. -- TWiki:Main.SteveJonesST - 04 Sep 2007

OK, So here's a heading with a double exclam:

This is a heading

Save Edit again and it appears correctly Save again Still works. Can you reproduce this problem in LitterTray Web please? AFAICT it works fine.

CC

Hi Crawford. Can you try editing TestTopic9. It broke when I edited it, and I've put it back to it's pre-broken state. I think the point is that the heading is a variable, has no space before, and is double exclam escaped. Thanks for your patience.

An aside - I saw your message that TinyMCE should be OK on 4.0.5. I would prefer to use this, but I need to map it to the WYSIWYG button, not the standard edit button. Can I do this easily ?

-- TWiki:Main.SteveJonesST - 04 Sep 2007

OIC, sorry, I misunderstood your report. An example always helps a lot.

To map to the WYSIWYG button, modify the view template to invoke edit...?nowysiwyg=1 for the "normal" edit, and move the old edit link to the WYSIWYG button.

-- TWiki:Main.CrawfordCurrie - 04 Sep 2007

This is due to the order in whcih !% is interpreted. I had to bring it earlier in the rendering cycle for other reasons, and didn't realise at the time that ---+!!% would get caught by it (it's one of those vague, undefined things in TML)

Anyway, I made it consistent with the rendering.

CC