If I use a different theme for admin interface (for example Root Candy) and I use this interface to edit nodes and blocks, the WYSIWYG doesn't appear.

Not sure if this is a bug or a feature request. However, the administration of the WYSIWYG doesn't have any reference to themes or different behaviours depending of the theme used for editing.

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Fixed

Please read the FAQ: http://drupal.org/node/417166

alex.cunha’s picture

alex.cunha commented
Status: Fixed » Active

Sun, thanks for you help.

Yes, i have read the FAQ before post.
Sorry but I don't see any QA about this issue or something like.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

I tested all supported editors in Root Candy and they work fine.
I think sun referred to the first FAQ entry where Wysiwyg API works in the default themes but not a custom theme because $scripts or $closure is missing. These are present in Root Candy and if they were not you should get JavaScript errors.

robeano’s picture

robeano commented

I had aggressive caching and page compression on when I upgraded to 6.x-2.0. I found disabling these settings fixed the problem. The editor appears without error. I re-enabled the settings after the editor displayed and it is still working.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: WYSIWYG/TinyMCE doesn't work if using a diferent theme on admin interface » JS breaks after upgrade to 2.0 with aggressive caching enabled
Category: support » bug
Status: Active » Needs work

Sounds like we should add a module update function that flushes all relevant caches.

  // Change query-strings on css/js files to enforce reload for all users.
  _drupal_flush_css_js();

  drupal_clear_css_cache();
  drupal_clear_js_cache();

  // Rebuild the menu to remove old admin/settings/wysiwyg/profile item.
  menu_rebuild();

  // Flush content caches.
  cache_clear_all();
sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: JS breaks after upgrade to 2.0 with aggressive caching enabled » Caches need to be flushed after upgrade to 2.0 when caching is enabled

uhm. Better title.

alex.cunha’s picture

alex.cunha commented

I cleared the cache and disabled the cache and the editor doesn't appear.
This needs further investigation and debug.
I will try latter. And on other of my sites.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs work » Fixed

Thanks for reporting, reviewing, and testing! Committed to all 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.