Using latest versions of everything (today), I cant switch an input format while editing a Page. Doing so will remove the editor (although buttons disable rich text remain). Switching back to the original input format does not make the editor re-appear. Its simply gone once you switch an input format and therefore and unworkable situation.

I was using FCKeditor and Jwysiwyg.

CommentFileSizeAuthor
#10 wysiwyg_tinymce_flash_media_plugins.patch2.12 KBTwoD
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

TwoD’s picture

Which browser is this in? Any errors?
We know this happens with FCKeditor and Konqueror but have so far been unable to debug it. #414768: FYI, WYSIWYG breaks Konqueror

design4effect’s picture

I found the same thing on a fresh install of Drupal 6.10 the wysiwyg API and TinyMCE 3.2.2.3

I enabled the editor for the two HTML formats but not for PHP.

I noticed that I could switch back and forth between PHP (raw code) and the default TinyMCE format (filteredHTML).
The editor would disappear and reappear as expected.

But if I switched between two TinyMCE formats (ie FilteredHTML/FullHTML) the editor would disappear.
Only way to get it back was to exit the page and go back again.

- Kent

TwoD’s picture

I am unable to reproduce this in Firefox 3.0.8 on Drupal 6.10 with Wysiwyg's latest version (HEAD) and TinyMCE 3.2.2.3. I also have Image Assist installed on both sites I tested with, but if I understood you correctly this happens with the default editor settings?
You did not specify which browser(s) you are using, or if there are any JavaScript errors. That information is vital.
A link to a site where the problem exists (if it's open to the public) would also be helpful.

design4effect’s picture

Component: Editor - FCKeditor » Editor - TinyMCE

After uninstalling wysiwyg API I tried the Texy filter and every time I went to preview the page it switched back to Filtered HTML.

So, I deactivated Better Formats

Now it's working as it should (Texy anyways).

I haven't researched it thoroughly but I think Better Formats might be having a problem dealing with the admin user without explicit permissions.

- Kent

sun’s picture

Status: Active » Closed (won't fix)

Either answer TwoD's questions or stop asking for support.

Anonymous’s picture

It happened in Firefox 3.0.8, with FCK 2.6.4.

jwilson3’s picture

I have the same issue with WYSIWYG + TinyMCE on Filtered HTML and Full HTML.

1) the default input format is set to Full HTML.

2) using Better Formats, the anonymous user AND authenticated user are set to use only Filtered HTML for both nodes and comments.

3) when going to edit / create a node as SUPER admin (user 1), i would expect the default input format of Full HTML to be set, but it is not.

This also leads me to believe, just like design4effect, that Better Formats doesn't deal with the super user correctly.

* WYSIWYG 6.x-2.0-alpha1
* Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.10) Gecko/2009042315 Firefox/3.0.10
* TinyMCE latest (3.2.4.1)

jwilson3’s picture

So I continued testing... to get back to the original problem. I created a custom Role called "admin" and assigned User 1 to that role, and in Better Formats, set the default input format for the "admin" role to be Full HTML. Went to create a node, and sure enough, i get the correct default format, but no rich text (TinyMCE) editor.

* upon switching to Filtered HTML input in the node edit page the trimmed down TinyMCE editor does not appear, and there are no javascript errors.
* upon toggling the 'enable/disable rich text' link no editors appear and no javascript errors occur

Note that the original problem was that the editor shows up fine when the default is 'filtered html' but switching to full disables all rich text editors forever. Now, with Full HTML set as the default, i cannot ever get a rich text editor to display.

jwilson3’s picture

It took me a while, and some crazy combination of the buttons and plugin configurations, but finally nailed down why the advanced HTML editor wasn't appearing... it was because the Flash button was enabled in the TinyMCE configuration screen. There may be other buttons that cause this too, but that was the first one I found to cause the problem. Strange that no JS error popped up.

If that button is disabled, I can switch between filtered - full and the wysiwyg editor also changes seamlessly.

TwoD’s picture

Thank you for nailing it down to the Flash plugin.
The Wysiwyg API implementation for TinyMCE was created before the Flash plugin was replaced by the Media plugin.
Since you use the latest TinyMCE version, enabling the Flash plugin, which no longer exists, causes the initialization to fail.

I have created a quick patch which checks if TinyMCE is detected to be above version 2.0.6 and then enables the Media plugin (default settings).
It also checks if it's above version 3 and then no longer includes the Flash plugin.
Note that both should not be enabled at the same time, TinyMCE should show an error message in that case.

I've only made a quick test of Media plugin in FF3 and would appreciate if more people could help testing this.

TwoD’s picture

Status: Closed (won't fix) » Needs review

Sorry, forgot to change status...

Josh Waihi’s picture

oh awesome stuff, subscribing

sun’s picture

Status: Needs review » Fixed

Thanks for reporting, reviewing, and testing! Committed a slightly modified version of this patch to all 2.x branches.

A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.