CKFinder 2.x/Developers Guide/ASP.NET/Troubleshooting - Revision history

Wiktor at 16:08, 5 December 2015

2015-12-05T16:08:05Z

Wiktor at 16:07, 5 December 2015

2015-12-05T16:07:08Z

Anna: /* Flash Upload Problem */ Some text proofiing

2011-11-28T09:32:46Z

‎Flash Upload Problem: Some text proofiing

Wiktor: Added Flash Upload Problem section

2011-09-13T18:52:13Z

Added Flash Upload Problem section

Wiktor: Created page with '== Debugging == When installing and configuring CKFinder, sometimes it may happen that for unknown reason CKFinder doesn't work as expected, for example it returns an error abou…'

2010-05-14T19:11:51Z

Created page with '== Debugging == When installing and configuring CKFinder, sometimes it may happen that for unknown reason CKFinder doesn't work as expected, for example it returns an error abou…'

New page

== Debugging ==

When installing and configuring CKFinder, sometimes it may happen that for unknown reason CKFinder doesn't work as expected, for example it returns an error about insufficient permissions ("It was not possible to complete the request due to file system permission restrictions."). In such case it might be more usable to run the debug version of server connector to find out what's the problem.

==== web.config ====

To use CKFinder for ASP.NET in debug mode, add <code><compilation debug="false"/></code> to the web.config.

<system.web>
<compilation debug="true" />
</system.web>

==== CKFinder.dll ====

Apart from setting compilation element, the debug version of CKFinder binaries: CKFinder.dll and CKFinder.pdb should be copied to the "bin" directory of ASP.NET application. Both files are available in the ckfinder/bin/Debug directory.

When debugging problems with file uploads, using a tool to trace HTTP connections, like [http://www.fiddlertool.com/fiddler/ Fiddler], might be helpful.

'''Warning:''' it is not recommended to run production ASP.NET applications with debug mode enabled.

== Disabling FCN ==

When File Change Notifications (FCN) are turned on, session state may be lost after deleting a subfolder. See this [http://blogs.msdn.com/toddca/archive/2005/12/01/499144.aspx blog post on msdn] to find out more about this issue.
This might be a problem when using CKFinder, i.e. user might be automatically logged out after deleting a folder.

A resolution for this problem (apart from suggestions in the blog post mentioned above) is using a special HTTP module
that disables FCN provided with CKFinder, named StopAppDomainRestartModule. To enable this module, add the following to web.config inside the <system.web> element:

<httpModules>
<add name="StopAppRestartOnFolderDelete" type="CKFinder.Utils.StopAppDomainRestartModule" />
</httpModules>

'''Note:''' this solution will not work in medium trust environment.

← Older revision		Revision as of 16:08, 5 December 2015
Line 21:		Line 21:

	==Flash Upload Problem==		==Flash Upload Problem==
−
−	~~'''Note: the flash upload component has been completely removed in CKFinder 2.6.'''~~

	{{Template:Flash Upload Problem}}		{{Template:Flash Upload Problem}}

← Older revision		Revision as of 16:07, 5 December 2015
Line 21:		Line 21:

	==Flash Upload Problem==		==Flash Upload Problem==
		+
		+	'''Note: the flash upload component has been completely removed in CKFinder 2.6.'''

	{{Template:Flash Upload Problem}}		{{Template:Flash Upload Problem}}

@@ Line 24: / Line 24: @@
 {{Template:Flash Upload Problem}}
-To workaround this problem we have created a dedicated HTTP module named <code>FixFlashCookies</code> which  retrieves appropriate cookies on server side. So if you are using flash upload component together with session scope variables to identify your user, make sure this module is enabled in <code>web.config</code>.
+To work around this problem we have created a dedicated HTTP module named <code>FixFlashCookies</code> which retrieves appropriate cookies on the server side. If you are using the Flash upload component together with session scope variables to identify your user, make sure this module is enabled in your <code>web.config</code>.
 <source lang="xml">
@@ Line 32: / Line 32: @@
 </source>
-Alternatively, enabling cookieless in the <code>web.config</code> should solve this issue in most cases as well:
+Alternatively, in most cases enabling <code>cookieless</code> in the <code>web.config</code> file should solve this issue as well:
 <source lang="xml">
 <system.web>

← Older revision		Revision as of 18:52, 13 September 2011
Line 19:		Line 19:

	'''Warning:''' it is not recommended to run production ASP.NET applications with debug mode enabled.		'''Warning:''' it is not recommended to run production ASP.NET applications with debug mode enabled.
		+
		+	==Flash Upload Problem==
		+
		+	{{Template:Flash Upload Problem}}
		+
		+	To workaround this problem we have created a dedicated HTTP module named <code>FixFlashCookies</code> which retrieves appropriate cookies on server side. So if you are using flash upload component together with session scope variables to identify your user, make sure this module is enabled in <code>web.config</code>.
		+
		+	<source lang="xml">
		+	<httpModules>
		+	<add name="FixFlashCookies" type="CKFinder.Utils.FixFlashCookiesModule" />
		+	</httpModules>
		+	</source>
		+
		+	Alternatively, enabling cookieless in the <code>web.config</code> should solve this issue in most cases as well:
		+	<source lang="xml">
		+	<system.web>
		+	<sessionState cookieless="true" />
		+	</system.web>
		+	</source>

	== Disabling FCN ==		== Disabling FCN ==