CKFinder 2.x/Developers Guide/Upgrading - Revision history

Anna: /* Upgrade Instructions */ Article section proof-read.

2012-01-05T13:29:38Z

‎Upgrade Instructions: Article section proof-read.

Anna: Article introduction proof-read and expanded

2012-01-05T13:25:52Z

Article introduction proof-read and expanded

Wiktor at 14:36, 31 May 2010

2010-05-31T14:36:50Z

Wiktor: /* Method 3 */

2010-05-31T13:56:57Z

‎Method 3

Wiktor: /* Method 3 */

2010-05-31T13:56:32Z

‎Method 3

Wiktor at 13:56, 31 May 2010

2010-05-31T13:56:06Z

Wiktor: /* Method 3 */

2010-05-31T13:55:42Z

‎Method 3

Wiktor at 13:54, 31 May 2010

2010-05-31T13:54:08Z

Wiktor at 13:53, 31 May 2010

2010-05-31T13:53:41Z

Wiktor at 13:11, 31 May 2010

2010-05-31T13:11:30Z

@@ Line 8: / Line 8: @@
 == Upgrade Instructions ==
 If you want to upgrade your CKFinder installation, proceed as described below.
-# Download the new version of CKFinder from the [http://ckfinder.com/download CKFinder website].
+# Download the latest CKFinder version from the [http://ckfinder.com/download official CKFinder website].
-# Backup your old copy of CKFinder in a safe place.
+# Backup your old copy of CKFinder to a safe place.
-# Temporarily disable access to CKFinder for all users in your application.
+# Temporarily disable access to CKFinder for all users of your application.
-# Delete all files from CKFinder folder (remember to '''not delete the "userfiles"''' folder if you have configured CKFinder to store files there).
+# Delete all files from the CKFinder folder (remember to '''not delete the <code>userfiles</code>''' folder if you configured CKFinder to store files there).
-# Unpack new CKFinder in the folder where old CKFinder was installed.
+# Unpack the new CKFinder version to the folder where old CKFinder was previously 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 a file is available, e.g.: <br><br><source>
+# (Optional) In you application add a timestamp to the path to <code>ckfinder.js</code> to help browsers recognize that the new version of the file is available, e.g.: <br><br><source lang="javascript">
 <script type="text/javascript" src="/ckfinder/ckfinder.js?t=20100601"></script>
 </source>
-# Make some simple tests to ensure that CKFinder is running fine.
+# Perform some simple tests to ensure that CKFinder is running fine.
-# Enable access to CKFinder for all users in your application.
+# Enable access to CKFinder for all users of your application.
 == Upgrading from CKFinder 1.x ==

@@ Line 1: / Line 1: @@
-Upgrading CKFinder is very easy, below you'll find a complete instruction how to do it.
+Latest CKFinder is always the greatest CKFinder. Each new release brings plenty of bug fixes and new features, so it is highly recommended to upgrade often.
-== Upgrading instructions ==
+<note>Please note that each CKFinder license grants you one year of free upgrades. If you want to take advantage of new CKFinder releases after that time, you can [http://ckfinder.com/purchase renew your license] at any time for a discounted price.</note>
 # Download the new version of CKFinder from the [http://ckfinder.com/download CKFinder website].
 # Backup your old copy of CKFinder in a safe place.

@@ Line 9: / Line 9: @@
 # 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.: <br><br><source>
+# (Optional) In you application, add a timestamp to a path to '''ckfinder.js''' to help browsers recognize that the new version of a file is available, e.g.: <br><br><source>
 <script type="text/javascript" src="/ckfinder/ckfinder.js?t=20100601"></script>
 </source>

← Older revision		Revision as of 13:56, 31 May 2010
Line 53:		Line 53:
	# In ckfinder.html change: <br><br><source><script type="text/javascript" src="ckfinder.js"></script></source> into <br><br> <source><script type="text/javascript" src="ckfinder_v2.js"></script></source>		# In ckfinder.html change: <br><br><source><script type="text/javascript" src="ckfinder.js"></script></source> into <br><br> <source><script type="text/javascript" src="ckfinder_v2.js"></script></source>

−	~~This~~ method is not recommended, because you'll have to repeat steps above everytime you download a newer version of CKFinder.	+	'''Note:''' this method is not recommended, because you'll have to repeat steps above everytime you download a newer version of CKFinder.

← Older revision		Revision as of 13:56, 31 May 2010
Line 53:		Line 53:
	# In ckfinder.html change: <br><br><source><script type="text/javascript" src="ckfinder.js"></script></source> into <br><br> <source><script type="text/javascript" src="ckfinder_v2.js"></script></source>		# In ckfinder.html change: <br><br><source><script type="text/javascript" src="ckfinder.js"></script></source> into <br><br> <source><script type="text/javascript" src="ckfinder_v2.js"></script></source>

−	This method is not recommended, because you'll have to repeat ~~those~~ steps everytime you download a newer version of CKFinder.	+	This method is not recommended, because you'll have to repeat steps above everytime you download a newer version of CKFinder.

← Older revision		Revision as of 13:55, 31 May 2010
Line 52:		Line 52:
	# Rename ckfinder_v1.js to ckfinder.js		# Rename ckfinder_v1.js to ckfinder.js
	# In ckfinder.html change: <br><br><source><script type="text/javascript" src="ckfinder.js"></script></source> into <br><br> <source><script type="text/javascript" src="ckfinder_v2.js"></script></source>		# In ckfinder.html change: <br><br><source><script type="text/javascript" src="ckfinder.js"></script></source> into <br><br> <source><script type="text/javascript" src="ckfinder_v2.js"></script></source>
		+
		+	This method is not recommended, because you'll have to repeat those steps everytime you upgrade download a newer version of CKFinder.

← Older revision		Revision as of 13:54, 31 May 2010
Line 52:		Line 52:
	# Rename ckfinder_v1.js to ckfinder.js		# Rename ckfinder_v1.js to ckfinder.js
	# In ckfinder.html change: <br><br><source><script type="text/javascript" src="ckfinder.js"></script></source> into <br><br> <source><script type="text/javascript" src="ckfinder_v2.js"></script></source>		# In ckfinder.html change: <br><br><source><script type="text/javascript" src="ckfinder.js"></script></source> into <br><br> <source><script type="text/javascript" src="ckfinder_v2.js"></script></source>
−
−	~~...and that's it!~~

← Older revision		Revision as of 13:53, 31 May 2010
Line 43:		Line 43:

	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.
		+
		+	==== Method 3 ====
		+	<div style="border:1px solid #444;padding:5px;margin-bottom:5px;">Please make sure that you're using CKFinder downloaded after May 31th, 2010 to be able to follow this method.</div>
		+	This method is similar to method (2), but does not require any changes in existing applications.
		+	Instead, we just rename some files from CKFinder package.
		+
		+	# Rename ckfinder.js to ckfinder_v2.js
		+	# Rename ckfinder_v1.js to ckfinder.js
		+	# In ckfinder.html change: <br><br><source><script type="text/javascript" src="ckfinder.js"></script></source> into <br><br> <source><script type="text/javascript" src="ckfinder_v2.js"></script></source>
		+
		+	...and that's it!