Role save problem about laravel-boilerplate

[rappasoft]

This is fixed in the upcoming 5.1 release. But you can fix it by going to EloquentRoleRepository.php to the update method and replacing it with this:

public function update($id, $input, $permissions) {
        $role = $this->findOrThrowException($id);

        //Validate
        if (strlen($input['name']) == 0)
            throw new GeneralException('You must specify the role name.');

        //See if the role must contain a permission as per config
        if (config('access.roles.role_must_contain_permission') && count($permissions['role_permissions']) == 0)
            throw new GeneralException('You must select at least one permission for this role.');

        $role->name = $input['name'];

        if ($role->save()) {
            //Remove all permissions
            $role->detachPermissions($role->permissions);

            //Attach permissions, if any
            if (count($permissions['role_permissions']) > 0)
                $role->attachPermissions($permissions['role_permissions']);

            return true;
        }

        throw new GeneralException('There was a problem updating this role. Please try again.');
    }

[rappasoft]

Delete that role and clear the permissions from it in the database as well to make sure its working properly.

[hawkefly]

Yes , it works perfect now, thank you.

[rappasoft]

No problem sorry meant to make a hotfix but was in the middle of the 5.1 conversion and didn't want to lose track of where I was.

[rappasoft]

Weird, it could be something to do with the way firefox handles sessions.

[rappasoft]

Though Laravel has been known to have Token exceptions on rapid refresh, just like on multiple AJAX calls at the same time. I don't know if there is a solution. But why are you refreshing several times on the dashboard?

[dhb52]

Another fatal problem to me, it seems with Firefox form submit fails more often than never.

[dhb52]

I removed 'App\Http\Middleware\VerifyCsrfToken' middleware, it still broken.
Sorry for the OT above.

Why not use Role::savePermissions for patch of this issue?

[rappasoft]

Good question, that's a better solution. Good call, i'll commit it.