Template:Ckfinder 2.x ACL Examples - Revision history

J.swiderski at 14:51, 7 March 2013

2013-03-07T14:51:33Z

J.swiderski at 14:26, 7 March 2013

2013-03-07T14:26:31Z

J.swiderski at 14:25, 7 March 2013

2013-03-07T14:25:17Z

Anna: Header level changed

2011-03-31T08:31:54Z

Header level changed

Anna: Template contents expanded

2011-03-31T08:29:44Z

Template contents expanded

Anna: Article content moved to a template

2011-03-31T08:15:15Z

Article content moved to a template

New page

== Access Control List Examples ==
Have a look at the following examples that present various permission configurations in order to learn more about using Access Control Lists in CKFinder.

=== Example 1 ===
If you want to restrict the upload, renaming, or deletion of files in the <code>Logos</code> folder of the resource type <code>Images</code>, use the following ACL settings.

@@ Line 27: / Line 27: @@
 *Folder path has to start from slash character.
-*If you use a wildcard for resource type {{{wildcard_resource}}}, CKFinder will look through all resource types and apply ACL to every folder that matches the rule, for example Files:/Logos, Flash:/Logos.
+*If you use a wildcard for resource type <code>{{{wildcard_resource}}}</code>, CKFinder will look through all resource types and apply ACL to every folder that matches the rule, for example Files:/Logos, Flash:/Logos.
 <br>

@@ Line 27: / Line 27: @@
 *Folder path has to start from slash character.
-*If you use a wildcard for resource type (acl.ResourceType = "*";), CKFinder will look through all resource types and apply ACL to every folder that matches the rule, for example Files:/Logos, Flash:/Logos.
+*If you use a wildcard for resource type {{{wildcard_resource}}}, CKFinder will look through all resource types and apply ACL to every folder that matches the rule, for example Files:/Logos, Flash:/Logos.
 <br>

← Older revision		Revision as of 14:25, 7 March 2013
Line 15:		Line 15:

	Now a user can view and create a folder, but he will be unable to rename or delete it.		Now a user can view and create a folder, but he will be unable to rename or delete it.
		+
		+	== Explaining Folder Path for Example 1 <br>==
		+
		+	In the first example above the <code>/Logos</code> path was used in ACL definition. It is rather obvious that this is not an absolute path to folder on the server.<br>
		+
		+	Let us assume that the absolute path on server to the application folder is <code>/sites/example.com/</code> and the path to userfiles folder is <code>/sites/example.com/userfiles/</code>.There is also <code>"Images"</code> resource type which in this case points to <code>/sites/example.com/userfiles/images/</code>.<br>
		+
		+	Knowing the above let's define correct path for the <code>Logos</code> folder located in <code>/sites/example.com/userfiles/images/Logos</code>. The key is to define '''path relative to resource type''' (In this case resource type is <code> "Images" </code> pointing to <code>/sites/example.com/userfiles/images/</code>), thus the value that needs to be assigned to ACL folder property is <code> /Logos/</code>.<br>
		+
		+	Please also note that:
		+	*Folder path has to start from slash character.
		+
		+	If you use a wildcard for resource type (acl.ResourceType = "";), CKFinder will look through all resource types and apply ACL to every folder that matches the rule, for example Files:/Logos, Flash:/Logos.
		+	<br>

@@ Line 9: / Line 9: @@
 This example only refers to file operations in the <code>/Logos</code> folder. It does not restrict operations on the folder, so the user can delete or rename it. In order to limit users' ability to modify the folder itself (not its contents), you should change permissions in the parent folder.
-==== Example 2 ====
+=== Example 2 ===
 The following settings restrict folder operations for the <code>Images</code> resource type.

← Older revision		Revision as of 08:29, 31 March 2011
Line 4:		Line 4:
	=== Example 1 ===		=== Example 1 ===
	If you want to restrict the upload, renaming, or deletion of files in the <code>Logos</code> folder of the resource type <code>Images</code>, use the following ACL settings.		If you want to restrict the upload, renaming, or deletion of files in the <code>Logos</code> folder of the resource type <code>Images</code>, use the following ACL settings.
		+
		+	{{{example1}}}
		+
		+	This example only refers to file operations in the <code>/Logos</code> folder. It does not restrict operations on the folder, so the user can delete or rename it. In order to limit users' ability to modify the folder itself (not its contents), you should change permissions in the parent folder.
		+
		+	==== Example 2 ====
		+	The following settings restrict folder operations for the <code>Images</code> resource type.
		+
		+	{{{example2}}}
		+
		+	Now a user can view and create a folder, but he will be unable to rename or delete it.