Re: Problem with CState is undefined

  •  03-23-2006, 6:18 AM

    Re: Problem with CState is undefined

    No that is not the problem, the js and the js.asp files are being loaded based on the browser is being used. No you will not find where they are doing it, but they are.
     
    #1 cause in _cstate is an incorrect path
     
    < !-- #include file = "CuteEditor_Files/include_CuteEditor.asp" -- >
    editor.FilesPath = "CuteEditor_Files"
     
    I store CE off the root in a directory called editor, notice the relative .. in the include
     
    < !-- #include file = "../editor/CuteEditor_Files/include_CuteEditor.asp" -- >
     
    I am including the script I use, I have these in an include file that I load where I need them. I have removed a few items that do not pertain to the illustration.  This example used the now deleted "enableall" configuration, so change it to what you need.
     
    Set editor = New CuteEditor
    editor.ID = "Editor1"
    editor.Text = content
       
    editor.DisableAutoFormatting = true
    editor.EditorOnPaste = "ConfirmWord"  
    editor.RemoveServerNamesFromUrl=true   
    editor.FilesPath = "/editor/CuteEditor_Files"
       
    editor.AllowUpload=true
    editor.AllowPasteHtml = true

    editor.ImageGalleryPath = "/user_upload/images/"
    editor.FilesGalleryPath = "/user_upload/documents/"
    editor.FlashGalleryPath = "/user_upload/images/"
    editor.MediaGalleryPath = "/user_upload/images/"
    editor.MaxImageSize = 100
    editor.AutoConfigure = "EnableAll"
    editor.BreakElement= "p"

    editor.ThemeType="office2003"  
    editor.Width = "100%"
    editor.DisableAutoFormatting =true
    editor.EditorBodyStyle = "font:normal 12px arial;"
    editor.EditorWysiwygModeCss = "/editor/CuteEditor_Files/gfeditorcss.css"  
    editor.Draw()
     
    #2 cause is the incorrect XMLDOM
     
    Download the following file http://www.az-technology.com/xmldom.zip, unzip it and run it in your web site. You can see what it should look like by running it on my site at http://www.az-technology.com/xmldom.asp. This will tell you what version of XMLDOM you have, idealy you should have 4.0, but that may or not be the case. You should get something like this.
     
    MSXML2.DOMDocument.5.0 can NOT be used. Reason: 006~ASP 0177~Server.CreateObject Failed~800401f3)
    MSXML2.DOMDocument.4.0 can be used.
    MSXML2.DOMDocument.3.0 can be used.
    MSXML2.DOMDocument.2.6 can be used.
    MSXML2.DOMDocument can be used.
    Microsoft.XMLDOM can be used.
     
    In this case, MSXML2.DOMDocument.4.0 can be used, if not then you will have to change the MSXML2.DOMDocument.4.0 reference in include_cuteeditor.asp, getstring.asp and tag.asp to the version you need. If MSXML2.DOMDocument.4.0 can not be used , then try first MSXML2.DOMDocument.
     
     
    RC
View Complete Thread