I use D 6.19, Wysiwyg 6.x-2.1, TinyMCE 3.3.8

It all works fine for FF but the editor simply just doesnt appear for Chrome and IE....any idea?

Comments

twod’s picture

Status: Active » Postponed (maintainer needs more info)

Have ou tried the 6.x-2.x-dev version to see if this has already been fixed?
Are you seeing any JavaScript errors in Chrome's console (Ctrl+Shift+J) or IE's lower left corner?

pramudya81’s picture

Hi 6.x-2.x-dev version does not solve the problem.

And I don't see any error in Chrome's console (Ctrl+Shift+J) or IE's lower left corner.

I tried to unable the css and js compression too but still same issue occurs.

Thx.

pramudya81’s picture

Anything on this yet?

If you want to try go to www.dakiunta.com
user : cheline
pass : cheline

Try to create a posting and see that the wysiwyg is not appear on IE and chrome.

Regards

twod’s picture

It looks like you are missing wysiwyg.js, Wysiwyg's main JavaScript file. Perhaps there were problems when aggregating or minifying it? The file is there, so rebuilding the minified JavaScript file should do the trick.

If I execute the scrips from that file manually, the editor does appear. Not sure why it happens only in IE and Chrome (I only had IE to test with here at work), unless some module is doing some browser detection and adding scripts conditionally based on that. If that's what's happening, Drupal could be serving broken cached files to those browsers only, while the others get working cached files.

Can you try disabling JavaScript optimization/aggregation/minification and test with the browsers again?

sun’s picture

Category: bug » support
Status: Postponed (maintainer needs more info) » Fixed
pramudya81’s picture

Hi, I tried to disable both CSS and Javascript optimization also the minification.

No work. Issue remains. Nobody else facing the same problem? Only me?

Regards

sw3b’s picture

Same thing for me ! Tiny MCE is not working anymore after going to 2.2 or the latest DEV version !

But after editing de profile in Wysiwig profile and adding the options manually. Tiny MCE is OK. You have to add your icon manually and if do not do this step is just a TinyMce who is blank on the page. Before when to not choose option all the basic are show but not anymore.

Choose your option and it should be OK. Have you tried this ?

twod’s picture

@sw3b, what you're seeing is expected, see #1003850: 6.x-2.2 has no toolbar buttons by default.

@pramudya81, there's a syntax error where the second minified JavaScript file gets inserted (that's where wysiwyg.js is included, not in the file from the header like I said earlier, sorry). IE chokes when it sees </div and then the script tag so it just ignores it. Other browsers seem to figure out that it's a closing div tag and are able to fetch the script normally.
I think you need to move the printing of the $closure variable in your page.tpl.php slightly to fix that.

Btw, I noticed that the script loaded from kumpulblogger.com took a very long time to load, and the image it in turn tries to load takes even longer. This also delays the time before scripts are executed (onload), look at the Smilies fieldset and you'll notice it takes a while before you can click it.

pramudya81’s picture

Hi TwoD,

Where to move the $closure to? I am dumb to technical issue.

Anyway could this be user role related?

If I use user to login
IE : No works (X)
Chrome : No works (X)
FF : Works

If I use admin to login
IE : No Works (X)
Chrome : Works
FF : Works

Regards

pramudya81’s picture

Maybe you should try on Chrome. IE is very slow. And I dont know why Kumpulblogger so slow on IE.

Regards

twod’s picture

No, it's not role related because the $closure variable in page.tpl.php is always printed in the same place.
It works in Chrome and FF because they interpret the malformed HTML markup despite the script tag being "inside" a div tag.

Look near the bottom of page.tpl.php in your theme and copy the code around where $closure is printed, a few rows before and a few rows after would be enough, then paste it here and I'll see if I can spot the issue. Use <code></code> wrappers so the filters here won't mangle it.

pramudya81’s picture

Hi, thanks for your willingness to see the code.

<!-- footer -->
<div id="footer" class="clear-block">
 
  <?php echo $footer ?>

<div class="clear-both">
  Copyright &copy; 2010 <a href="<?php print $base_path ?>"><?php print $site_name ?></a></div
  <?php echo $footer_message ?>
  <?php echo $closure ?>
</div>

</div>
<!-- /footer -->

Above this code are some block / column script, below this code are some Google analytic scripts.

Regards

sun’s picture

Try to move the $closure to after the end of your page template markup, but still within BODY.

michael_lessard_micles.biz’s picture

In my case, such issues were caused by jquery files (*.js) not being installed properly in the Drupal /misc folder. This should normally only be a Drupal 5 problem, as Drupal 6 allows the module to auto-place the files in /misc, but since a missing .js in /misc does cause such issues, I thought I might mention it as a place to look...

michael_lessard_micles.biz’s picture

Almost forgot : another common reason why TinyMCE does not appear is language.

If you select, for example, French, but you have not installed the French translations in libraries/tinymce/jsscripts/tiny_mce/..., then this editor will simply not show up at all.

twod’s picture

  Copyright &copy; 2010 <a href="<?php print $base_path ?>"><?php print $site_name ?></a></div

There's a missing > last on this line.
And like Sun suggested, I'd move this to just before the body, less chance it'll interfere with the footer and it'll allow all markup to be loaded before scripts start to load.

  <?php echo $closure ?>
</body>
pramudya81’s picture

Hi,

Thanks a lot to TwoD and Sun.

That was a good pointing to missing ">" for div. I feel so dumb-dumb now, not noticing the missing syntax at the first place.

I added the missing ">" and move the $closure just before . Now it works fine.

Thanks all. Please close this thread then.

Regards

Status: Fixed » Closed (fixed)

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