We need to deal with editing articles. Of course we can add new routes manually, like this:
<code>Route::get('/articles/{id}/edit', 'ArticleController@edit');</code>
Let’s use artisan
’s route:list
from the command line to view our current routes:
<code>php artisan route:list</code>
In the case of RESTful compliance, it may be a good choice to directly use laravel's resource
route. However, we will remove all routes and only add the only one:
<code>Route::resource('articles', 'ArticlesController');</code>
Use <code>php artisan route:list</code> again to view the routes, wow, a bunch of routes that meet our expectations are generated. Look at each item carefully.
Now add method in controller:
<code> public function edit($id) { $article = Article::findOrFail($id); return view('articles.edit', compact('article')); }</code>
Create View Now
<code>@extends('layout') @section('content') <h1 id="Edit-article-gt-title">Edit: {!! $article->title !!} </h1> <hr> ...</code>
Okay, I admit that these codes are all copied from create.blade.php
and modified a bit. The question is do we need to repeat them? We will deal with this issue later, now let’s look at the form submission issue. In the routing <code>php artisan route:list</code>, look again and use the PATCH
method. Let’s modify the view:
<code>{!! Form::open(['method' => 'PATCH', 'url' => 'articles/' . $article->id]) !!} </code>
Visit /articles/1/edit
in the browser, check the source code, and find that laravel automatically generates the hidden field of _method=PATCH
.
The first problem is that we edit the article, but the information of the article is not displayed. Let’s modify the view:
<code> {!! Form::model($article, ['method' => 'PATCH', 'url' => 'articles/' . $article->id]) !!}</code>
OK, everything's ok, except that the published_on
field is still set to the current date, we'll deal with that later.
Now add method in controller:
<code> public function update($id, \Illuminate\Http\Request $request) { $article = Article::findOrFail($id); $article->update($request->all()); return redirect('articles'); }</code>
We also need to verify during the modification process. Let us reuse our Request class and rename CreateArticleRequest
to the more general ArticleRequest
. Don’t forget to modify the parameters in the store
method.
<code> public function update($id, Requests\ArticleRequest $request) { $article = Article::findOrFail($id); $article->update($request->all()); return redirect('articles'); }</code>
The remaining problem now is that our new and edit use most of the same code, such as displaying errors, but there are two copies of them, let's fix this problem.
We create a new file list.blade.php
directly under views/articles
, and copy the error handling code from create.blade.php
:
<code>@if ($errors->any()) <ul class="alert alert-danger"> @foreach($errors->all() as $error) <li>{{ $error }}</li> @endforeach </ul> @endif</code>
In create.blade.php
just replace the error handling code with the following statement:
<code>@include('articles.list')</code>
Let’s deal with the form code again. The form code is almost the same except for form
which is different from the submit button. We create a view articles/form_partial.blade.php
and copy the code
<code><div class="form-group"> {!! Form::label('title', 'Title:') !!} {!! Form::text('title', null, ['class' => 'form-control']) !!} </div> <div class="form-group"> {!! Form::label('body', 'Body:') !!} {!! Form::textarea('body', null, ['class' => 'form-control']) !!} </div> <div class="form-group"> {!! Form::label('published_at', 'Publish On:') !!} {!! Form::input('date', 'published_at', date('Y-m-d'), ['class' => 'form-control']) !!} </div> <div class="form-group"> {{--这里要设置变量,依据是编辑还是修改来改变,当然也可以不放置在partial中--}} {!! Form::submit($submitButtonText, ['class' => 'btn btn-primary form-control']) !!} </div></code>
Modify create.blade.php
<code>@extends('layout') @section('content') <h1 id="Write-a-New-Article">Write a New Article</h1> <hr> @include('articles.list') {{--使用我们添加的 illuminate\html 开源库--}} {!! Form::open(['url' => 'articles']) !!} @include('articles.form_partial', ['submitButtonText' => 'Add Article']) {!! Form::close() !!} @stop</code>
Modify edit.blade.php
<code>@extends('layout') @section('content') <h1 id="Edit-article-gt-title">Edit: {!! $article->title !!} </h1> <hr> @include('articles.list') {{--使用我们添加的 illuminate\html 开源库--}} {!! Form::model($article, ['method' => 'PATCH', 'url' => 'articles/' . $article->id]) !!} @include('articles.form_partial', ['submitButtonText' => 'Update Article']) {!! Form::close() !!} @stop</code>
The above has introduced the basics of Laravel 5 (11) - Subview and form reuse, including aspects of it. I hope it will be helpful to friends who are interested in PHP tutorials.

ThesecrettokeepingaPHP-poweredwebsiterunningsmoothlyunderheavyloadinvolvesseveralkeystrategies:1)ImplementopcodecachingwithOPcachetoreducescriptexecutiontime,2)UsedatabasequerycachingwithRedistolessendatabaseload,3)LeverageCDNslikeCloudflareforservin

You should care about DependencyInjection(DI) because it makes your code clearer and easier to maintain. 1) DI makes it more modular by decoupling classes, 2) improves the convenience of testing and code flexibility, 3) Use DI containers to manage complex dependencies, but pay attention to performance impact and circular dependencies, 4) The best practice is to rely on abstract interfaces to achieve loose coupling.

Yes,optimizingaPHPapplicationispossibleandessential.1)ImplementcachingusingAPCutoreducedatabaseload.2)Optimizedatabaseswithindexing,efficientqueries,andconnectionpooling.3)Enhancecodewithbuilt-infunctions,avoidingglobalvariables,andusingopcodecaching

ThekeystrategiestosignificantlyboostPHPapplicationperformanceare:1)UseopcodecachinglikeOPcachetoreduceexecutiontime,2)Optimizedatabaseinteractionswithpreparedstatementsandproperindexing,3)ConfigurewebserverslikeNginxwithPHP-FPMforbetterperformance,4)

APHPDependencyInjectionContainerisatoolthatmanagesclassdependencies,enhancingcodemodularity,testability,andmaintainability.Itactsasacentralhubforcreatingandinjectingdependencies,thusreducingtightcouplingandeasingunittesting.

Select DependencyInjection (DI) for large applications, ServiceLocator is suitable for small projects or prototypes. 1) DI improves the testability and modularity of the code through constructor injection. 2) ServiceLocator obtains services through center registration, which is convenient but may lead to an increase in code coupling.

PHPapplicationscanbeoptimizedforspeedandefficiencyby:1)enablingopcacheinphp.ini,2)usingpreparedstatementswithPDOfordatabasequeries,3)replacingloopswitharray_filterandarray_mapfordataprocessing,4)configuringNginxasareverseproxy,5)implementingcachingwi

PHPemailvalidationinvolvesthreesteps:1)Formatvalidationusingregularexpressionstochecktheemailformat;2)DNSvalidationtoensurethedomainhasavalidMXrecord;3)SMTPvalidation,themostthoroughmethod,whichchecksifthemailboxexistsbyconnectingtotheSMTPserver.Impl


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SublimeText3 Linux new version
SublimeText3 Linux latest version

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

Notepad++7.3.1
Easy-to-use and free code editor
