3 you need to make use of the submit button: the rest of your code looks good (except the spaces), the action field holds the url to the desired server resource, which takes the data for further processing. – Imperative Apr 16 ’13 at 11:41 ,This can be done with an input element of a type «submit». This will appear as a button to the user and clicking the button will send the form.,I typically use this when my form is too long and I want a submit button at the beginning and also at the end of the page.,No control can be submitted without a name, and the content of a button element is the label, not the value.
No control can be submitted without a name, and the content of a button element is the label, not the value.
Answer by Jace Vu
The formmethod attribute specifies which HTTP method to use when sending the form-data. This attribute overrides the form’s method attribute.,The formmethod attribute is only used for buttons with type=»submit».,The numbers in the table specify the first browser version that fully supports the attribute.,The form-data can be sent as URL variables (with method=»get») or as HTTP post (with method=»post»).
The formmethod attribute specifies which HTTP method to use when sending the form-data. This attribute overrides the form’s method attribute.
Definition and Usage
The formmethod attribute specifies which HTTP method to use when sending the form-data. This attribute overrides the form’s method attribute.
Answer by Tru Gillespie
We can open up the reply.blade.php partial view we had already created during this tutorial series. In it, let’s modify the html markup so that it resembles what we have in this code snippet shown below. This should give us a decent looking html button we can use to submit a POST request to trigger the favorite feature.,When an html form submits a request, we don’t want the flow of the page to just stop once it completes. We should perform a redirect for the user, to give a better experience. Laravel provides the convenient back() helper function to allow this. We’ll place a call to that helper function in the controller like so:,In the prior tutorial, we did a lot of work to set up a test and the supporting code to make sure that a user could only submit a favorite for a reply one time. This was done at both the database level, and the PHP level. With our example logged in user, we can click away like a madman – but you can see the favorite count does not increment. This is very good. ,Therefore, the string contained in the action attribute will be as follows:
We can open up the reply.blade.php partial view we had already created during this tutorial series. In it, let’s modify the html markup so that it resembles what we have in this code snippet shown below. This should give us a decent looking html button we can use to submit a POST request to trigger the favorite feature.
owner->name>> said created_at->diffForHumans() >>
>
The method attribute is already set. This determines what type of http verb is used for the request to be sent. The POST http verb has already been selected. We need to fill out that action attribute as well. The action attribute is what determines where the request will be sent to. In our case we want to send that request to this route defined in the routes file.
Therefore, the string contained in the action attribute will be as follows:
The last thing we want to make sure to include in the button and form markup, is a call to the csrf_field() helper function. This will make the form more secure and protect against Cross-Site Request Forgery attacks. The final markup for our partial view with the csrf_field highlighted is shown here:
owner->name>> said created_at->diffForHumans() >>
>
When an html form submits a request, we don’t want the flow of the page to just stop once it completes. We should perform a redirect for the user, to give a better experience. Laravel provides the convenient back() helper function to allow this. We’ll place a call to that helper function in the controller like so:
middleware('auth'); > public function store(Reply $reply) < $reply->favorite(); return back(); > >
The user of the site should definitely be able to see the number of favorites assigned to each reply. We will need to modify the view file to display this to the user. In reply.blade.php, we can make a call to the relationships we have defined in our Model to display the count of favorites. We can once again make use of that very useful str_plural() helper function.
Bootstrap provides a nice class to disable a button in the user interface. Why not use this feature here? It makes perfect sense. If a user has already submitted a favorite for a particular reply, then we can apply the .disabled class to the button. That way the user can not even try to keep clicking multiple times. To do this, we will need to set up a new method we can call to check and see if the reply already has a favorite. Here is how we want the api to work, we can then add the code in the Model to facilitate this.
Now we need to add the method to the Reply Model.
belongsTo(User::class, 'user_id'); > public function favorites() < return $this->morphMany(Favorite::class, 'favorited'); > public function favorite() < $attributes = ['user_id' =>auth()->id()]; if (!$this->favorites()->where($attributes)->exists()) < return $this->favorites()->create($attributes); > > public function isFavorited() < return $this->favorites()->where('user_id', auth()->id())->exists(); > >
Answer by Lylah Arnold
Either, use an , instead of that button.,or, Use a bit of javascript, to get a hold of form object (using name or id), and call submit(..) on it. Eg: form.submit(). Attach this code to the button click event. This will serialise the form parameters and execute a GET or POST request as specified in the form’s method attribute.,I want a submit type button to send a POST request.,This can be done with an input element of a type «submit». This will appear as a button to the user and clicking the button will send the form.
I am thinking about something like this:
Answer by Brianna Parrish
An HTML form on a web page is nothing more than a convenient user-friendly way to configure an HTTP request to send data to a server. This enables the user to provide information to be delivered in the HTTP request.,Note: Servers can be configured with a size limit for files and HTTP requests in order to prevent abuse.,The element defines how the data will be sent. All of its attributes are designed to let you configure the request to be sent when a user hits a submit button. The two most important attributes are action and method.,The method attribute defines how data is sent. The HTTP protocol provides several ways to perform a request; HTML form data can be transmitted via a number of different methods, the most common being the GET method and the POST method
The following example expands a previous example, but creates submit and reset buttons with BUTTON instead of INPUT. The buttons contain images by way of the IMG element.,The layout of the form (given by the contents of the element).,The control type defined by the INPUT element depends on the value of the type attribute:,The INPUT element Control types created with INPUT Examples of forms containing INPUT controls
Here’s a simple form that includes labels, radio buttons, and push buttons (reset the form or submit it):
Last name: email: Male Female
Answer by Aurora Morton
If we change the method attribute of the HTML form in the example we saw earlier to POST, the HTTP request made to submit the form will use the POST method and put the query string in the body of the request, rather than adding it to the URL.,A button with a type attribute of submit will, when pressed, cause the form to be submitted. Pressing enter when a form field is focused has the same effect.,When the element’s method attribute is GET (or is omitted), the information in the form is added to the end of the action URL as a query string. The browser might make a request to this URL:,This code describes a form with two fields: a small one asking for a name and a larger one to write a message in. When you click the Send button, the form is submitted, meaning that the content of its field is packed into an HTTP request and the browser navigates to the result of that request.
If you type eloquentjavascript.net/18_http.html into your browser’s address bar, the browser first looks up the address of the server associated with eloquentjavascript.net and tries to open a TCP connection to it on port 80, the default port for HTTP traffic. If the server exists and accepts the connection, the browser might send something like this:
GET /18_http.html HTTP/1.1 Host: eloquentjavascript.net User-Agent: Your browser's name
Then the server responds, through that same connection.
HTTP/1.1 200 OK Content-Length: 65585 Content-Type: text/html Last-Modified: Mon, 08 Jan 2018 10:29:45 GMT . the rest of the document
The information sent by the client is called the request. It starts with this line:
The server’s response will start with a version as well, followed by the status of the response, first as a three-digit status code and then as a human-readable string.
The first line of a request or response may be followed by any number of headers. These are lines in the form name: value that specify extra information about the request or response. These headers were part of the example response:
A form with two submit buttons. The first submit button submits the form data with method=»get», and the second submits the form data with method=»post»:
Definition and Usage
The formmethod attribute specifies which HTTP method to use when sending the form-data. This attribute overrides the form’s method attribute.
The formmethod attribute is only used for buttons with type=»submit» .
The form-data can be sent as URL variables (with method=»get» ) or as HTTP post (with method=»post» ).
it appends the form-data to the URL in name/value pairs
it is useful for form submissions where a user want to bookmark the result
There is a limit to how much data you can place in a URL (varies between browsers), therefore, you cannot be sure that all of the form-data will be correctly transferred
Never use the «get» method to pass sensitive information! (password or other sensitive information will be visible in the browser’s address bar)
it sends the form-data as an HTTP post transaction
Form submissions with the «post» method cannot be bookmarked
it is more robust and secure than «get»
it does not have size limitations
Browser Support
The numbers in the table specify the first browser version that fully supports the attribute.
Attribute
formmethod
9.0
10.0
4.0
5.1
15.0
Syntax
Attribute Values
Value
Description
get
Appends the form-data to the URL: URL?name=value&name=value