Chapter 15For your developer
Known issues
Ten dashboard screens return a server error instead of loading. None of them stop you running the club — every one has a working route to the same job — but they should be fixed. Hand this page to whoever maintains the site.
If you hit one of these, you have not broken anything.These were broken before this guide was written. Use the workaround listed beside each one.
15.1
Training → Edit (the one that matters)
Editing an existing training session fails. This is routine club admin, so it is the most disruptive of the ten.
WhereCricket›Club & Community›Training
| Detail | |
|---|---|
| Screen | /admin/training/{id}/edit |
| Error | Undefined variable $trainingSession |
| File | resources/views/admin/training/edit.blade.php |
| Cause | The controller passes the session under a different variable name than the view expects. |
| Workaround | Delete the session and create it again. |
15.2
Five “view detail” screens
Clicking a row to view its detail page fails on these five. The Edit screen for each one works normally and shows the same information.
| Screen | Error |
|---|---|
| Events → Show | EventController::show() not implemented |
| Sponsors → Show | SponsorController::show() not implemented |
| Videos → Show | VideoController::show() not implemented |
| Awards → Show | method not implemented |
| Girls Academy → Show | GirlsAcademyTeamController::show() not implemented |
Workaround.Use Edit instead of clicking the row. It opens the same record and shows everything the detail page would.
15.3
Four “Add New” screens
The dedicated Add New form fails on these four. In each case you can still add records from the list screen itself.
| Screen | Error |
|---|---|
| Blog Categories → Create | method not implemented |
| Club Milestones → Create | method not implemented |
| Club Values → Create | method not implemented |
| Sponsor Packages → Create | method not implemented |
Workaround.Add and edit these from the list screen, which works normally.
15.4
What is actually wrong
All ten share one cause, and the fix is small.
How to change it
- Each of these modules is registered with
Route::resource(), which creates all seven standard routes — index, create, store, show, edit, update, destroy. - The controllers only implement some of those methods.
- So the route exists and the link is clickable, but the method behind it does not exist, and Laravel raises a 500.
- The fix is to add the missing controller methods, or to restrict the route with
Route::resource(...)->only([...])so the dead links are never generated. - The training one is separate: rename the variable in
edit.blade.phpto match what the controller passes.
Two screens could not be checked.Sponsor Packages → Edit and Sponsor Requests → View have no records in the database, so there was nothing to open. They may work, or they may fail the same way — worth testing once you have real data.