Line 37: | Line 37: | ||
==== Method 2 ==== | ==== Method 2 ==== | ||
− | Alternatively, you may simply include '''ckfinder_v1.js''' <u>instead of</u> '''ckfinder.js''' in your application to not worry about the API | + | Alternatively, you may simply include '''ckfinder_v1.js''' <u>instead of</u> '''ckfinder.js''' in your application to not worry about changes in the API . ckfinder_v1.js contains a comptibility pack that makes ugrading from 1.x even easier. |
This method of upgrading is not the same as the first method. When using ckfinder_v1.js, an extra file named ckfinder.html is used to create CKFinder instance, for better performance the first method should be used instead. | This method of upgrading is not the same as the first method. When using ckfinder_v1.js, an extra file named ckfinder.html is used to create CKFinder instance, for better performance the first method should be used instead. |
Revision as of 14:02, 31 May 2010
Upgrading CKFinder is very easy, to do it, simply follow these steps:
Upgrading instructions
- Download the new version of CKFinder from CKFinder website.
- Backup your old copy of CKFinder in a safe place.
- Temporarily disable access to CKFinder for all users in your application.
- Delete all files from CKFinder folder (remember to not delete the "userfiles" folder if you have configured CKFinder to store files there).
- Unpack new CKFinder in the folder where old CKFinder was installed.
- Apply changes from the old configuration file to the new configuration file shipped with CKFinder (most of the time, you can simply use the old configuration file).
- (Optional) In you application, add a timestamp to a path to ckfinder.js to help browsers recognize that the new version of file is available, e.g.:
<script type="text/javascript" src="/ckfinder/ckfinder.js?t=20100601"></script>
- Make some simple tests to ensure that CKFinder is running fine.
- Enable access to CKFinder for all users in your application.
Upgrading from CKFinder 1.x
Method 1
In CKFinder 2.x we have made a small changes to the API to conform to CKEditor coding standards. The JavaScript methods now begin with a lower case letter. The following code used in CKFinder 1.x:
var finder = new CKFinder(); finder.BasePath = '/ckfinder/'; finder.SelectFunction = ShowFileInfo; finder.Create();
should be changed in CKFinder 2.x into:
var finder = new CKFinder(); finder.basePath = '/ckfinder/'; finder.selectFunction = ShowFileInfo; finder.create();
Method 2
Alternatively, you may simply include ckfinder_v1.js instead of ckfinder.js in your application to not worry about changes in the API . ckfinder_v1.js contains a comptibility pack that makes ugrading from 1.x even easier.
This method of upgrading is not the same as the first method. When using ckfinder_v1.js, an extra file named ckfinder.html is used to create CKFinder instance, for better performance the first method should be used instead.