Adding ACL rules to your component - Revision history

Wilsonge: Update 1.6/1.7 to 2.5. Update 3.0 to 3.1 and add incomplete tags because conclusion not finished

2013-04-29T09:07:10Z

Update 1.6/1.7 to 2.5. Update 3.0 to 3.1 and add incomplete tags because conclusion not finished

2013-02-01T17:25:51Z

Joomla Version update

2012-09-18T01:19:24Z

version/tutorial template

2012-06-28T13:04:51Z

‎Put Action Control In Action

2012-06-28T13:03:44Z

Changed some spelling and formatting.

2011-12-16T18:40:47Z

‎Using Your Action Control In Code

2011-12-05T13:53:20Z

‎Contributors

2011-12-05T13:47:08Z

‎Add Rules Field to Your Form

2011-12-05T13:45:24Z

‎ACL Architecture Overview

2011-12-05T13:01:35Z

@@ Line 1: / Line 1: @@
-{{version/tutor|1.6,1.7,2.5,3.0}}This tutorial will demonstrate how to add custom action permission to your component down to object level. Normally we familiar with ACL in global configuration level, category level and component level. Now we will learn how to add action permission control in our component.
+{{version/tutor|2.5,3.1}}{{incomplete}}
 == ACL Architecture Overview ==
-Action permissions for component in Joomla! 1.6 can be defined at up to 3 levels
+Action permissions for component in Joomla! 2.5 can be defined at up to 3 levels
 # '''Global Configuration''': determines the default permissions for each action and group.
 # '''Component Options->Permissions''': can override the default permissions for our component
@@ Line 193: / Line 194: @@
 [[Category:Tutorials]]
 [[Category:Access Control]]
-[[Category:Joomla! 1.6]]
+[[Category:Joomla! 2.5]]
-[[Category:Joomla! 1.7]]
+[[Category:Joomla! 3.1]]

← Older revision		Revision as of 17:25, 1 February 2013
Line 1:		Line 1:
−	{{version/tutor\|1.6,1.7}}This tutorial will demonstrate how to add custom action permission to your component down to object level. Normally we familiar with ACL in global configuration level, category level and component level. Now we will learn how to add action permission control in our component.	+	{{version/tutor\|1.6,1.7,2.5,3.0}}This tutorial will demonstrate how to add custom action permission to your component down to object level. Normally we familiar with ACL in global configuration level, category level and component level. Now we will learn how to add action permission control in our component.

	== ACL Architecture Overview ==		== ACL Architecture Overview ==

@@ Line 1: / Line 1: @@
-This tutorial will demonstrate how to add custom action permission to your component down to object level. Normally we familiar with ACL in global configuration level, category level and component level. Now we will learn how to add action permission control in our component.
+{{version/tutor|1.6,1.7}}This tutorial will demonstrate how to add custom action permission to your component down to object level. Normally we familiar with ACL in global configuration level, category level and component level. Now we will learn how to add action permission control in our component.
-{{JVer|1.6}} {{JVer|1.7}}
 == ACL Architecture Overview ==
 Action permissions for component in Joomla! 1.6 can be defined at up to 3 levels

@@ Line 129: / Line 129: @@
      if ($this->getState('suffix') == '14') {
-         // theses fields does not exists in Asterisk version 1.4
+         // theses fields do not exists in Asterisk version 1.4
          $form->setFieldAttribute('call-limit', 'disabled', 'true');
          $form->setFieldAttribute('call-limit', 'filter', 'unset');

@@ Line 106: / Line 106: @@
 You will see that I have also create new action for my component. The "asterman.edit.basic" action is to control if user has right to edit some part of the record or not.
-== Using Your Action Control In Code ==
+== Put Action Control In Action ==
 Using action control in your code is easy than you think, we use JUser 's method to do this. This method is authorise() which requires two parameters one is action and second one is assest name. Unlike our global component access control, here we refer to asset name per record, please JTable descandant class above.
 <source lang="php">

@@ Line 180: / Line 180: @@
+}
 </source>
 == Contributors ==
 [[User:mrs.siam|Prasit Gebsaap]]

@@ Line 79: / Line 79: @@
 </source>
-For rules field type, we have to provide component attribute as our component name and section attribute according to section define in our access.xml. Please see the example below.
+For rules field type, we have to provide '''component attribute''' as our component name and '''section attribute''' according to section defined in our access.xml. Please see the example below.
 <source>
 <?xml version="1.0" encoding="UTF-8"?>

@@ Line 7: / Line 7: @@
 # '''Record Options->Permissions''': this is what we discuss in this tutorial.
-The other level that you will see is '''Category''' which can override the default permissions for objects assigned to category. We can use this if we use category in our component. I separate this one from others as its parent is '''Global Configuration'''. But t
+The other level that you will see is '''Category''' which can override the default permissions for objects assigned to category. We can use this if we use category in our component. I separate this one from others as its parent is '''Global Configuration'''.
 == Using JTable To Handle Action Control Saving and Loading ==