How to upgrade DotNetNuke fckEeditor to version 2.6 :

First you will need to download a copy of the FCKEditor from the web site http://www.fckeditor.net/

After unzipping FCKeditor_2.6.zip file follow these steps:

1)      First of all make a copy of currently installed FckEditor for possible needs. You can find it in your DotNetNuke root folder \Providers\HtmlEditorProviders\Fck\FCKeditor

2)      Copy the “editor” folder (including all of its contents) from new version into \Providers\HtmlEditorProviders\Fck\FCKeditor\editor of your installed DotNetNuke.

3)      Copy fckconfig.js from new version into \Providers\HtmlEditorProviders\Fck\Custom of your installed DotNetNuke then right_click on it and choose “edit” from the list. In this notepad file opened, you must find FCKConfig.ToolbarSets["Default"] and change it to :

                                                                                                             FCKConfig.ToolbarSets["DNNDefault"]

4)      In \Providers\HtmlEditorProviders\Fck\Custom of your installed DotNetNuke also right_click on fckconfigsecure.js and choose “edit” from the list. In this notepad file opened, you must find FCKConfig.ToolbarSets["Default"] and change it to:

                                                                                                             FCKConfig.ToolbarSets["DNNDefault"]

5)      Copy the following files from new version into \Providers\HtmlEditorProviders\Fck\FCKeditor of your installed DotNetNuke.

The files are:   fckconfig.js , fckpackage.xml , fcktemplates.xml , fckstyles.xml

Now you can browse to your portal and enjoy the new version!

Further - I might be mistaken again but I think what you want to do is copy the DNNDefault & NoGallery toolbar config from the old fckconfig.js (which you hopefully have a backup of as it wasn't listed as a file necessary to backup!) otherwise you end up with the new (massive) default FCK toolbars.

Then I think you should copy fckconfig.js and rename it fckconfigsecure.js and then remove the 'Source' option from however many toolbars it appears in i.e. meaning that when used in some secure sense the HTML cannot be edited.

I could be wrong... but from comparing the files this would seem the right approach and it seems to work as expected.

Writing about this gives me the distinct feeling that I'm swearing left right and centre - a bit like wearing fcuk clothing I guess :)

Cheers,

I've done the upgrade from FCK 2.4.1 in DNN 4.8.2 to FCK 2.6 myself and was planning to write up the process but didn't because too many people have had various problems trying this. It can be done, and can work, but be careful. Here's a few miscellaneous comments in no particular order;

• If you're not confident that you can undo the process if it doesn't work then don't start!
• The only difference between the DNN shipped fckconfig.js and fckconfigsecure.js is the removal of the Source button from the toolbars in the secure version.
• The DNN shipped fckconfig.js is not a default 2.4.1 FCK fckconfig.js, and the 2.6 fckconfig.js has a number of changes to the 2.4.1 version. If things go wrong then it is quite possibly to do with these changes but I haven't got round to investigating them properly yet.
• I found Firefox to be very agressive in caching some of the JavaScript files - try clearing your browser cache if you have any problems.
• For what it's worth, my own upgrade doesn't function in Safari 3 on Windows but this isn't a problem for me. If I get a chance to look into it I'll post and update here.

To end on a positive note, the 2.6 FCKeditor has much better support for the <PRE> tag (very useful if you're editing example code snippets) and generally  feels more stable .

Regards, Rhys.