ACL Technique in Joomla! - Revision history

Hutchy68: removing 1.7, still testing varchar use

2013-04-25T11:49:30Z

removing 1.7, still testing varchar use

2013-04-25T05:45:02Z

‎The #__assets table: reverting to source varchar issue fixed

2013-04-23T07:55:53Z

Mark as incomplete due to the number of TODO's marked on the page

Hutchy68: /* The #__assets table */ making tags

 tags

2013-04-22T18:15:52Z

‎The #__assets table: making <source> tags <pre> tags

2013-04-22T08:07:51Z

Add version tag

2012-09-24T08:13:18Z

added a section "ACL-related methods in JControllerForm and JModelAdmin"

2012-08-24T12:42:44Z

‎Introduction

2012-08-24T12:41:28Z

added intro to skeleton and added the sql for the assets database table

2012-08-24T10:50:06Z

‎The #__assets table

2012-08-24T10:49:29Z

‎JUser authorisation methods and properties

← Older revision		Revision as of 11:49, 25 April 2013
Line 1:		Line 1:
−	{{version\|~~1.7,~~2.5,3.1\|platform=11.1}}{{incomplete}}{{RightTOC}}	+	{{version\|2.5,3.1\|platform=11.1}}{{incomplete}}{{RightTOC}}

	A technical overview of how Access Control is implemented in Joomla!.		A technical overview of how Access Control is implemented in Joomla!.

@@ Line 8: / Line 8: @@
 == The #__assets table ==
 The #__assets database table has the following structure (MySql):
-<pre>
+<source lang="mysql">
 CREATE TABLE IF NOT EXISTS `#__assets` (
    `id` int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT 'Primary Key',
@@ Line 15: / Line 15: @@
    `rgt` int(11) NOT NULL DEFAULT '0' COMMENT 'Nested set rgt.',
    `level` int(10) unsigned NOT NULL COMMENT 'The cached level in the nested tree.',
-   `name` var<nowiki></nowiki>char(50) NOT NULL COMMENT 'The unique name for the asset.',
+   `name` varchar(50) NOT NULL COMMENT 'The unique name for the asset.',
-   `title` var<nowiki></nowiki>char(100) NOT NULL COMMENT 'The descriptive title for the asset.',
+   `title` varchar(100) NOT NULL COMMENT 'The descriptive title for the asset.',
-   `rules` var<nowiki></nowiki>char(5120) NOT NULL COMMENT 'JSON encoded access control.',
+   `rules` varchar(5120) NOT NULL COMMENT 'JSON encoded access control.',
    PRIMARY KEY (`id`),
    UNIQUE KEY `idx_asset_name` (`name`),
@@ Line 23: / Line 23: @@
    KEY `idx_parent_id` (`parent_id`)
 );
-</pre>
+</source>
 TODO: describe the Assets database table. Fields, layout and purpose.

← Older revision		Revision as of 07:55, 23 April 2013
Line 1:		Line 1:
−	{{version\|1.7,2.5,3.1\|platform=11.1}}{{RightTOC}}	+	{{version\|1.7,2.5,3.1\|platform=11.1}}{{incomplete}}{{RightTOC}}

	A technical overview of how Access Control is implemented in Joomla!.		A technical overview of how Access Control is implemented in Joomla!.

@@ Line 8: / Line 8: @@
 == The #__assets table ==
 The #__assets database table has the following structure (MySql):
-<source lang="mysql">
+<pre>
 CREATE TABLE IF NOT EXISTS `#__assets` (
    `id` int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT 'Primary Key',
@@ Line 23: / Line 23: @@
    KEY `idx_parent_id` (`parent_id`)
 );
-</source>
+</pre>
 TODO: describe the Assets database table. Fields, layout and purpose.

@@ Line 1: / Line 1: @@
-{{JVer|Platform}}{{JVer|2.5}}{{JVer|3.0}}
+{{version|1.7,2.5,3.1|platform=11.1}}{{RightTOC}}
 A technical overview of how Access Control is implemented in Joomla!.
@@ Line 15: / Line 15: @@
    `rgt` int(11) NOT NULL DEFAULT '0' COMMENT 'Nested set rgt.',
    `level` int(10) unsigned NOT NULL COMMENT 'The cached level in the nested tree.',
-   `name` varchar(50) NOT NULL COMMENT 'The unique name for the asset.',
+   `name` var<nowiki></nowiki>char(50) NOT NULL COMMENT 'The unique name for the asset.',
-   `title` varchar(100) NOT NULL COMMENT 'The descriptive title for the asset.',
+   `title` var<nowiki></nowiki>char(100) NOT NULL COMMENT 'The descriptive title for the asset.',
-   `rules` varchar(5120) NOT NULL COMMENT 'JSON encoded access control.',
+   `rules` var<nowiki></nowiki>char(5120) NOT NULL COMMENT 'JSON encoded access control.',
    PRIMARY KEY (`id`),
    UNIQUE KEY `idx_asset_name` (`name`),

@@ Line 75: / Line 75: @@
 == access.xml ==
 TODO: describe the use of the access.xml file
 == How it all comes together ==
-TODO: describe how the above parts are used together in a workflow
+TODO: describe how all the above parts are used together in a workflow
 == Further reading ==

@@ Line 4: / Line 4: @@
 == Introduction ==
-TODO: short intro about different parts in the system that work together as one Access Control.
+TODO: short intro about different parts that work together as one Access Control system.
 == The #__assets table ==

@@ Line 40: / Line 40: @@
 * http://api.joomla.org/Joomla-Platform/User/JUserHelper.html
 * http://api.joomla.org/Joomla-Platform/User/JAuthentication.html and http://api.joomla.org/Joomla-Platform/User/JAuthenticationResponse.html
-* http://api.joomla.org/Joomla-Platform/Table/JTableUser.html
+* http://api.joomla.org/Joomla-Platform/Table/JTableUser.html and http://api.joomla.org/Joomla-Platform/Table/JTableUsergroup.html
 == JTable methods and properties for storing access permissions ==