I submitted this through your support system but got no response... aarrrrgh!

I am trying to get the CuteEditor working in our Staging environment; however, I am having an issue with the file path and url.

My development instance works perfectly and lives on our local intranet here:

(c:\inetpub\wwwroot\myapplicationname)

However, my Staging and Production environments live behind an Apache-based "translation" layer called "portalservices".  Therefore, their URLs and paths look like this...

 

Staging:

 (c:\inetpub\wwwroot\acpchapterportal)

 

Production:

(c:\inetpub\wwwroot\myapplicationname) 

Initially (in staging), I entered "<add key="CuteEditorDefaultFilesPath" value="~/cutesoft_client/cuteeditor" />" into the web.config and received an error stating that it could not find the following URL...

 

...which is correct - that URL does not exist.  The URL it *should* detect is...

Then, I was able to "fake out" the control by entering the following line into the Staging web.config...

 

...and placing a copy of the "cutesoft_client/cuteeditor" files here...

However, not only is this not preferred, but now the control draws itself with everything disabled. (wtf)  Again, the same control, code, & configuration works flawlessly in the localhost and development environments.

The ability to enter a path without the ~/ I would expect would solve my problem.  I'm guessing that the "CuteEditorDefaultFilesPath" is being used by the control in more than one manner, thus the limitation.  Therefore, I suggest splitting apart the various uses of it into separate web.config attributes.

We have already paid for this control and now I am VERY frustrated.  Please help!

-Tim