Announcing Bonfire - A jumpstart for your web apps

[eluser]frozenmaiden[/eluser]
[quote author="kilishan" date="1306191799"]You are correct. You currently need to set the permissions you desire in the permissions table. This allows different roles to have different permissions.

To restrict/check access in your modules, see the has_permission() and restrict() methods in the Auth library docs.

If you have a suggestion for a better way to handle RBAC and modules, I'm all ears. I like simple solutions. [/quote]

Why not make one table for list of permissions and another table for assign the permissions into specific roles?

for example

Code:

bf_permissions : id | permissions_name
                  1 | Content

bf_roles_permissions : id | roles_name | permissions_id | add | edit | delete | view
                        1 | admin group|       1        |  1  |  1   |    1   |   1

What do you think? :red:

Btw,i make some modules "appointment" extends admin_controllers,but i didn't want it become one of the context(content,stat,etc) so i declare it like

Code:

class Appointment extends Admin_Controller {

}

How can i call the module ?
i try http://localhost/admin/appointment but it throw 404 hut: