Question

• I have initially installed and enabled the WysiwygPlugin and KupuContrib plugins. I have recently installed the TinyMCEPlugin plugin but cannot make it work (edit opens raw text editing, Wysiwyg opens the kupu editor).

• I've tried the following measures to no avail:
  • On the sitelevel preferences, removed the references to Kupu in the COMPOSER and the WYSWIYGPLUGIN_WYSIWYGSKIN flags.
  • Supply TinyMCE in the cover url (e.g.

    topicurl?cover=TinyMCE

    ).
  • Disable the WysiwygPlugin plugin.

• I was also wondering whether I should set the WYSIWYG_EXCLUDE flag to any specific value?

Environment

-- EyalTeutsch - 20 Sep 2007

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

What happens if you start a new topic? At least in this case, TinyMCEPlugin should open even if WYSIWYG_EXCLUDE is set.

-- MartinKaufmann - 20 Sep 2007

edit opens the raw TML editor, no trace of the TinyMCEPlugin editor (and I have enabled it in the Plugin section of the configure page).

-- EyalTeutsch - 20 Sep 2007

It seems that on new topics the editor loads ok. It is only on some of the existing ones that it won't load. Doesn't seem as a cahce related issue as cleaning the cache did not help.

-- EyalTeutsch - 20 Sep 2007

Have you updated the WysiwygPlugin recently? TinyMCEPlugin requires a fairly recent version to run. Any error messages in your web server log?

-- MartinKaufmann - 20 Sep 2007

Ah right, so it does work for new topics? What is the WYSIWYG_EXCLUDE variable set to? Try to leave it empty for testing.

-- MartinKaufmann - 20 Sep 2007

I guess the fact that it switches itself off on some topics, is related to the following paragraph in TinyMCEPlugin: The editor automatically "switches itself off" (i.e. reverts to the old text-only window) when editing topics that contain TWiki content it can't handle, such as complex TWiki variables.

What actually makes a twiki variable to be a complex one?

-- EyalTeutsch - 20 Sep 2007

A TWiki variable is "complex" if it has parameters - for example %COMPLEX{...}% versus %SIMPLE%. The reason complex variables are distinguished is that the parameter values can contain HTML, which messes up the translator.

However the latest WysiwygPlugin should work 99% of the time with the WYSIWYG_EXCLUDE clear.

-- CrawfordCurrie - 22 Sep 2007

Hi, I have the same problem with TinyMCEPlugin on TWiki 4.1. I tried all of the above suggestions but TinyMCEPlugin wont open; not even with new topics. I have the latest WysiwygPlugin installed and InstalledPlugins shows no errors but both Plugins as activated. Any further ideas?

-- JanStrube - 24 Oct 2008

Same problem. IE 6, FF6, TWiki 4.1.2 Installed plugins is clear. WysiwygPlugin ( 03 Aug 2008 ) TinyMCEPlugin ( 03 Aug 2008 )

Installation goes through flawless. But no editor shows up anywhere. Raw edit is still raw and wysiwyg is still wysiwyg. We have some settings in the TWikiPreferences on the wysiwyg plugin, can this be the problem? (composer etc.) I tried removing pretty much anything related but didn't get it working.

SmartEditAddon was easier to install into a custom skin compared to this /rant

We are planning to take this into use, but the problems here prevent it.

Would appreciate any advice.

-- SakariKaikkonen - 03 Dec 2008

Ok. It appears that the class-name used to init the the plugin has changed. Which is NOT mentioned in the documentation, or very well hidden. Changing the classaname in the edit.pattern.tmpl for the textarea seems to work. I got this from this bugreport.

Thanks guys.

-- SakariKaikkonen - 03 Dec 2008

Closing this as it seems to be answered.

-- PeterThoeny - 04 Dec 2008

I am reopening this, because I'm having a similar problem in 4.12 (TinyMCE is installed but I can't use it with pattern skin), but I don't understand the solution. I just downloaded the latest TinyMCE and WYSIWYG plugins, and they show as installed correctly. If I try to edit a page using

?composer=%COMPOSER%

It must be a template issue.

Per the last comment re changing the classname in edit.pattern.tmpl, I change the textarea class from twikiEditboxStyleProportional to twikiTextarea but I'm not sure that's what the bug report meant, and it doesn't seem to work for me anyway. Can someone clarify what in http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item5547 fixes this problem?

Thanks!

-- KathyDeLaCruz - 25 Feb 2009

OK, I have found more details in this bug reports and I have changed the Tiny MCE Plugin page's editor_selector setting to twikiEditboxStyleProportional but it still doesn't work (even after disabling & re-enabling Tiny MCE and WYSIWYG plugins, and clearing the browser's cache)

Anything I'm missing?

-- KathyDeLaCruz - 25 Feb 2009