StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POUnderstanding user permissions and how to apply it
primarykey
Id
11520448
data
AcceptedAnswerId
12220778
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-17T10:19:09.880
FavoriteCount
2
LastActivityDate
2012-08-31T18:29:30.983
LastEditDate
2012-07-17T20:55:16.963
LastEditorUserId
1157147
OwnerUserId
383691
ParentId
0
PostTypeId
1
Score
5
ViewCount
2561
LastEditorDisplayName
text
Body
I am developing a module for a site using <a href="http://www.socialengine.com/" rel="noreferrer">Social Engine</a>, which uses Zend Framework. I am new to both Zend Framework and Social Engine but have experience in OOP and MVC architecture so could get to grips with basics relatively quickly. Its a test module I'm developing so have just built a simple module where the user can create, edit or delete CD information. Then there is a widget which can be displayed where they like which shows there CD information. I am now at the point where I need to set permissions of what CDs people can see etc. So I studied other modules and found the Poll module to be a concrete example. Looking at other modules I realised that when you create something, they let the user set their permissions manually. So added this code to my form to create a select box with relevant permissions: <pre><code>$auth = Engine_Api::_()->authorization()->context; $user = Engine_Api::_()->user()->getViewer(); $viewOptions = (array) Engine_Api::_()->authorization()->getAdapter('levels')->getAllowed('ryan', $user, 'auth_view'); $viewOptions = array_intersect_key($availableLabels, array_flip($viewOptions)); $privacy = null; if( !empty($viewOptions) && count($viewOptions) >= 1 ) { // Make a hidden field if(count($viewOptions) == 1) { //$this->addElement('hidden', 'auth_view', array('value' => key($viewOptions))); $privacy = new Zend_Form_Element_Hidden('auth_view'); $privacy->setValue(key($viewOptions)); // Make select box } else { $privacy = new Zend_Form_Element_Select('auth_view'); $privacy->setLabel('Privacy') ->setDescription('Who may see this CD?') ->setMultiOptions($viewOptions) ->setValue(key($viewOptions)); /*$this->addElement('Select', 'auth_view', array( 'label' => 'Privacy', 'description' => 'Who may see this CD?', 'multiOptions' => $viewOptions, 'value' => key($viewOptions), ));*/ } } $this->addElements(array($artist, $title, $privacy, $submit)); </code></pre> To be honest I'm not entirely sure what this code does apart from obviously create a select box and fill it with values specified. So if the user selects 'Everyone' everyone should be able to delete and edit that cd, and so on. Obviously I thought controller must have some code that might deal with determining whether the user has the rights to view each cd etc. So scanning the Poll controller I found this is in the init function of the controller: <pre><code>public function init() { // Get subject $poll = null; if( null !== ($pollIdentity = $this->_getParam('poll_id')) ) { $poll = Engine_Api::_()->getItem('poll', $pollIdentity); if( null !== $poll ) { Engine_Api::_()->core()->setSubject($poll); } } // Get viewer $this->view->viewer = $viewer = Engine_Api::_()->user()->getViewer(); $this->view->viewer_id = Engine_Api::_()->user()->getViewer()->getIdentity(); // only show polls if authorized $resource = ( $poll ? $poll : 'poll' ); $viewer = ( $viewer && $viewer->getIdentity() ? $viewer : null ); if( !$this->_helper->requireAuth()->setAuthParams($resource, $viewer, 'view')->isValid() ) { return; } } </code></pre> And in each action at the top they have some different authorization code, one such example is the <code>editAction</code> which has this code right at the top: <pre><code>// Check auth if( !$this->_helper->requireUser()->isValid() ) { return; } if( !$this->_helper->requireSubject()->isValid() ) { return; } if( !$this->_helper->requireAuth()->setAuthParams(null, null, 'edit')->isValid() ) { return; } </code></pre> also in the same action is has several other bits i don't understand what they are doing, below is random snippets from the <code>editAction</code> in the Poll controller: <pre><code>$auth = Engine_Api::_()->authorization()->context; $roles = array('owner', 'owner_member', 'owner_member_member', 'owner_network', 'registered', 'everyone'); // Populate form with current settings $form->search->setValue($poll->search); foreach( $roles as $role ) { if( 1 === $auth->isAllowed($poll, $role, 'view') ) { $form->auth_view->setValue($role); } if( 1 === $auth->isAllowed($poll, $role, 'comment') ) { $form->auth_comment->setValue($role); } } // CREATE AUTH STUFF HERE if( empty($values['auth_view']) ) { $values['auth_view'] = array('everyone'); } if( empty($values['auth_comment']) ) { $values['auth_comment'] = array('everyone'); } $viewMax = array_search($values['auth_view'], $roles); $commentMax = array_search($values['auth_comment'], $roles); </code></pre> My problem is I really don't understand much if any of the above and after sitting on it for a couple of days and googling to my fingers hurt I still don't really have a clue if I am 100% honest. Can any of the above be cleared up for me, help explain things to me, and if possible how can i apply the permissions I want to my module. 
Tags
<php><zend-framework><permissions><user-permissions><socialengine>
Title
Understanding user permissions and how to apply it
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USByteNudger
UserOwnerUserId
1. USRSM
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POUnderstanding user permissions and how to apply it
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTApproveEditSuggestion
2. VO
 singulars
 PostPostId
 POUnderstanding user permissions and how to apply it
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POUnderstanding user permissions and how to apply it
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.