Template:Ckfinder acl explanation - Revision history

Anna: Template contents expanded

2011-03-31T08:05:26Z

Template contents expanded

Anna: Template contents proof-read and formatted

2011-03-31T07:52:54Z

Template contents proof-read and formatted

Wiktor: New page: * '''role'''
The role is an attribute which sets the type of the user. It is set to "*" as default and you may treat as 'everybody'. You may set this parameter to other name like: 'user...

2008-01-11T09:26:14Z

New page: * '''role''' The role is an attribute which sets the type of the user. It is set to "*" as default and you may treat as 'everybody'. You may set this parameter to other name like: 'user...

New page

* '''role''' The role is an attribute which sets the type of the user. It is set to "*" as default and you may treat as 'everybody'. You may set this parameter to other name like: 'user' or 'limited_functions'. The name of the user type will be directly connected to the function the user may use. 

* '''resourceType''' The resourceType defines the resources handled in CKFinder. A resource type is nothing more than a way to group files under different paths, each one having different configuration settings, e.g. ''Images'', ''Flash'', ''Files''. It is set to '*' as default and means that all of the resources are available.

* '''folder''' ''' '''Folder determines where your limitations will be used. By placing the folders name you specify the place you want to put your restrictions in. It is set to '/' as default so no folder is set.

* '''folder and file options''' The rest of the variables are bool type and can be set as '''true''' or '''false'''. True of course enables an option, false disables it.

* '''other information''' Many "AccessControl" entries can be added. All attributes are optional. Subfolders inherit their default settings from their parents' definitions.

@@ Line 1: / Line 1: @@
 * <code>role</code> &ndash; this attribute sets the type of the user. By default it is set to <code>*</code> which can be treated as "everybody". You may set this parameter to other name like <code>user</code> or <code>limited_functions</code>. The name of the user type will be directly related to the functions the user can make use of.
@@ Line 7: / Line 8: @@
 * <code>folder*</code> and <code>file*</code> options &ndash; these variables are of Boolean type and can be set to <code>true</code> or <code>false</code>. The <code>true</code> setting enables an option, <code>false</code> disables it.
-* '''other information''' &ndash; it is possible to define numerous ACL entries. All attributes are optional. Subfolders inherit their default settings from their parents' definitions.
+* It is possible to define numerous ACL entries. All attributes are optional. Subfolders inherit their default settings from their parents' definitions.

@@ Line 1: / Line 1: @@
-* '''role'''<br>The role is an attribute which sets the type of the user. It is set to "*" as default and you may treat as 'everybody'. You may set this parameter to other name like: 'user' or 'limited_functions'. The name of the user type will be directly connected to the function the user may use.<br>
+* <code>role</code> &ndash; this attribute sets the type of the user. By default it is set to <code>*</code> which can be treated as "everybody". You may set this parameter to other name like <code>user</code> or <code>limited_functions</code>. The name of the user type will be directly related to the functions the user can make use of.
-* '''resourceType'''<br>The resourceType defines the resources handled in CKFinder. A resource type is nothing more than a way to group files under different paths, each one having different configuration settings, e.g. ''Images'', ''Flash'', ''Files''. It is set to '*' as default and means that all of the resources are available.
+* <code>resourceType</code> &ndash; this setting defines the resources handled in CKFinder. A resource type is nothing more than a way to group files under different paths, each having different configuration settings (like '''Images''', '''Flash''', '''Files'''). By default it is set to <code>*</code> which means that all resources are available.
-* '''folder''' '''<br>'''Folder determines where your limitations will be used. By placing the folders name you specify the place you want to put your restrictions in. It is set to '/' as default so no folder is set.
+* <code>folder</code> &ndash; this setting determines where the restrictions will be used. By declaring a folder name you specify the place you want to put your restrictions on. By default it is set to <code>/</code>, so no folder is set.
-* '''folder and file options''' <br>The rest of the variables are bool type and can be set as '''true''' or '''false'''. True of course enables an option, false disables it.
+* <code>folder*</code> and <code>file*</code> options &ndash; these variables are of Boolean type and can be set to <code>true</code> or <code>false</code>. The <code>true</code> setting enables an option, <code>false</code> disables it.
-* '''other information''' <br>Many "AccessControl" entries can be added. All attributes are optional.<br>Subfolders inherit their default settings from their parents' definitions.
+* '''other information''' &ndash; it is possible to define numerous ACL entries. All attributes are optional. Subfolders inherit their default settings from their parents' definitions.

Template:Ckfinder acl explanation - Revision history

Anna: Template contents expanded

Anna: Template contents proof-read and formatted

Wiktor: New page: * '''role'''The role is an attribute which sets the type of the user. It is set to "*" as default and you may treat as 'everybody'. You may set this parameter to other name like: 'user...

Wiktor: New page: * '''role'''
The role is an attribute which sets the type of the user. It is set to "*" as default and you may treat as 'everybody'. You may set this parameter to other name like: 'user...