TinyMCE upgrade to 2.0.5, editor gone

[stephan.b]

Ik was running TinyMCE 2.0.4, no problem.

Now I'm trying to upgrade to 2.0.5 using Module Manager.
It seems ok, the TinyMCE options are popping up, but in the editor field, I only get plain html.

Does anybody know how I can get the upgraded TinyMCE editor get in action?

[chead]

Out of curiosity, does your admin/header.php file have compression enabled?

Something like:
@ob_start('ob_gzhandler');
@ob_start('gzhandler');

Instead of the default/original:
@ob_start();

The WYSIWYG editor in TinyMCE 2.0.5 didn't display for me either unitil I reverted that line back to its original without compression.

I don't know if that applies; if not, anything unique about your site that can help for debugging?

[cyberman]

The WYSIWYG editor in TinyMCE 2.0.5 didn't display for me either unitil I reverted that line back to its original without compression.

TinyMCE module supports zip compression by himself. It looks like double activating creates some problems. But you can deactivate it inside module admin ...

[chead]

I thought the double-compression might be the issue, too, but disabling/enabling the option in the TinyMCE configuration panel didn't help.

For me, it was the use of @ob_start('gzhandler') that caused the issue. (I had just set it prior to upgrading TinyMCE, or it might not have even occurred to me.) 2.0.5 worked without it; didn't work with it. I hadn't been using compression long enough to feel the loss of any speed benefit, so I just returned to @ob_start(). 

[Russ]

1. I had an out of memory error in NuSoap module whilst trying to install with the module manager. Probably a real out of memory error? Zip install went OK.

2. I don't seem to have any problems with compression?

3. I do have problems with instead of and instead of . I have everything checked and have cleared caches, closed browser and re-opened. Anyone have any ideas - I'm sure this worked in the previous version?

Russ

[Hare]

This might be a silly question but better make sure... Have you selected TinyMCE again from your personal settings? If you uninstall TinyMCE CMSMS can revert to "no wysiwyg" setting.

[stephan.b]

Out of curiosity, does your admin/header.php file have compression enabled?

Something like:
@ob_start('ob_gzhandler');
@ob_start('gzhandler');

Instead of the default/original:
@ob_start();

The WYSIWYG editor in TinyMCE 2.0.5 didn't display for me either unitil I reverted that line back to its original without compression.

I don't know if that applies; if not, anything unique about your site that can help for debugging?

Thanks for all your replies!
Well I checked the admin/header.php, it was/is like you suggested @ob_start()

Ik also tried unchecking compression, without succes, tried to completely remove tinymce, and then upgrade.
Tried with xml-file upgrading, and zip... no succes

In all cases, I checked tinymce as my editor in preverences, and het set permissions like it should.

I also agree about that and issue, I hoped for this to be an option in the upgrade

[chead]

I've now seen the "disappearing editor" issue -- though it happened on 2.0.4. Maybe a breakthrough in diagnosing the issue:

A site I recently migrated is working perfectly, except that TinyMCE isn't working on the new site. Comparing the source of the admin pages between the working site and the non-working site, I see that the Javascript to initialize TinyMCE is in the wrong place on the broken site.

On the working site, there are a few tags that import/include the TinyMCE routines and configuration right where they belong, between the and tags.

Code: Select all

<link rel="stylesheet" type="text/css" href="style.php" />

		<__script__ type="text/javascript" src="http://mysite/modules/TinyMCE/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php"></__script>
		<__script__ type="text/javascript" src="http://mysite/modules/TinyMCE/tinyconfig.php"></__script> 
<__script__ type="text/javascript" src="themes/default/includes/standard.js"></__script>

On the broken site, the first tag is at the very top of the source, followed by some CMS Javascript, then the actual Javascript TinyMCE configuration code (it isn't included by reference) ... well before the and tags.

Code: Select all

		<__script__ type="text/javascript" src="http://mysite2/modules/TinyMCE/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php"></__script>
		<__script__ type="text/javascript">

		function CMSmsCustomCleanup(type, value) {
			var start, end, previous_end, valuein, s;
			switch (type) {
				case "get_from_editor":
				start = -1;
				end = 0;
... code snipped ...
		tinyMCE.init({
			mode : "exact",
			elements : "content",
			content_css : "http://mysite2/modules/TinyMCE/content_css.php?mediatype=screen&templateid=",
			cleanup_callback : "CMSmsCustomCleanup",
... code snipped ...
			trim_span_elements : "false"
		});
		</__script>

		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
	"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<__html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

<head>

That explains why the editor isn't showing: it's never initialized, and depending on your browser/preferences you may or may not see a Javascript error about TinyMCE not being 'defined.'

Since all source files (except config) were copied from the working server to the new server, the code should be the same.

Those of you experiencing the issue, "view source" for the admin page. Are you seeing the same thing I am?

Devs, any idea about why TinyMCE is trying to initialize itself so early?

[Russ]

OK, I had a bit of a look and this seems to work.

1. For the incorrect and instead of the correct and respectively, I found that replacing the whole of the  'valid_elements : ""' section in the tinyconfig.php with the one here:
http://tinymce.moxiecode.com/punbb/viewtopic.php?pid=62#p62
gives you back and
I don't have time to check what is wrong at present but this fixes it for me.

2. As for compression, I use:

Code: Select all

#$Id: index.php 3767 2007-01-23 17:23:45Z wishy $
#Adds gzip compression
if (function_exists('gzopen'))@ob_start('ob_gzhandler'); else @ob_start();

which seems to work fine with 'Use TinyMCE compression module' checked.

Let me know if these work for you.

Russ

[Vin]

1. For the incorrect and instead of the correct and respectively, I found that replacing the whole of the  'valid_elements : ""' section in the tinyconfig.php with the one here:
http://tinymce.moxiecode.com/punbb/view ... pid=62#p62
gives you back and

Thanks a lot for searching. However, changing just the "verify_html" to true in tinyconfig.php sufficed. BTW, this is not the issue for IE, which doesn't need the value "true". Odd.

[Russ]

Thanks Yin, to be honest I just copied and pasted a working example I had! But here are a few more solutions / problems.

1. As you maybe aware the 'media' plugin for TinyMCE  does not seem to produce valid XHTML. Code from the a solution of sorts can be found here - just thought you'd like to know
http://modxcms.com/forums/index.php/topic,11127.msg75414.html#msg75414

I've applied the patch and it seems to work OK, I'm just trying to get it to work with the EnhancedXSPF module. Actually just got it working - I'll post on a list for it.

2. There seems to be another flaw with the media plugin - when clicking on a file name in the file browser (FCKeditor Resources Editor in TinyMCE) the file is selected in the underlying media dialog box but the FCKeditor Resources Browser just stays there and doesn't close and return you to the media dialog?

Russ