Problem integrating FCKeditor with .net

Hi danny, I'm not sure if I know the definitive answer, but here's a couple of suggestions which may help you.

Does the editor recognise the '~' in the basepath? I'm not sure, so I always use a full pathname when I create an FCKEditor in .NET - try with BasePath="/fckeditor/" and see if that works.

Also, I think that the basepath is case sensitive, I have a local source with "/fckeditor/" but on my server it's "/FCKEditor/" and I found that if I copied the source over to the server, it didn't work properly until I changed the case of the basepath.

joz65 wrote:Does the editor recognise the '~' in the basepath? I'm not sure, so I always use a full pathname when I create an FCKEditor in .NET - try with BasePath="/fckeditor/" and see if that works.

The "~/FCKeditor" notation is fine.

Some FTP clients will mess up case-sensitivity so that's definitely something to check.

Also check where you have installed FCKeditor. Did you create your ~/fckeditor and then unzip the package inside that, so it's actually in ~/fckeditor/FCKeditor ? Check that both these files exist: ~/fckeditor/fckconfig.js and ~/fckeditor/editor/fckeditor.html.

The problem is the "editor" folder containing the fckEditor.html file is not included in the download zip file.

Where do we get it from.

simonsabin wrote:The problem is the "editor" folder containing the fckEditor.html file is not included in the download zip file.

Where do we get it from.

I would look at the download page, who knows what might be available there?

Ok RTFM fair point. However I didn't expect to have to download some a beta file with the source to run the non beta code.

Further more on using that download I now get a host of javascript errors.

Error: FCKConfig.CustomConfigurationsPath is undefined
Source File: http://localhost:40674/Admin/editor/fck ... ar=Default
Line: 157
Error: A.PluginsPath is undefined
Source File: http://localhost:40674/Admin/editor/js/ ... e_gecko.js
Line: 33
Error: FCKConfig.ContextMenu is undefined
Source File: http://localhost:40674/Admin/editor/js/ ... e_gecko.js
Line: 105
Error: C is undefined
Source File: http://localhost:40674/Admin/editor/js/ ... e_gecko.js
Line: 99

Which I can only guess is due to me trying to use the Beta scripts with the non beta control.

Ok RTFM fair point. However I didn't expect to have to download some a beta file with the source to run the non beta code.

Actually the FCK beta's are usually pretty stable and FCKeditor.Net control isn't updated that often so unless the way FCKEditor is integrated into a page is drastically changed the .NET control will work. And given that nobody else is posting problems I'd maybe, possibly, assume its something you are doing? 2.9 milion downloaders can't be wrong...

For .NET development you'll need the main FCKEditor package and the FCKEditor.NET assembly, which are seperate downloads. But you knew that, right?

Like others have posted as far as I can tell, your application paths aren't correct, and using Cassini might also be causing you problems, but one step at a time...

you are using this:
<FCKeditorV2:FCKeditor ID="FCKeditor1" runat="server" BasePath="~/fckeditor/">

so that would mean your editor would be at http://localhost/admin/fckeditor (providing you have your virtual directory setup properly in IIS or http://localhost/fckeditor/ if you were running it from the root.

now, in your error message, there's a bit of a give away. Your first error Error: FCKConfig.CustomConfigurationsPath is undefined has the URL:
localhost:40674/Admin/editor/fckeditor.html?InstanceName=FCKeditor1&Toolbar=Default

what happened to the /FCKEditor/ folder?? Have you extracted the contents of the FCKEditor folder to the root of your site? Just for general housekeeping, it would be better keeping it in its own folder, but if thats the way you've done it, then your BasePath should be
<FCKeditorV2:FCKeditor ID="FCKeditor1" runat="server" BasePath="~/">

i'd also try removing the tilde (~) and putting the full directory path in eg "/admin/fckeditor/". Cassini (the internal .net dev server) might be screwing up your directory paths. I usually use IIS on localhost than Cassini, so I'm not 100% on this. Also, just verify the files are where they should be, turn on directory browsing and understand your folder structure.

I'd imagine the .NET control is in a seperate download from the main FCKEditor download because not everybody would use it (do you want to download the java integration files?) and to keep things simple so not to confuse people.

Hope this helps.

I'm having the exact same problem as the original poster on this page.

http://www.elon.edu/cms4/fckeditor/edit ... ar=Default

Here's what my asp line looks like:

<FCKeditorV2:FCKeditor ID="FCKeditor1" runat="server" BasePath="/cms4/fckeditor/" CustomConfigurationsPath="/cms4/fckeditor/" PluginsPath="/cms4/fckeditor/" />

I get tons of javascript errors when trying to load that page. Adding CustomConfigurationsPath, and PluginsPath fixed some of the javascript errors I was having.

Any help appreciated.

I had the same problem. I had unzipped all the code under my websites root directory.

I was loading the editor into a placeholder. Here is the code that worked for me:

FredCK.FCKeditorV2.FCKeditor f1 = new FredCK.FCKeditorV2.FCKeditor();

f1.BasePath = this.Request.ApplicationPath + "/fckeditor/";

pnl1.Controls.Add(f1);

alfonsoml wrote:

simonsabin wrote:The problem is the "editor" folder containing the fckEditor.html file is not included in the download zip file.

Where do we get it from.

I would look at the download page, who knows what might be available there?

I've been to the download page and any other page I can find up here but NOTHING says it contains the "scripts" needed to integrate with ASP.NET.

Would someone be so kind as to provide the exact link or page where these script files are located?

Many thanks.

For anyone interested, this is the download for the scripts:

http://sourceforge.net/projects/fckedit ... FCKeditor/

Not that one would ever know that without downloading a bunch of stuff and unzipping and experimenting over and over.


Would it be so hard to put a link on the main download page to the scripts that the page says are necessary?

Do you mean something like this?