This article details common error messages displayed while initializing EditLive!. For each type of error message, this article details how to locate the source of the error and how to solve the problem.
Accessing the Java Console
It will often be necessary to open the java console in order to understand exactly what is triggering an error in EditLive!. To open the java console, perform the following operations:
Windows Platforms
In the system tray there should be a java icon. Right click on this icon and select 'Open Console'.
Mac OS X
On the Macintosh, Java output is sent to the System console. This can be viewed using the Console application in the Application -> Utilities folder.
XML Configuration File Error Messages
These error messages will be shown by the following display in EditLive!:
An error occured while parsing the XML configuration file
These error messages reflect a problem with one or more sections of the configuration file used to initialize EditLive!. When prompted with this error message, opening the Java console will reveal more information about the specific location and cause of the problem.
Common errors include:
File Not Found Exception
This error will be shown by the following string in the Java console:
java.io.FileNotFoundException
This error refers to one of two conditions that could occur:
- The path specified in an EditLive! configuration file (using the setConfigurationFile Method) is incorrect. For more information on specifying the path of an EditLive! for Java configuration file, see the Configuration File load-time property documentation.
- The name of a specific EditLive! configuration file (using the setConfigurationFile Method) is incorrect. For more information on specifying the name of an EditLive! for Java configuration file, see the Configuration File load-time property documentation.
Illegal Argument Exception
This error will be shown by the following string in the Java console:
java.lang.IllegalArguement
This error reveals that there is a syntax error in the EditLive! configuration file. This is usually due to a syntax error entered by a developer manually editing the configuration file.
Character Encoding Error Message
This error message will be shown by the following display in EditLive!:
The required encoding for this document, XXXencodingMethodXXX, is unavailable on this system.
where XXXencodingMethodXXX represents the encoding method specified.
This error message reflects a problem with the character encoding method used for the content in EditLive!. Fixing this error will require locating where the character encoding was specified and specifying an acceptable character encoding method. The Specifying Character Sets in the Applet article details the three methods used to specify character encoding for EditLive! and its supported character sets.
Licensing Error Messages
These messages will be displayed in a separate pop-up window from the EditLive! editor. Licensing information is specified in an EditLive! configuration file. For information on how to specify an EditLive! licence, see the <license> Configuration File Element article and the Licensing EditLive! article.
Common errors include:
Account Not Found Error
This error will be shown by the following message in a pop-up window:
Licence error 203: Account not found
This error refers to an incorrect value being place in the key attribute of a <license> configuration file element. Make sure the product key provided by Tiny is correctly entered into this attribute.
License Domain Error
This error will be shown by the following message in a pop-up window:
Attempting to use an unlicensed domain
This error refers to an incorrect value being placed in the domain attribute of a <license> configuration file element. Make sure the organization's domain registered with Tiny is correctly entered into this attribute (commonly, the domain displayed by browsers in an organization is the domain name registered with Tiny).
Applet Not Appearing Errors
You may experience a problem where EditLive! does not load; instead, a box appears on your page featuring a small red 'X'. In order to identify the cause for this error, open the java console.
Class Not Found Exception
This error will be shown by the following string in the Java console:
java.lang.ClassNotFoundException: com.ephox.editlive.win.EditLiveJava
This indicates that the required EditLive! files were not able to be located to load the applet. This would be due to an incorrect value passed to the setDownloadDirectory Method.
QuickStart Applet Not Downloading the EditLive! .jar File
If you are using the ephoxQuickStart() function in Internet Explorer to preload the EditLive! .jar file, ensure the function is called within the document BODY.