laravel4cookbook

File-Based CMS 329
1 Route::any("admin/layout/add", [
2 "as" => "admin/layout/add",
3 "uses" => "LayoutController@addAction"
4 ]);
.
This was extracted from app/routes.php.
The form processing, in the addAction() method, is wrapped in a check for the save parameter. This
is the name of the submit button on the add form. We specify the validation rules (including one of
those we defined in the constructor). If validation fails, we redirect back to the add page, bringing
along the errors and old input. If not, we create a new file with the default meta title and default
meta description as metadata. Finally we redirect to the index page.
The view is fairly standard (including the bootstrap tags we’ve used). The name and code fields have
error messages and all of the fields have their values set to the old input values. We’ve also added a
route to the add page.
Edit follows a similar pattern:
1 public function editAction()
2 {
3 $layout = Input::get("layout");
4 $name = str_ireplace(".blade.php", "", $layout);
5 $content = $this->filesystem->read("layouts/" . $layout);
6 $extracted = $this->engine->extractMeta($content);
7 $code = trim($extracted["template"]);
8 $parsed = $this->engine->parseMeta($extracted["meta"]);
9 $title = $parsed["title"];
10 $description = $parsed["description"];
11
12 if (Input::has("save"))
13 {
14 $validator = Validator::make(Input::all(), [
15 "name" => "required|edit:" . Input::get("layout"),
16 "code" => "required"
17 ]);
18
19 if ($validator->fails())
20 {
21 return Redirect::route("admin/layout/edit")
22 ->withInput()