laravel4cookbook

File-Based CMS 332
56 type="submit"
57 name="save"
58 class="btn btn-default"
59 value="Save"
60 />
61
62 @stop
.
This file should be saved as app/views/admin/layout/edit.blade.php.
1 Route::any("admin/layout/edit", [
2 "as" => "admin/layout/edit",
3 "uses" => "LayoutController@editAction"
4 ]);
.
This was extracted from app/routes.php.
The editAction() method fetches the layout file data and extracts/parses the metadata, so that we
can present it in the edit form. Other than utilising the second custom validation function, we define
in the constructor, there’s nothing else noteworthy in this method.
The edit form is also pretty much the same, except that we provide default values to the Input::old()
method calls, giving the data extracted from the layout file. We also add a route to the edit page.
.
You may notice that the file name remains editable, on the edit page. When you change this value,
and save the layout it won’t change the name of the current layout file, but rather generate a new
layout file. This is an interesting (and in this case useful) side-effect of using the file name as the
unique identifier for layout files.
Deleting layout files is even simpler: