Download the PHP package divdax/roles without Composer
On this page you can find all versions of the php package divdax/roles. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package roles
Short Description Powerful package for handling roles and permissions in Laravel 5.
License MIT
Informations about the package roles
Abandoned
The Roles and permissions for laraval 5 package is abandoned and will no longer be maintained by Ultraware. Feel free to fork the project and submit it to packagist. We can share the url to your package on this page if you send us a message.
Roles And Permissions For Laravel 5
Powerful package for handling roles and permissions in Laravel 5.
- Installation
- Composer
- Service Provider
- Config File And Migrations
- HasRoleAndPermission Trait And Contract
- Migrate from Bican roles
- Usage
- Creating Roles
- Attaching, Detaching and Syncing Roles
- Checking For Roles
- Levels
- Creating Permissions
- Attaching, Detaching and Syncing Permissions
- Checking For Permissions
- Permissions Inheriting
- Entity Check
- Blade Extensions
- Middleware
- Config File
- More Information
- License
Installation
This package is very easy to set up. There are only couple of steps.
Composer
Pull this package in through Composer
If you are still using Laravel 5.0, you must pull in version
1.7.*
.
Service Provider
Add the package to your application service providers in config/app.php
file.
Config File And Migrations
Publish the package config file and migrations to your application. Run these commands inside your terminal.
php artisan vendor:publish --provider="Ultraware\Roles\RolesServiceProvider" --tag=config
php artisan vendor:publish --provider="Ultraware\Roles\RolesServiceProvider" --tag=migrations
And also run migrations.
php artisan migrate
This uses the default users table which is in Laravel. You should already have the migration file for the users table available and migrated.
HasRoleAndPermission Trait And Contract
Include HasRoleAndPermission
trait and also implement HasRoleAndPermission
contract inside your User
model.
Migrate from bican roles
If you migrate from bican/roles to ultraware/roles yoe need to update a few things.
- Change all calls to
can
,canOne
andcanAll
tohasPermission
,hasOnePermission
,hasAllPermissions
. - Change all calls to
is
,isOne
andisAll
tohasRole
,hasOneRole
,hasAllRoles
.
Usage
Creating Roles
Because of
Slugable
trait, if you make a mistake and for example leave a space in slug parameter, it'll be replaced with a dot automatically, because ofstr_slug
function.
Attaching, Detaching and Syncing Roles
It's really simple. You fetch a user from database and call attachRole
method. There is BelongsToMany
relationship between User
and Role
model.
Checking For Roles
You can now check if the user has required role.
You can also do this:
And of course, there is a way to check for multiple roles:
Levels
When you are creating roles, there is optional parameter level
. It is set to 1
by default, but you can overwrite it and then you can do something like this:
If user has multiple roles, method
level
returns the highest one.
Level
has also big effect on inheriting permissions. About it later.
Creating Permissions
It's very simple thanks to Permission
model.
Attaching, Detaching and Syncing Permissions
You can attach permissions to a role or directly to a specific user (and of course detach them as well).
Checking For Permissions
You can check for multiple permissions the same way as roles. You can make use of additional methods like hasOnePermission
or hasAllPermissions
.
Permissions Inheriting
Role with higher level is inheriting permission from roles with lower level.
There is an example of this magic
:
You have three roles: user
, moderator
and admin
. User has a permission to read articles, moderator can manage comments and admin can create articles. User has a level 1, moderator level 2 and admin level 3. It means, moderator and administrator has also permission to read articles, but administrator can manage comments as well.
If you don't want permissions inheriting feature in you application, simply ignore
level
parameter when you're creating roles.
Entity Check
Let's say you have an article and you want to edit it. This article belongs to a user (there is a column user_id
in articles table).
This condition checks if the current user is the owner of article. If not, it will be looking inside user permissions for a row we created before.
Blade Extensions
There are four Blade extensions. Basically, it is replacement for classic if statements.
Middleware
This package comes with VerifyRole
, VerifyPermission
and VerifyLevel
middleware. You must add them inside your app/Http/Kernel.php
file.
Now you can easily protect your routes.
It throws \Ultraware\Roles\Exceptions\RoleDeniedException
, \Ultraware\Roles\Exceptions\PermissionDeniedException
or \Ultraware\Roles\Exceptions\LevelDeniedException
exceptions if it goes wrong.
You can catch these exceptions inside app/Exceptions/Handler.php
file and do whatever you want.
Config File
You can change connection for models, slug separator, models path and there is also a handy pretend feature. Have a look at config file for more information.
More Information
For more information, please have a look at HasRoleAndPermission contract.
License
This package is free software distributed under the terms of the MIT license.
All versions of roles with dependencies
illuminate/support Version 5.8|^6.0
illuminate/database Version 5.8|^6.0