WYSIWYG editor content disappears

[ThePiston]

I created a site for a client and when she logs in to change something, she can see the contents in the editor for a brief moment, then it goes gray.  It works fine for me and all of my computers at work and at home... she has javascripts and java all enabled... any ideas?

[gharding]

Compare the URL she's entering in the address bar to the one entered in $mosConfig_live_site.  If they're different, you need to change one so that they're similar.

[ThePiston]

that's not it, i can do both from my computer no problem.

[amhazing]

Check configuration.php setting:

$mosConfig_live_site = 'http://www.amhazing.com.au'; (my site's setting obviously, not yours)

now by default fantastico (which is how I install mambo > Joomla these days) sets it to:

$mosConfig_live_site = 'http://amhazing.com.au';

and I get a similar WYSIWYG editor content not there error and javascript failure that you seem to be getting.  THe solution is to put in the www. at the front.

It's a pretty easy config to try.  It's an old bug that doesn't seem to have been dealt with.  What you'll find is that if you go to the site and you don't use the www to get there and your setting doesn't use www then the editor will work, but if you go to it with www. and the setting doesn't have www. it wont. (and vica versa)

Give it a go

regards,

H.

[ThePiston]

so, if i put www. in front of the URL, the the editor will work with both URLs or only http://www.url.com? 

[gharding]

Only http://www.url.com.  It's a bit of an annoying bug.

[ThePiston]

why does it work with both urls on my computer?  She is running explorer 6.0, does she need an update?

[beuvema]

I have a similar problem. It started today. in Firefox the HTML editor stopped working, and in Internet Explorer my Joomla site is not working properly in the back-end.

I think someting's wrong on the users computer as well as mine. I'am trying to figure out what might cause this. In the mean while I installed joomlafck editor....

I'll keep you informed...

Grtz Beuvema

[ThePiston]

well, we fixed our problem... it was the url problem, i just would like to know why it woks for me on both urls, and not her.

[amhazing]

Yep - took us ages to solve - found the answer in an obsure post about an earlier mambo version.  Was really hard to work out what was going on because some clients had the problem, and others didn't.  Originally thought it was a Javascript problem because that's the error message that comes up but when we set the URL it all came good

Shame it's not documented a bit better as a standard bug (maybe it is and I haven't seen it )

HL

[tijs]

I have exactly the same problem (content appears in gray and then all of a sudden disappears) and it is driving me nuts!  My URL was set with the www so that can't be the problem. Instead I think it is something to do with Firefox. In the latest Mozilla there is no problem, and neither is there any problem with the latest stable Firefox (1.0.7).

However, since the (much faster) 1.5 beta and release candidates versions came out, they don't seem to like the Joomla editors anymore, and there is the above problem. I have these issues both on Windows and Linux. It happens with both TinyMCE and MosCe, not with TMedit (HTML Area).

I hope this is just a Firefox bug and that they can sort this out.

[DeanMarshall]

Beta software is by definition prone to issues - sorry, but that's life.  I believe the Firefox beta issue is distinct from the Internet Explorer issue.

The Internet Explorer issue (mismatch of www. with live site variable) appears to be an attempt by Microsoft to restrict scripts to the same domain as the page being viewed. The presence in the url of the www prefix indicates a subdomain and is treated as a distinctly separate location than the domain without the www. prefix.

Whilst this mismatch and what looks like a Microsoft security policy lie at the heart of many instances of Internet Explorer / Joomla editor problems - it is by no means the cause of all.  Security / privacy / anti-virus / firewall / ad- blockers have all been implicated in blocking the javascript behind the editors and indeed the administration menus and buttons. Additionally, a few server configuration errors can stop the .js files being 'served' correctly.

Anyone who doesn't find a solution by editing the live site variable in configuration.php should consult this thread in the FAQs forum:
http://forum.joomla.org/index.php/topic,474.0.html

Dean Marshall.

[tijs]

The thing is, FF 1.5 is no longer beta but has already released its second release candidate. So I am wary this major annoyance will still be in the final version, which will prove most annoying for all of us who use a decent browser...

[DeanMarshall]

Depends on your definition of a decent browser

I have been a Firefox proponent for some time - but if they release a new version that doesn't work where previous versions did, then the issue lies fairly and squarely with them.

