Databases
StackOverflow2013
Postsdbo
POUsing Joomla 1.5 ACL for custom extension content - is this the right way?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Joomla 1.5 ACL for custom extension content - is this the right way?
    primarykey
    data
    text
    <p>I am developing a Joomla! 1.5 extention that has two types of registered users, each with access to their particular content.</p> <p>I have done alot of reading on utilising the Joomla ACL implementation to achieve this. I understand that it is based on phpGACL. </p> <p>I am seeking any guidance or advice if what I intend to do is the right approach.</p> <p>Suppose my extension is called "classroom".</p> <p>Suppose I have user types: "student" and "teacher"</p> <p>Both are registered users.</p> <p>"student" has access to "ebooks" "teacher" has access to "classregister"</p> <p>i assume that I use Access Extension Objects that will extend the Access Control Objects.</p> <pre><code>$extACL = &amp; JFactory::getACL(); //define permissions for teacher $extACL-&gt;_mos_add_acl('com_classroom','accessdata','users','registered','usersection','classregister'); //define permissions for student $extACL-&gt;_mos_add_acl('com_classroom','accessdata','users','registered','usersection','ebooks'); </code></pre> <p>Then as need arises, I can check permissions for (say) the "ebooks" area using the following</p> <pre><code>//After checking if it is the right user $user = &amp; JFactory-&gt;getUser(); if(! $user-&gt;authorize('com_classroom','accessdata','usersection','ebooks')) { JError::raiseError('403',JText::_('You are not logged in as a student')); } </code></pre> <p>Have I understood the right use of the Joomla! ACL for my extension or is it wrong? Or will I have to define my own access controls.</p> <p>Hope I made sense.</p> <p>Thanks for your time!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. UShbit
    1. USuser919426
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing Joomla 1.5 ACL for custom extension content - is this the right way?
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. CODo you mean Joomla 1.6/1.7? Joomle 1.5 didn't support proper ACL. Also Joomla 1.5 doesn't have much shelf-life left, I would avoid starting a new project with it.
      singulars
      1. POUsing Joomla 1.5 ACL for custom extension content - is this the right way?
      1. USudjamaflip
    2. COI never said it is a new project. I would appreciate 1.5 specific assistance. I am fully aware of the existance of new versions
      singulars
      1. POUsing Joomla 1.5 ACL for custom extension content - is this the right way?
      1. USuser919426
    3. COEither way your conceptual understanding of how the Joomla ACL in 1.5 (and also kind of 1.6/1.7) is correct, you extend the permission already set by the access extension object to define what controls each user group should have access to. Are you currently getting an error with this code?
      singulars
      1. POUsing Joomla 1.5 ACL for custom extension content - is this the right way?
      1. USudjamaflip
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload