I have an application which works fine on our testing server and accessed from within the office, however when posted to a production server and accessed via the internet the component fails to initialise in Firefox (works fine in IE), unfortunately our client has a preference for Firefox, and will be unlikely to buy an editor which makes him use IE.

 

Content does not appear in the editor, none of the mouseover effects work on the buttons (nor do the buttons), the stylesheet classnames appear in the css styles dropdown but without the styles applied. The links dropdown does not appear.

 

The editor tag in the aspx page reads:

 

<CE:Editor id="content" runat="server" ></CE:Editor>

The code to populate the editor reads:

 

if(_pageStandardLayout){
   content.EditorWysiwygModeCss="../bbh.css,../editorstandard.css";
}else{
   content.EditorWysiwygModeCss="../bbh.css,../editorblank.css";
}

content.Width = 770;
content.Height = 600;

content.ConfigurationPath="~/CuteSoft_Client/CuteEditor/Configuration/bbh.config";
content.EditCompleteDocument = false;
content.EnableStripScriptTags = false;

CuteEditor.ToolControl toolctrl = content.ToolControls["LinkTree"]; 

if(toolctrl != null){
   tdd = (CuteEditor.TreeDropDownList)toolctrl.Control;

   tdd.Items.Clear();
   getLinks(null, 0);  //populates the tree drop down from an xml document
}
content.Text = _pageContent;  //string _pageContent comes from sql database