A long standing problem with Fckeditor

If it's working for you then Lady Luck smiles on you. For me however, it does not work.

I tried this:

<?php
$oFCKeditor->BasePath = '/fckeditor/' ;
$oFCKeditor = new FCKeditor('content') ;
$oFCKeditor->Config["CustomConfigurationsPath"] = "/myconfig.js/" ;
$oFCKeditor->ToolbarSet = 'NewToolBar' ;
$oFCKeditor->Height = '400' ;
$oFCKeditor->Value = $content ;
$oFCKeditor->Create() ;
?>

I have put the "NewToolBar" toolbar on the custom config file and I also have it on the fckeditor.js file and neither works. I've cleared the browser cache time and time again, but the same is true now as it has always been in the past - fckeditor will not work once you have made even the slightest change to the fckeditor.js file - with or without a custom config file.

I'm just giving anyone who wants to use fckeditor a heads up. If you make any change whatsoever to the fckeditor.js file fckeditor there is a very good chance that fckeditor will not work anymore. The Documentation says that you can change the Toolbars in the fckeditor.js file or add new ones, but if you do - know that it will likely stop working, even if you empty your browser's cache.

You will get the javascript error message: "undefined" is null or not an object

If by some stroke of luck you are able get fckeditor working again after making a change to the fckeditor.js file by clearing your browser's cache file, you will need to post a message with instructions for all of your website users to do the same or fckeditor will not work on their computer.

If there is someway to force mine and every other Web surfer's browser to search for a newer copy of fckeditor.js file then it should be hard coded into the program instead of it being a hack that you add on later (In PHP this: + ( new Date() * 1 ) ; will return an error). My having to post a public message directing all my users to clear the browser cache in order to get fckeditor to work on my website on their computer is a bit extreme and would cause me to lose visitors. Also, Ctrl + F5 doesn't work either.

an invisible proxy or incorrect server caching settings

But this could be true for anyone who visits my website.

If I make a change to the fckeditor.js file and I do the research to discover and fix what's wrong with my computer/browser or whatever it is that's preventing fckeditor from appearing in my website, then everyone who visits my website would have to do the same. And I just don't think that would happen.

As far as I know my Web server does not have an invisible proxy. If it is on my computer and I'm running XP Home S2 standard install with IE 6.0, then everyone else running this same setup on their computer will have the same cache setting as I, and will have the problem I'm having on every website that is using fckeditor if the site owner makes a change to the fckconfig.js file. And that's a lot of people. But the website owner may never realize that it's a problem because most likely no one will tell him. That is - if he finds that the problem is on HIS computer and he fixes it. Then it'll look fine to him if he test his site. But everyone else will see that his website is non-functioning and will just click away.

I'm simply pointing out that there is a problem with fckeditor. It works fine until you change the fckconfig.js file - then it stops working.

If it is due to the cache size on my computer not being set right then half the people on the planet that owns a PC has the same problem, because the cache size is preset and no one outside of geeks ever change it. If fckeditor breaks down because of an invisible proxy then the folks who created fckeditor should take the time and address this issue; telling people what it is, what causes it and how to fix it. Or better yet, add code to the program to handle invisible proxies (if possible).

I have followed the instructions in the documentation concerning what to do when you make a change to the fckeditor.js file, but it does not work. I have cleared my browser cache from the browser Tools -> Internet Options, and from the Control Panel, and using Ctrl + F5 - to no avail. Fckeditor is setup correctly because it worked fine before adding a new toolbar to the fckeditor.js file. In fact, I am running the exact same setup on another website but there I had the sense to alter the fckconfig.js file before uploading it to my server, and it works fine because I haven't made any changes to the fckconfig.js file.

But acoote, I appreciate your help on the matter.


alfonsoml - Yes, I am talking about the fckconfig.js file - a mistype on my part. Also, I tried the myconfig.js in various ways including the way you have it, but it was a no go.

The short-term fix as I see it is to remove fckeditor from my website for a week or so and then reinstall it with the modified fckconfig.js file and see if it'll work then. In the meantime, I'll use a regular textarea on my Web pages - I guess I can live without Bold, Underline and Italicize.