Form validation: Difference between revisions

From Joomla! Documentation

MATsxm (talk | contribs)
m Marked for translation
Cmb (talk | contribs)
Some markup changes.
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<noinclude><languages /></noinclude>
<noinclude><languages /></noinclude>
<translate>Joomla has client-side and server-side form validation capabilities.<br/>
<translate><!--T:1-->
Server side validation is the minimum since everything before that can be overridden on the user side. But client-side is the most user-friendly one, so using both is not a bad idea (especially since the latter is unobtrusive and won't give problems on javascript-disabled or -problematic client browsers).</translate>
Joomla has client-side and server-side form validation capabilities.


<translate>==Client-side validation==</translate>
Server side validation is essential since everything before that can be overridden on the user side by hackers. However client-side is the most user-friendly validation, so using both is considered best practice.</translate>
<translate>.. is done via javascript while the user is filling in the form fields.<br/>
It uses the HTML '''classes''' <u>required</u> and <u>validate-[xxx]</u> (with [xxx] being a joomla or custom rule; e.g. validate-numeric)</translate>


<translate>More here: [[S:MyLanguage/Client-side form validation|Client-side form validation]]</translate>
<translate>==Client-side Validation== <!--T:2--></translate>
<translate><!--T:3-->
...is done via JavaScript while the user is filling in the form fields.


<translate>==Server-side validation==</translate>
It uses the HTML classes ''required''' and ''validate-[xxx]'' (with ''[xxx]'' being a Joomla or custom rule; e.g. validate-numeric)</translate>
<translate>.. is done after having submitted the form and will normally return to the form when not validated with some extra messages. <br/>
It used the HTML '''attributes''' <u>required</u> ("true" or "required") and <u>validate</u> (with value being a joomla or custom rule; e.g. validate="email")</translate>


<translate>More here: [[S:MyLanguage/Server-side form validation|Server-side form validation]]</translate>
<translate><!--T:4-->
More here: [[S:MyLanguage/Client-side form validation|Client-side form validation]]</translate>
 
<translate>==Server-side validation== <!--T:5--></translate>
<translate><!--T:6-->
...is done after having submitted the form and will normally return to the form when not validated with some extra messages.
 
It uses the HTML ''attributes'' ''required'' ("true" or "required") and ''validate'' (with the value being a Joomla or custom rule, e.g. ''validate="email"'')</translate>
 
<translate><!--T:7-->
More here: [[S:MyLanguage/J3.x:Server-side form validation|Server-side form validation]]</translate>


<noinclude>
<noinclude>
<translate>
<translate>
<!--T:8-->
[[Category:Form fields]]
[[Category:Form fields]]
[[Category:Development]]
[[Category:Development]]
</translate>
</translate>
</noinclude>
</noinclude>

Latest revision as of 23:35, 9 November 2022

Joomla has client-side and server-side form validation capabilities.

Server side validation is essential since everything before that can be overridden on the user side by hackers. However client-side is the most user-friendly validation, so using both is considered best practice.

Client-side Validation

...is done via JavaScript while the user is filling in the form fields.

It uses the HTML classes required' and validate-[xxx] (with [xxx] being a Joomla or custom rule; e.g. validate-numeric)

More here: Client-side form validation

Server-side validation

...is done after having submitted the form and will normally return to the form when not validated with some extra messages.

It uses the HTML attributes required ("true" or "required") and validate (with the value being a Joomla or custom rule, e.g. validate="email")

More here: Server-side form validation