- using `Model::where('download', '=', 1)` over`Model::where('download', 1)`
- decided is easier for new devs to understand.
- thanks to @werrpy for helping with the regex to mass update.
--- Issue ---
When you create a new group it never sets up any forums permissions for
that group. This was causing errors like
Trying to get property 'show_forum' of non-object ...
This is due to in code its trying to access a property of a null object,
this is fatal and cause the app to crash, this happens when the page
tries and loads permissions for that group/forum and the groups
permissions is a null object.
--- Fix ---
In the add() method of the Staff/GroupsController.php we create a
permissions object for each forum and associate it to the new groups id.
--- Views ---
When using traditional form inputs and passing that data through
the request object, you should name the inputs the same name as the
database columns. This will make it easier in code to just pass the
request data to the create/update operations.
--- Models ---
When using mass assignments like Model::create() and/or Model::update(),
we have to tell the model to not guard those columns. So by adding
`protected $guarded = ['id'];` to the Model we say Only guard the 'id'.
Also, try and avoid the `Raw` eloquent queries!
--- Controllers ---
Validation rules should be in here and not in the Model and should be
validated BEFORE the creation of the resource!
--- Reminder ---
The Model is strictly for interacting with the database.
The Controller handles the http/ajax requests
The View handles how to present the data to the users screen
The Repository/Concrete Classes are to handle the application specific
logic
- #75
- Add Breadcrumbs
- Added missing group permissions/options
- Update Migration
- Cleanup/Refactor
- Note this does not fully close issue noted above. There is more to be
done which will be finalized in (Update) Groups System PT.2
HDVinnie