laraveldaily / laravel-roles-permissions-bouncer Goto Github PK

For example if I want to edit the <title>{{ trans('panel.site_title') }}</title> to output not "Permissions Bouncer" but something else? Where do I edit it? Also if I want to use a trans('global.login_username') instead of trans('global.login_email') ?

First thanks for your wonderful example. It reduce to spending lot of time to work on Role based authentication.

I'm working in a project with Client and their members. Based on your example we can create Multiple Role like Admin,Client, Member, etc ... We can restrict the client don't see the Admin details and Member don't see the Admin and client details. So Admin can control all Client and members, client can control all members. Here is my problem.

I want to make a Client can view and control their members only. Not interact with other Client members. It's like a Group. So a Client have a group. He can control their group members only.

I have an idea to make that, While a Client create a user, we can get the id of the client and store it in a db column. So we can use a query to fetch the all users respect to their clients. But is it secure ? or I want to make separate table to hold the relationship like 'client_id, user_id,created_at,updated_at' ?

Please give me some suggestions ?

When i try to logout it shows me 404 /login not found

Hello,
not exactly a problem with your package but with Bouncer, but I thought it might help others.

What I am trying to do: Install a clean laravel-roles-permissions-bouncer

What I do:
I follow all the outlined steps for installation, which finishes with no errors. Then I want to update the packages, so I issue composer update

What I get:

Error Declaration of Silber\Bouncer\Database\HasRolesAndAbilities::isNot($role) should be compatible with Illuminate\Database\Eloquent\Model::isNot(Illuminate\Database\Eloquent\Model $model)

This seems due to an incompatibility between Bouncer and Laravel versions 5.4.x with x at least 31 and up (it seems), as noted in this issue

(Temporary) Solution: either change composer.json line from
"silber/bouncer": "v1.0.0-beta.2"
to
"silber/bouncer": "v1.0.0-beta.3"

OR

change composer.json line from
"laravel/framework": "5.4.*",
to
"laravel/framework": "5.4.28",

The update method in the RolesController does not work.

Line 98 has:

foreach ($role->abilities() as $ability)

and I think it should be:

foreach ($role->getAbilities() as $ability)

I've done some minor modifications to AdminLTE (including applying a purchased admin template rather than AdminLTE) and now I am unable to mass-delete users. Instead, I receive a MethodNotAllowedHttpException in RouteCollection.php (line 251). What pieces need to be in place so that mass delete button will work?

Also, please forgive me for being a complete newbie to AdminLTE and Bouncer, as well as a still-learning rookie with Laravel.

New Install.
Run php artisan migrate --seed
I get ErrorException
[ErrorException] compact(): Undefined variable: operator

If we have edit permission name after assign to a user then i got error because you directly check permission name on view like @can('users_manage') it is not dynamic method

i'm noob in laravel sorry for if i missing some thing

i have put pr for it #11

Hi,
im starting to use laravel (and boucer), i looked over your code but i couldnt find how this works

https://github.com/LaravelDaily/laravel-roles-permissions-bouncer/blob/master/resources/views/actionsTemplate.blade.php

where does $gateKey and $routeKey are coming from?

im thinking in use this pattern for the abilities name:
https://voyager.readme.io/docs/permissions

and i think i will need something like the actionstemplate, but i couldnt find where in the code you used it.