This bug report references Joomla and other scripts interfacing with wysiwyg editors.
https://bugzilla.mozilla.org/show_bug.c ... 61008 

Their forum also has a post or two that reference the issue
http://forums.mozillazine.org/viewtopic ... ght=joomla

Ity looks like the Mozilla people believe that this is a Joomla issue - but I haven't seen any evidence of inherent Joomla problems. I don't know whether anyone from the core team can liaise with them on this.

Dean Marshall.

[tijs]

Cheers Dean, thanks for these links, I didn't realise a bug had already been filed. In any case, now there is a catch 22, isn't there. It would be good if some developers could look into this.
I can only try to make some noise on this forum and the Mozillazine forum so that this hopefully gets fixed...

[san2k]

So what whell we do now? Wait?

[DeanMarshall]

So what whell we do now? Wait?

Add your voice to those on the Mozilla / Firefox forum - let them know you think that the problem is their end.

Dean.

[tijs]

But then they say there are no problems with other systems like forum software...

That it works OK in Fx 1.0.7 doesn't necessarily mean its a Fx bug. It could be they were relying on a bug in Gecko 1.7.x that got fixed for Gecko 1.8 (like the Amex "tall menus" problem). I have no idea if that's true here or not, though.

It won't be fixed for Fx 1.5/Gecko 1.8, though. Baring a major crasher, RC3=Fx 1.5.

So, who is right here?

In any case this is bad news for all Joomla users using Firefox, since very soon everybody will be upgraded to FF 1.5...

[random]

I have a solution, it may not be the right one but it works.

I start FF in Safemode and I can edit, in normal mode everything is invisable, I think it has to do with profiles, start a new profile and you can edit, not sure why this is but it is a fix.


I posted this in another thread also but relating to the same problem FYI

[heavyboots]

Hmmm, I'm tinkering with this on my Mac (Tiger 10.4.3/Apache1.3.33), trying to access via FireFox 1.5 and having no luck currently.

[1] This is a local site. So I've defined joomla to access it via the IP number. There is no 'www' involved--the url is http://10.0.0.10/joomla.

[2] Oddly enough, reloading the page after reaching it will result in a properly inited editing window. I am allowed to edit and Apply EXACTLY ONCE. Then I have to hit reload before I can make more edits. Grrrrrr.

[3] The offending code block is this:

Code: Select all

if(!tinyMCE.isMSIE&&doc.title!="blank_page"){
doc.location.href=tinyMCE.baseURL+"/blank.htm";  // This code always fails THE FIRST TIME LOADED in Firefox 1.5
window.setTimeout("tinyMCE.setupContent('"+editor_id+"');",1000);
return;
}

I have added lots of returns so I could find the exact bit that was dying; in the unedited /joomla/mambots/editors/mosce/jscripts/tiny_mce/tiny_mce.js file, this is part of line 90. The error code it generates is this:

Code: Select all

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMLocation.href]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: http://10.0.0.10/joomla/mambots/editors/mosce/jscripts/tiny_mce/tiny_mce.js :: anonymous :: line 90"  data: no]
Source File: http://10.0.0.10/joomla/mambots/editors/mosce/jscripts/tiny_mce/tiny_mce.js
Line: 90

I have also tried replace the code with a hardwired version to the blank.htm file, but that fails too, so it is definitely a problem with doc.location.href not working as expected apparently. (BTW, I tested the URL in an empty FireFox browser window and it does correctly load the blank.htm page, so I have the URL correctly entered!)

Code: Select all

if(!tinyMCE.isMSIE&&doc.title!="blank_page"){
// This line fails, so I tried hardwiring it but that also fails 
// --> doc.location.href=tinyMCE.baseURL+"/blank.htm";
doc.location.href="http://10.0.0.10/joomla/mambots/editors/mosce/jscripts/tiny_mce/blank.htm";
window.setTimeout("tinyMCE.setupContent('"+editor_id+"');",1000);
return;
}

[4] Lastly, I tried having FireFox 1.5 create a new profile, but that didn't change the situation at all.

Well, I suppose I will now go and copy this message into the Firefox bug report, but I just thought I'd toss this into the hopper in case it inspires anyone here to a sudden brainflash to fix this. I am not an actual programmer, I only play one occasionally at work!

[DeanMarshall]

