Hi,
I have a serious issue. The time the editor takes to load on my page is very long.
When i run my application on my local system i dont actually feel the difference but when I deploy it on my client side and try to access it is where i face the problem. It takes a lot of time.
I was wondering if anyone knows hwo to reduce this. if this keeps up then i may have to look at some editor which will load faster.
Thanks in advance
I have a serious issue. The time the editor takes to load on my page is very long.
When i run my application on my local system i dont actually feel the difference but when I deploy it on my client side and try to access it is where i face the problem. It takes a lot of time.
I was wondering if anyone knows hwo to reduce this. if this keeps up then i may have to look at some editor which will load faster.
Thanks in advance
Re: How to improve FCK loading time
If the sFile variable is set as fckeditor-original.html that means you're downloading all the original source files with your implementation. If you change this to fckeditor.html you will be downloading FCK_HOME/editor/js/*.js instead which is your compressed js file.
The biggest problem with this is if you made any changes to the source files in FCK_HOME/editor/_source/*. If this is the case then you will need to download the FCKeditor.packager.exe which has an easy to follow readme to compress all of your changes into the correct directory.
Hope this helps
Re: How to improve FCK loading time
What is "very long"?
For example reloading the demo http://www.fckeditor.net/demo it takes about 3-4 seconds for me, if it takes longer for you then you have a bad internet connection or a misconfigured browser
Re: How to improve FCK loading time
I have the same problem to use FCKEditor .... I want to use it inside DotNetNuke ...... for example if I use the http://www.fckeditor.net/demo links then the FCK Editor works fine but not if I try to use it inside the DotNetNuke bundle ... then the Internet Explorer hangs completely and this I cannot have som for now I have been forced to use Freetextbox editor instead .... can you please have a dialog with the DotNetNuke team about this ...... the Freetextbox has a lot less javascript in it so I think thats wy it is loading a lot better ..... I wish i could use the FCKEditor but having the Explorer freeze up is a no no .....
/Johan
http://www.itansvar.se
Re: How to improve FCK loading time
-"Hey this guy says that he has a problem"
-"Yes, he said it also here"
-"but it works fine for us"
-"also for us"
-"so you don't have a clue?"
-"no"
-"bye"
-"bye"
as a minimum, I would ask you to please set up a demo that can be tested, if this was really a problem in DNN then lots of people would be complaining, not only you.
Re: How to improve FCK loading time
I've encountered similar problems to what Johan reported when using FCKEditor in an ASP.NET application, where IE will freeze/hang when loading the page containing FCKEditor. The whole browser process stops responding (can't use any menus, window doesn't repaint itself).
The problem only happens to some users. It only happens in IE (confirmed in IE6, not sure if IE7 is also affected). When a computer is affected by this problem, refreshing the page, rebooting, restarting the browser, etc. don't help.
When a user is affected by the problem, they can still use FCKEditor on other sites, e.g. fckeditor.net/demo.
The problem started happening more frequently when we changed some network infrastructure in our web hosting, which made me wonder if the hang was triggered by a race condition in the browser, and perhaps the network changes had changed the timing of scripts being downloaded to the browser. (I know that's a bit of a stretch... maybe the network changes were unrelated.)
There is a bug in Internet Explorer, "Internet Explorer stops responding for five minutes while it accesses dynamic content in frames": http://support.microsoft.com/kb/279745, which seems to fit the problem. That KB article links to a Windows registry change which can work around the problem. I've tried this and had some success, but I'm not sure if this registry change was what actually fixed the problem.
Has anyone seen anything similar? Any ideas how to reliably reproduce this issue or work around it?
Thanks for your time,
DJ