Integration"

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.

(Minor rewording)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
__TOC__
 
{{CKFinder_2.x Integration Introduction|language=PHP|ext=php|classext=php}}
 
{{CKFinder_2.x Integration Introduction|language=PHP|ext=php|classext=php}}
  
 
=== Example ===
 
=== Example ===
To launch CKFinder, basically we need to do three things:
+
In order to launch CKFinder, you need to do three things:
* Create an instance of a CKFinder class.
+
* Create an instance of the <code>CKFinder</code> class.
 
* Assign CKFinder properties.
 
* Assign CKFinder properties.
* Call the '''Create''' method.
+
* Call the <code>Create()</code> method.
  
The example of creating CKFinder using a PHP class:
+
An example of creating CKFinder using a PHP class:
 
<source lang="php">
 
<source lang="php">
 
<?php
 
<?php
Line 18: Line 19:
 
</source>
 
</source>
  
For a full working examples please refer to the "'''_samples'''" directory. Note that in both cases it is required to include the integration file (ckfinder.js or ckfinder.php) to have access to the CKFinder class.
+
For a full working example please refer to the <code>_samples</code> directory of the installation package.
  
=== Integration methods ===
+
== Integration methods ==
 
+
* [[/JavaScript|JavaScript integration]] &ndash; the preferred integration method, simple yet powerful.
* [[/JavaScript|JavaScript integration]] - The preferred method of integration, simple, yet powerful.
+
* [[/JavaScript V1|JavaScript integration (V1)]] &ndash; the old "V1" way, useful when migrating from CKFinder 1.x because it makes it possible to reuse existing code.
* [[/JavaScript V1|JavaScript integration (V1)]] - The old "V1" way, useful when migrating from CKFinder 1.x because it is possible to reuse the old code.
+
* [[/PHP V1| PHP integration]] &ndash; if you have not worked with JavaScript before or the JavaScript integration seems to be too complicated, it might be the way to go for you.
* [[/PHP V1| PHP integration]] - If you haven't worked with JavaScript before or the JavaScript integration seems to be too complicated then it might be the way to go for you.
 

Latest revision as of 10:37, 21 November 2011

Introduction

Before reading this section, please read the installation and configuration instructions and make sure that the examples located in the _samples directory are working correctly.

The _samples directory contains HTML files with examples of launching CKFinder by using the JavaScript code as well as a php folder with examples of launching CKFinder by using the PHP language.

The following files are used when either the JavaScript or the PHP method of launching CKFinder is used:

  • ckfinder.js in case of the JavaScript integration method,
  • ckfinder_v1.js in case of JavaScript V1 integration method (useful when migrating from CKFinder 1.x),
  • ckfinder.php in case of the PHP integration method.

Example

In order to launch CKFinder, you need to do three things:

  • Create an instance of the CKFinder class.
  • Assign CKFinder properties.
  • Call the Create() method.

An example of creating CKFinder using a PHP class:

<?php
$finder = new CKFinder() ;
$finder->BasePath = '/ckfinder/' ;
$finder->SelectFunction = 'ShowFileInfo' ;
$finder->Width = 800 ;
$finder->Create() ;
?>

For a full working example please refer to the _samples directory of the installation package.

Integration methods

  • JavaScript integration – the preferred integration method, simple yet powerful.
  • JavaScript integration (V1) – the old "V1" way, useful when migrating from CKFinder 1.x because it makes it possible to reuse existing code.
  • PHP integration – if you have not worked with JavaScript before or the JavaScript integration seems to be too complicated, it might be the way to go for you.
This page was last edited on 21 November 2011, at 10:37.