Error Messages"

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(Undo revision 3022 by Wiktor (Talk))
 
Line 1: Line 1:
 
{{CKFinder_2.x_SSI_Warning}}
 
{{CKFinder_2.x_SSI_Warning}}
 +
== Error Messages ==
  
 
The value of the "number" attribute of the <error> tag is always checked when receiving response. The data is processed only if the "ErrorNumber" value is equals to "0" (zero). Any other value will popup an error message box to the user.
 
The value of the "number" attribute of the <error> tag is always checked when receiving response. The data is processed only if the "ErrorNumber" value is equals to "0" (zero). Any other value will popup an error message box to the user.

Latest revision as of 20:59, 14 May 2010

Note: This information is intented for programmers interested in modifying the CKFinder core.
If you are interested in installing/configuring CFKinder, please take a look at the Developer's Guide.

Error Messages

The value of the "number" attribute of the <error> tag is always checked when receiving response. The data is processed only if the "ErrorNumber" value is equals to "0" (zero). Any other value will popup an error message box to the user.

Each command may implement its set of default errors based on the number. For example the "CreateFolder" command sends a "115" error if the folder already exists.

The special error number "1" (one) is reserved for "custom error messages". When processing this error, the File Browser will look for the value of the "text" attribute of the <error> tag and show and alert box with that text.

For security reasons, all connectors to not be active by default, requiring its manual activation by the end developer. In this way we can prevent the use of the connector by others (hackers) on cases were developers haven’t properly configured it. In those cases, the error “500” must be returned to the user for any command request. Something like this:

<?xml version="1.0" encoding="utf-8"?>
<Connector>
 <Error number="500" />
</Connector>
This page was last edited on 14 May 2010, at 20:59.