StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18694545
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-09T08:46:23.913
FavoriteCount
0
LastActivityDate
2013-09-09T08:46:23.913
LastEditDate
LastEditorUserId
0
OwnerUserId
1156254
ParentId
18069276
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I do something very similar in my application, but after some trial and error myself I figured the best way to authenticate users and admins was to have two separate filters. So, here is what I do: I have an <code>auth</code> filter that simply logs a user in - <pre><code>Route::filter('auth', function() { if (Auth::guest()) return Redirect::to('login'); }); </code></pre> In addition to this, I have an <code>auth.admin</code> filter that checks for the logged in Users role: <pre><code>Route::filter('auth.admin', function() { if(Auth::user()->userprofile->security_level < 4) { return Redirect::route('projects.home'); } }); </code></pre> One caveat to remember is that to not use the <code>auth.admin</code> filter, standalone, in your routes. Will throw an error when the user is not logged in. You can do something like: <pre><code>Route::group(array('before' => 'auth'), function() { Route::get('user', array('as' => 'user.home', 'uses' => 'UsersController@index'));}); } Route::group(array('before' => 'auth|auth.admin'), function() { Route::get('user/create', array('as' => 'user.create', 'uses' => 'UsersController@create')); }); </code></pre> With this setup, add the pages you want only your admin to access to the latter routing group with <code>auth</code> and <code>auth.admin</code>. Now, with this setup, you don't need to check for logic in your composer. Ideally, your routing (or your controller, based on what your argument is) should handle your routing logic. You can rewrite your composer like this: <pre><code>View::composer( array( 'common.menu_addition','common.base_errors' ), function( $view ) { // get all categories using the category model $categories = Category::all(); $view->with( 'categories', $categories ); }); </code></pre> A composer is used to pass the same set of data or to carry out the same set of tasks for a set of views. I am sure this will sort you out ;)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLaravel 4 filters and view composers
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USrizwaniqbal
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. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.