Download the PHP package hacoidev/permissionmanager without Composer

On this page you can find all versions of the php package hacoidev/permissionmanager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package permissionmanager

Backpack\PermissionManager

Build Status Quality Score Style CI Total Downloads

Admin interface for spatie/laravel-permission. It allows admins to easily add/edit/remove users, roles and permissions, using Laravel Backpack.

As opposed to some other packages:

This package is just a user interface for spatie/laravel-permission. It will install it, and let you use its API in code. Please refer to their README for more information on how to use in code.

Edit a user in Backpack/PermissionManager

Security updates and breaking changes

Please subscribe to the Backpack Newsletter so you can find out about any security updates, breaking changes or major features. We send an email every 1-2 months.

Install

0) This package assumes you've already installed Backpack for Laravel. If you haven't, please install Backpack first.

1) In your terminal:

2) Finish all installation steps for spatie/laravel-permission, which as been pulled as a dependency. Run its migrations. Publish its config files. Most likely it's:

3) Publish backpack\permissionmanager config file & the migrations:

Note: We recommend you to publish only the config file and migrations, but you may also publish lang and routes.

4) Run the migrations:

5) The package assumes it's ok to use the default Backpack user model (most likely to administer Users. Use a different one if you'd like by changing the user model in the file. Any model you're using, make sure it's using the and traits:

6) [Optional] Add a menu item for it in or :

7) [Optional] If you want to use the handler inside Backpack routes, you can:

(7.A.) Change Backpack to use the default guard instead of its own guard. Inside change:

Note:

OR

(7.B.) Add a middleware to all your Backpack routes by adding this to your file:

Why? spatie/laravel-permission uses the facade for determining permissions with . The facade uses the default guard defined in , NOT our backpack guard.

Please note:

8) [Optional] Disallow create/update on your roles or permissions after you define them, using the config file in config/backpack/permissionmanager.php. Please note permissions and roles are referenced in code using their name. If you let your admins edit these strings and they do, your permission and role checks will stop working.

Customize UserCrudController

If you would like to add more fields to the default user controller provided by this package, you can bind your own controller to overwrite the one provided in this package:

API Usage

Because the package requires spatie/laravel-permission, the API will be the same. Please refer to their README file for a complete API. Here's a summary though:

Using permissions

A permission can be given to a user:

A permission can be revoked from a user:

You can test if a user has a permission:

Saved permissions will be registered with the Illuminate\Auth\Access\Gate-class. So you can test if a user has a permission with Laravel's default can-function.

Using roles and permissions

A role can be assigned to a user:

A role can be removed from a user:

You can determine if a user has a certain role:

You can also determine if a user has any of a given list of roles:

You can also determine if a user has all of a given list of roles:

The assignRole, hasRole, hasAnyRole, hasAllRoles and removeRole-functions can accept a string, a Role-object or an \Illuminate\Support\Collection-object.

A permission can be given to a role:

You can determine if a role has a certain permission:

A permission can be revoked from a role:

The givePermissionTo and revokePermissionTo-functions can accept a string or a Permission-object.

Saved permission and roles are also registered with the Illuminate\Auth\Access\Gate-class.

Using blade directives

This package also adds Blade directives to verify whether the currently logged in user has all or any of a given list of roles.

You can use Laravels native @can directive to check if a user has a certain permission.

Upgrade from 3.x to 4.x

To upgrade from PermissionManager 3.x to 4.x:

If you are upgrading to a Laravel 8 instalation, please note that User Model may have moved from to , check if your config is compliant with that change .

Change log

Please see CHANGELOG for more information what has changed recently.

Overwriting functionality

If you need to modify how this works in a project:

When creating your own controllers, seeders, make sure you use the model, instead of the model in your app. The easiest would be to use which pulls in the User model fully qualified namespace, as defined in your . You might need to instantiate it using in order to do things like .

Contributing

Please see CONTRIBUTING for details.

Security

If you discover any security related issues, please email [email protected] instead of using the issue tracker.

Please subscribe to the Backpack Newsletter so you can find out about any security updates, breaking changes or major features. We send an email every 1-2 months.

Credits

License

Backpack is free for non-commercial use and 49 EUR/project for commercial use. Please see backpackforlaravel.com for more information.

Hire us

We've spend more than 50.000 hours creating, polishing and maintaining administration panels on Laravel. We've developed e-Commerce, e-Learning, ERPs, social networks, payment gateways and much more. We've worked on admin panels so much, that we've created one of the most popular software in its niche - just from making public what was repetitive in our projects.

If you are looking for a developer/team to help you build an admin panel on Laravel, look no further. You'll have a difficult time finding someone with more experience & enthusiasm for this. This is what we do. Contact us. Let's see if we can work together.


All versions of permissionmanager with dependencies

PHP Build Version
Package Version
Requires spatie/laravel-permission Version ^5.0|^4.0|^3.0
hacoidev/crud Version ^1.0.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package hacoidev/permissionmanager contains the following files

Loading the files please wait ....