@heavyboots : if you 'view -> source' of your page - with the editor loaded and examine the source do you see anything out of the ordinary.
In particular I am thinking about chunks of javascript within blocks with new line characters where there shouldn't be any. Do any javascript 'strings' get broken over two lines within the source?
Are there any errors reported in the javascript console once the editor locks up?
Have you read the posts from the FAQs section and ruled out all of the other common causes of editor (and admin menu) failures - the two are closely related relying on the underlying Javascript.

I think that non-printing character (control codes) embeded within the code are the most likely cause of these difficult to track problems.

If you see nothing out of the ordinary within the blocks - can you examine the linked .js files for similar 'irregularities'.

Dean.

[tijs]

I think the problem is with TinyMCE.

Recently the stable version 2.0 was released, and in the release notes it says among others:

The release of Firefox 1.5 resulted in new bugs and issues with TinyMCE so the 1.xx versions isn't very compatible with this browser.

(http://tinymce.moxiecode.com/)

So, I guess upgrading TinyMCE in Joomla will do the trick.

[heavyboots]

Yep, you're right. I just installed it and it works. I wonder what the deal was? Anyways, now I must go eat crow in the Mozilla bug reports area...  :P

Thanks for the info!

EDIT: Of course, now the question is... how to bring those bug-fixes (or all of the 2.0 code) across to mosCE?

[cwconley]

Ok.
newbie here.
i've downloaded the new TinyMCE.
how exactly do i load it and update it in Joomla?

thanks
chris wes

[heavyboots]

If I recall correctly, go into:

path-to-joomla/mambots/editors/

and rename the existing tinymce folder to tinymce_old (just in case this all goes horribly wrong!).

Then unzip the new tinymce folder into this location (it should now have the name tinymce just like the old one used to).

Toss the .zip file and you're done! 

[bry]

I just wanted to say you guys are awesome, you saved a lot of bloodshed

Thanks again!

[cwconley]

ok,
last clarification.

I download the new TinyMCE update.

Unzip it (on my desktop?) and then replace the old folder (after renaming it) by FTP??

thanks much
chris

[prodgers]

Hi Guys,

I'm having the save problem on IE6.

I've just started using Joomla a couple of weeks ago (most excellent software tool dudes) and I'm building my first site.

I've managed to get components installed and configured and everything was going fine until yesterday -
I tried editing some content items which I had created previously using TinyMCE and it has suddenly stopped working (
- as described by others above).

Not only does the content not show up in the TinyMCE editor, but I cannot use [Save] or [Cancel] to get out of it.
I end up having to log out - and the content item is then locked.

I followed your advice above and installed the latest version of TinyMCE tonight, but I still have the same problem.

I noticed that I was getting some cookies being blocked when I went into editor mode, so I changed my privacy settings to allow cookies temporarily - but this didn't change anything.

The only thing I can think of is, that I installed and then uninstalled a couple of components in the last few of days - that could have disrupted something perhaps?

In the meantime I'm just going to have to switch off WYSIWYG editing.

Unless someone has any other ideas...


Also in the meantime - how do I unlock the content items which got locked when my editor froze? (Joomla obviously still thinks these are being edited!

Thanks in advance to anyone who can help with this.

Paul Rodgers.

[prodgers]

Oops - sorry.
I should have looked a bit harder.
The answer was here ( http://forum.joomla.org/index.php/topic,9832.0.html ) all along!

[JasonB]

OK, I'm now beyond frustrated, and I'm not getting my work done. I'm having the same problem where when I click on the HTML button in TinyMCE, all I get is a blank window. I upgraded the version, and it worked fine for a day. However, today it isn't working. This happens in both FireFox and IE. To top this, I installed mosCE bot and com. I made sure I switched it in Global Config and published the bot. Yet when I go to edit content, TinyMCE is still the editor. I even tried to unpublish TinyMCE, and when I went to edit content, I didn't even have an editor. Even if I set No WYSIWYG Editor in globals, TinyMCE still shows up! It's like a virus! This seems like it might be a Joomla problem, since I didn't have this problem when I was still using Mambo. I checked my live site settings (without the www) and that is how I logged in. I also tried it with the www after editing the .php file and that didn't help either. So what do I do now? I've tried everything... at least everything that's been discussed in this forum.