Collapsible fieldsets aren't collapsed in popup image upload form

Yes, this is something that's often tweaked me about this and seeing this bug tonight prompted me to track it down.

The problem actually appears to reside in the tiny mce module (but I have a hack for you). There is a setting for the tiny mce module that allows you to use the theme css. However, it doesn't appear to work right. Therefore, when img_assist loads, it asks tinymce what css to use and it gets the tinymce default css.

I simply disabled the check so it loads all the css files like any other page. A patch is attached, but you don't like patches, just edit img_assist.module and add false to line 1731, like such:

$output .= " if (false && parent.tinyMCE) {\n";

Much sexier output now :-)

Again, this is not a fix, but a hack to make it work. Perhaps now that the devs know where to look, they can make a real fix. (although, to be honest, this page will always look like ass if system.css isn't included anyways.)

What happens if you merge the contents of if and else in that code, so TinyMCE's and Drupal's stylesheets are loaded concurrently?

The bug reported in #2 above persists. I'm using version 5.x-2-alpha1 along with TinyMCE 3 and Wysiwyg.

In my case, when I popup the image assist dialog from tiny tinymce button, no css styles are being embedded properly, not even the default TinyMCE css.

Using my rudimentary javascript debugging skills if I put an alert in the image_assist.module around line 1788 as follows:

  $output .= "  if (parent.tinyMCE) {\n";
  $output .= "  alert(parent.tinyMCEPopup.getParam(\"popups_css\"));\n"; // my debugging
  $output .= "    document.write('<link href=\"' + parent.tinyMCEPopup.getParam(\"popups_css\") + '\" rel=\"stylesheet\" type=\"text/css\">');\n";
  $output .= "  } else {\n";

The alert msg on the browser says "undefined."

Using the hack in #2, I was at least able to get the drupal css into the form.

Not sure how to fix this as I don't understand the getParam(popups_css) bit.

Thanks,
Mike

Hm. Did you check the version of this issue?

I did. The same issue seems to be cropping up in the newer version of the module so I bumped this thread rather than start a new issue...

Mike

Well, there are fundamental differences between 1.x and 2.x. Either this issue is reclassified as bug in 2.x, or I'm going to mark this issue won't fix, since I will not waste any more time with 1.x.

Sun, totally understand.

I'll go ahead and reclassify this issue. If that causes any problems, please let me know and I'll start a new one...

Mike

This issue is not going to be fixed anymore.