The component implements Joomla!'s powerful access control features and we recommend reading more about how Joomla! access control works if you are unsure:
-
ACL concepts overview http://magazine.joomla.org/issues/issue-jan-2012/item/637-Joomla-1-6,-1-7,-and-2-5- ACL-Concepts-Overview (beginners)
-
Joomla! ACL: Access Levels http://magazine.joomla.org/issues/issue-feb-2012/item/639-Joomla-ACL-Access- Levels (beginners; scroll all the way down for a very good video)
-
A case for role-based ACL http://magazine.joomla.org/issues/Issue-Aug-2012/item/825-A-Case-for-Role-Based- ACL (advanced)
-
Implementing role-based ACL http://magazine.joomla.org/issues/Issue-Sept-2012/item/856-Implementing-Role- Based-ACL (advanced)
-
ACL Manager http://www.aclmanager.net is a third party commercial component which can help you effectively managing ACLs on complex sites.
Alternatively, you'll have to just take our word and follow our easy instructions below.
In order to create a fully functional front end editing ability the component has built upon the ACL permissions available within Joomla. Previously the ACL defaults were based upon the component itself. Release 1.2.0 extends this to provide control at the individual issue level.
Note | |
---|---|
The component does not make use of the ‘categories’ which is used by other Joomla components. This does mean that there are changes in the use of the ACL rules. |
This change includes adding an additional field to the it_issues table which is a reference to the Joomla assets table, which contains the permissions for the individual issue. When installed the 1.2.0 update will add the asset_id field but will not populate the field. When the issue is next edited the value will be automatically populated. The implication of this is that a user will be unable to edit their own issues UNTIL such time as the existing issue is updated.
All new issues have the field automatically populated.
So to repeat: an existing user will be unable to edit any existing issues created prior to release 1.2.0 being installed unless the issues have been edited since the upgrade.
One suggested method to do this without causing the generation of a lot of notification emails is to temporarily turn off all notifications via the options and then edit each issue in the back end and then immediately save and close the issue. Of course you may only want to enable editing on some of the existing issues, in which case choose only those issues to edit. Unfortunately we cannot think of any easier way to perform the task, ensuring the integrity of the internal Joomla linkages.