Troubleshooting CKFinder

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.

(Article restructured)
Line 1: Line 1:
{{#CUSTOMTITLE:Debugging CKFinder}}
+
{{#CUSTOMTITLE:Troubleshooting CKFinder}}
 +
This article describes some measures that can be taken in case of problems with the CKFinder for Java application.
 +
 
 +
== Debugging CKFinder ==
 
CKFinder for Java contains a special debugging mode that makes it easier to troubleshoot the application. This mode can be turned on in the <code>WEB-INF/web.xml</code> file, by setting a new <code><init-param>debug</init-param></code> node to <code>true</code>.
 
CKFinder for Java contains a special debugging mode that makes it easier to troubleshoot the application. This mode can be turned on in the <code>WEB-INF/web.xml</code> file, by setting a new <code><init-param>debug</init-param></code> node to <code>true</code>.
  
Line 23: Line 26:
  
 
<note>The debugging mode should not be turned on by default on a production server and should only be used to diagnose a problem when CKFinder does not work as expected.</note>
 
<note>The debugging mode should not be turned on by default on a production server and should only be used to diagnose a problem when CKFinder does not work as expected.</note>
 +
 +
 +
== Empty Message Errors ==

Revision as of 08:39, 2 August 2011

This article describes some measures that can be taken in case of problems with the CKFinder for Java application.

Debugging CKFinder

CKFinder for Java contains a special debugging mode that makes it easier to troubleshoot the application. This mode can be turned on in the WEB-INF/web.xml file, by setting a new <init-param>debug</init-param> node to true.

<servlet>
	<servlet-name>ConnectorServlet</servlet-name>
	<servlet-class>com.ckfinder.connector.ConnectorServlet</servlet-class>
	<init-param>
		<param-name>XMLConfig</param-name>
		<param-value>/WEB-INF/config.xml</param-value>
	</init-param>
	<init-param>
		<param-name>debug</param-name>
		<param-value>true</param-value>
	</init-param>
	<load-on-startup>1</load-on-startup>
</servlet>

For more information on the web.xml file refer to the Integration article.

With the debugging mode on, CKFinder returns detailed exception information when an error occurs.

important note
The debugging mode should not be turned on by default on a production server and should only be used to diagnose a problem when CKFinder does not work as expected.


Empty Message Errors