-
Bug
-
Resolution: Fixed
-
High
-
2.0
-
None
-
Mac OS X 10.4.3 (Tiger)
Safari 2.0.2
Firefox 1.0.6
Camino 1.01a
Confluence 2.0
Summary:
Disabling WYSIWYG editor via General Configuration means that tinyMCE is not defined on the "Preview" page. You can't go back to the "WikiMarkup" page.
Discussion:
The editor doesn't seem to work for me in Camino (1.01a – Gecko browser for the Mac). When the "Edit" page first appears, a normal-size text window with the page content appears briefly and then is quickly replaced by a full-window-width Rich Text editor with no content. I decided to make the Rich Text editor the default editor and then later to disable it completely for everyone using the Administration preference in "General Configuration".
After I did that, the Rich Text editor doesn't appear as a tab when editing a page, which is fine. However, if you edit the page, go to "Preview" and then try to go back to the "WikiMarkup" page, you just get a spinning disc (very Mac OS X-like, by the way). Checking the JavaScript console in Firefox (this didn't work for me in Camino either), it's complaining that "tinyMCE" is not defined in the line:
var html = tinyMCE.getContent();
However, if you have the Rich Text editor enabled in the preferences but you're using the "WikiMarkup" editor, you don't get this error when going to "Preview" and back to "WikiMarkup". My guess is when you've disabled the Rich Text editor, the page doesn't load the relevant JavaScript classes/objects for it (but you don't check for that!) and so it fails.
If you try this in Safari 2.0.2, this isn't what happens. Safari 2.0.2 uses the "old" preview method, familiar from Confluence 1.4.x.
[CONFSERVER-4745] Disabling WYSIWYG editor causes AJAX error in Preview mode
Jeremy Higgs
added a comment - Hi Michelle,
I've been able to reproduce this on Firefox 1.5RC3 on Windows.. I'll look into it.
Jeremy
Jeremy Higgs
added a comment - Hi Michelle,
I've been able to reproduce this on Firefox 1.5RC3 on Windows.. I'll look into it.
Jeremy 
Hi Michelle,
I've fixed this issue and it will be included in the 2.0.1 release, which should be out shortly. Thanks for bringing it to our attention!
Jeremy