new tables and models for RBAC system: gender,profile,role,status,user_type
added helpers: ValueHelpers, PermissionHelpers and RecordHelpers
Access control to backend by enforcing an active status and minimum value to the role of the user (at least admin role).
Access control to frontend by enforcing an active status of the user.
delete fake "id" columns from role,status and user_type tables = better relations
working user profile
We created an upgrade controller and view and then enforced rules to bring the user to the page if they didn’t meet the minimum user type allowed for access. We did this by adding a PermissionsHelper method, requireUpgradeTo(‘Paid’) to the update method on the profile controller.
We also added a requirement for the user to have a status of active. This tightens up security and access and did this by adding a matchCallback requirement to the access rules in the behaviors method.
Social widgets on the home page (more widgets: http://www.yiiframework.com/doc- 2.0/guide-widget-bootstrap.html)
Font awesome integration (icons: http://fortawesome.github.io/Font- Awesome/)
First step of backend creation: CRUD for profile,role,status,user and user type models