I am getting the FTB problem  with DNN I've seen mentioned in a number of posts.

The error below is occuring, and I've seen advice saying it's to do with CSS handling and the new version of FTB. As advised I've tried to remove all white space and extra  carriage returns from default.css, portal.css, DNNBlue skin.css but no joy (the CSS comments are still in though).

1) Does anyone know an answer to the problem

2) Have I got the right CSS files (I'm using a standard DNN install from my Host Provider, Crystaltech)

many thanks, this is getting a bit urgent now !

Andy

Error text -
FreeTextBox has not been correctly installed. To install FreeTextBox either:
(1) add a reference to FtbWebResource.axd in web.config:
<system.web>
<httpHandlers>
<add verb="GET"
path="FtbWebResource.axd"
type="FreeTextBoxControls.AssemblyResourceHandler, FreeTextBox" />
</httpHandlers>
</system.web>

(2) Save the FreeTextBox image and javascript files to a location on your website and set up FreeTextBox as follows
<FTB:FreeTextBox id="FreeTextBox1" SupportFolder="ftbfileslocation" JavaScriptLocation="ExternalFile" ButtonImagesLocation="ExternalFile" ToolbarImagesLocation="ExternalFile" ButtonImagesLocation="ExternalFile" runat="server" />

I am guessing you only copied the new FTB DLL.
It has embedded resources but DNN is not using that method to read them presently.  Instead we are using the extracted resources from the DLL (they also come in the FTB download)  you will need to copy the .js, language and image files from the new version to their respective directories under \Providers\HtmlEditorProviders\Ftb3HtmlEditorProvider\.

then you will need to recompile the HTMLEditor provider project.

see if that helps.

I am experiencing the same issue.  However, I've not copied any new Ftb files, rather I have simply created a parent portal with custom portal folder.

Parent portal with custom folder creates such folder in the DNN installation root folder.  Ftb is working with all previously created sites, but DOES NOT work with this new parent portal.  The symptom is as stated above.

This seems to be an issue with paths and configurations of IIS and the FTB provider.  But I am unsure of how to fix it.

Thanks.