I just upgraded to Firefox 3.5 and FCKeditor has fallen apart. Didn't work previously on Chrome so this "problem" may have been around for awhile. We're on v2.6.4
firebug tells me
Permission denied for <http://mysite.org> to set property Window.FCK_STATUS_NOTLOADED on <http://www.mysubdomain.mysite.org>. [Break on this error] var FCK_STATUS_NOTLOADED=window.parent.FCK_STATUS_NOTLOADED=0;
What I notice:
- the site is never, ever referred to as http://mysite.org
- the subdomain that the editor is used on never has the www at the front: http://www.mysubdomain.mysite.org
What might be set up wrong?
Re: All was well until FF3.5
Re: All was well until FF3.5
Re: All was well until FF3.5
Broken with Chrome.
Broken with FF3.5
Ok with earlier versions of FF
I was wondering if it was linked to the fact I was running it on a subdomain ...
Not blaming FF so much as recognising that different versions "accommodate" different errors in js, css etc and this one obviously didn't like this error. Can't blame it, reading what js was trying to do.
Re: All was well until FF3.5
Re: All was well until FF3.5
Re: All was well until FF3.5
What do you mean?
I'm guessing that now suddenly it has started working correctly without any change?
is it right?
maybe there's some change at the hosting?
Re: All was well until FF3.5
No changes. Perhaps something refreshed in the cache but I did a Ctrl+F5 often enough to encourage that to happen sooner.
Re: All was well until FF3.5
In "normal" pages it might be enough, but as js files are loaded dynamically in FCKeditor you need to really clear the cache. For example in IE it means closing any windows/tab with the page, then clear the cache and only then you'll be sure to get the updated files.
Usually it's no necessary to be so drastic, but otherwise you might not get the new file.
In Firefox usually it's enough to clear the cache and then reload the page.
Re: All was well until FF3.5
Either way it's not an FCKEditor problem so that's good.
Re: All was well until FF3.5