What's wrong with laravel's new addition and the inability to edit it?
Apr 23, 2023 am 10:06 AMRecently, when developing a project using the Laravel framework, I discovered a problem: the newly added data cannot be edited. After further troubleshooting and analysis, I found the problem and solved it. Let me share some solution ideas below.
First of all, we need to clarify a concept - HTTP request method. HTTP request method refers to the method used by the client when requesting resources from the server, including GET, POST, PUT, DELETE, etc. Among them, the GET method is used to obtain resources, the POST method is used to create resources, the PUT method is used to update resources, and the DELETE method is used to delete resources.
In Laravel, when using form submission, the default request method is POST, for example:
<form action="/user" method="POST"> ????<input type="text" name="name"> ????<button type="submit">提交</button> </form>
Then, we use the store
method in the controller to handle this request :
public?function?store(Request?$request) { ????$user?=?new?User; ????$user->name?=?$request->input('name'); ????$user->save(); ????return?redirect('/user'); }
In the above code, we create a new User object, assign the name field submitted by the form to the name attribute of the User object, and then save the data and redirect to /user
page.
However, the above code sometimes has a problem: the newly added data cannot be edited. When we access the edit page, we will find that there is no originally created data information in the page. Why is this? We can first look at the code of the edit page:
<form action="/user/{{ $user->id?}}"?method="POST"> ????{{?method_field('PUT')?}} ????<input type="text" name="name" value="{{ $user->name?}}"> ????<button type="submit">提交</button> </form>
In this code, we use the method_field
method to specify the request method as PUT, because in the HTTP protocol, updating resources requires PUT method. However, in the Laravel framework, the default POST request cannot recognize the PUT request. Therefore, when accessing the edit page, Laravel will process it according to the default POST request instead of the PUT request we expect.
There are two ideas to solve this problem: one is to use the PUT request method to create data; the other is to use the _method
parameter to specify the request method when using the POST method to create data.
The first solution is a simpler method, but it requires more code changes. We need to use the PUT request method in the form:
<form action="/user/{{ $user->id?}}"?method="POST"> ????{{?method_field('PUT')?}} ????<input type="hidden" name="_token" value="{{ csrf_token() }}"> ????<input type="text" name="name" value="{{ $user->name?}}"> ????<button type="submit">提交</button> </form>
Then, handle the PUT request in the controller:
public?function?update(Request?$request,?$id) { ????$user?=?User::findOrFail($id); ????$user->name?=?$request->input('name'); ????$user->save(); ????return?redirect('/user'); }
Using this method, we need to specify the PUT method in the form, and A _token parameter needs to be passed to prevent CSRF attacks, which will increase a lot of code workload.
The second solution is much simpler. We need to use the POST method in the form, but add the _method parameter when submitting to specify the request method as PUT:
<form action="/user/{{ $user->id?}}"?method="POST"> ????<input type="hidden" name="_method" value="PUT"> ????<input type="hidden" name="_token" value="{{ csrf_token() }}"> ????<input type="text" name="name" value="{{ $user->name?}}"> ????<button type="submit">提交</button> </form>
Then, when processing the POST request in the controller, use method
Method to identify PUT requests:
public?function?update(Request?$request,?$id) { ????$user?=?User::findOrFail($id); ????$user->name?=?$request->input('name'); ????$user->save(); ????return?redirect('/user'); }
Using this method, we only need to add a _method parameter to the form, which is more readable and requires less code work.
In the process of developing Laravel projects, it is inevitable to encounter problems. Solving problems requires our patience and care, as well as an in-depth understanding and mastery of the framework and technology. I hope this article can provide some reference and help to readers.
The above is the detailed content of What's wrong with laravel's new addition and the inability to edit it?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

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

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

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

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

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

InLaravel,policiesorganizeauthorizationlogicformodelactions.1.Policiesareclasseswithmethodslikeview,create,update,anddeletethatreturntrueorfalsebasedonuserpermissions.2.Toregisterapolicy,mapthemodeltoitspolicyinthe$policiesarrayofAuthServiceProvider.

Yes,youcaninstallLaravelonanyoperatingsystembyfollowingthesesteps:1.InstallPHPandrequiredextensionslikembstring,openssl,andxmlusingtoolslikeXAMPPonWindows,HomebrewonmacOS,oraptonLinux;2.InstallComposer,usinganinstalleronWindowsorterminalcommandsonmac

The main role of the controller in Laravel is to process HTTP requests and return responses to keep the code neat and maintainable. By concentrating the relevant request logic into a class, the controller makes the routing file simpler, such as putting user profile display, editing and deletion operations in different methods of UserController. The creation of a controller can be implemented through the Artisan command phpartisanmake:controllerUserController, while the resource controller is generated using the --resource option, covering methods for standard CRUD operations. Then you need to bind the controller in the route, such as Route::get('/user/{id

Laravel allows custom authentication views and logic by overriding the default stub and controller. 1. To customize the authentication view, use the command phpartisanvendor:publish-tag=laravel-auth to copy the default Blade template to the resources/views/auth directory and modify it, such as adding the "Terms of Service" check box. 2. To modify the authentication logic, you need to adjust the methods in RegisterController, LoginController and ResetPasswordController, such as updating the validator() method to verify the added field, or rewriting r

Laravelprovidesrobusttoolsforvalidatingformdata.1.Basicvalidationcanbedoneusingthevalidate()methodincontrollers,ensuringfieldsmeetcriterialikerequired,maxlength,oruniquevalues.2.Forcomplexscenarios,formrequestsencapsulatevalidationlogicintodedicatedc

Selectingonlyneededcolumnsimprovesperformancebyreducingresourceusage.1.Fetchingallcolumnsincreasesmemory,network,andprocessingoverhead.2.Unnecessarydataretrievalpreventseffectiveindexuse,raisesdiskI/O,andslowsqueryexecution.3.Tooptimize,identifyrequi

InLaravelBladetemplates,use{{{...}}}todisplayrawHTML.Bladeescapescontentwithin{{...}}usinghtmlspecialchars()topreventXSSattacks.However,triplebracesbypassescaping,renderingHTMLas-is.Thisshouldbeusedsparinglyandonlywithfullytrusteddata.Acceptablecases

TomockdependencieseffectivelyinLaravel,usedependencyinjectionforservices,shouldReceive()forfacades,andMockeryforcomplexcases.1.Forinjectedservices,use$this->instance()toreplacetherealclasswithamock.2.ForfacadeslikeMailorCache,useshouldReceive()tod
