{error:email}
{/if} // when inline error handling is enabled ### Password Member password. This is a **required** field. -{error:password}
{/if} // when inline error handling is enabled ### Password Confirmation Password confirmation. If a new password is submitted, the password confirmation field is **required** and must match the entered password. -{error:screen_name}
{/if} // when inline error handling is enabled ### Username @@ -121,6 +135,7 @@ Member username. This is a **required** field and must be unique across the site + {if error:username}{error:username}
{/if} // when inline error handling is enabled ### Custom field @@ -128,6 +143,10 @@ The custom profile fields can be displayed individually by addressing them using {field:birthday} +If inline error handling is enabled, you can use the `{error:field_name}` tag to display the error message for the field. + + {error:birthday} + ## Custom Profile Field Variable Pair All custom fields are output inside the ``{custom_profile_fields}`` variable tag pair. @@ -139,6 +158,8 @@ All custom fields are output inside the ``{custom_profile_fields}`` variable tag {form:custom_profile_field} + {if error}{error}{/if} + {/custom_profile_fields} @@ -189,6 +210,10 @@ Maximum length set for text fields Short name of the fieldtype used for field +#### `{error}` + +Error message for the field, if inline error handling is enabled. + ## Example {exp:member:edit_profile diff --git a/docs/member/forgot-password.md b/docs/member/forgot-password.md index be0bfe65e..2c6e817e2 100644 --- a/docs/member/forgot-password.md +++ b/docs/member/forgot-password.md @@ -55,6 +55,16 @@ This parameter allows you to define where the user will be returned after succes 1. Use the standard Template_Group/Template syntax to specify where to return the user. For instance, if you want the user to be returned to the "local" Template in the "news" Template Group, you would use: return="member/forgot-password/sent" 2. Use a full URL. For example: return="Auto-login on future visits
{/if} +### `{errors}...{error}...{/errors}` + +When inline errors enabled, displays all errors in a loop. Each individual error message is available as `{error}` variable within the loop. + +This variable pair is useful for displaying all errors at once, for example, in a fieldset at the top of the form. It can also be used as a conditional to check if there are any errors at all: `{if errors}`. ## Example diff --git a/docs/member/registration.md b/docs/member/registration.md index 4ce434879..c2df332d8 100644 --- a/docs/member/registration.md +++ b/docs/member/registration.md @@ -38,7 +38,13 @@ This parameter allows you to specify the primary role to assign the new member, ### `error_handling="inline"` error_handling="inline" -This parameter allows you to use inline errors in your registration form. The errors can be displayed using the `{error:field_name}` tag where `field_name` would need to be replaced with the name of the field that has an error, as used to compose the form. +This parameter allows you to use inline errors in your registration form. The errors can be displayed using the `{error:field_name}` tag where `field_name` would need to be replaced with the name of the field that has an error or using [`{errors}` variable pair](templates/globals/single-variables.md#error-variables). + +### `return_error=` + +When inline errors are enabled, this parameter allows you to specify the template to return to if there are errors in the form. The default is the same template that the form is on. + + return_error="member/error" ### `include_assets=` @@ -160,6 +166,10 @@ Shows the fully parsed custom member form field. Indicates whether the field is marked as required +#### `{error}` + +Error message for the field, if inline error handling is enabled. + ## Variables ### `{accept_terms}` @@ -207,6 +217,16 @@ This will show errors with the submitted password as well as password confirm. Displays the custom field input form for the given field (substitute `field_name` with the actual field name). Note that the field must be set as "visible on registration" in order to show up. +### `{error:field_name}` + +When inline errors enabled, displays the error message for the given field (substitute `field_name` with the actual field name). + +### `{errors}...{error}...{/errors}` + +When inline errors enabled, displays all errors in a loop. Each individual error message is available as `{error}` variable within the loop. + +This variable pair is useful for displaying all errors at once, for example, in a fieldset at the top of the form. It can also be used as a conditional to check if there are any errors at all: `{if errors}`. + ## Example {exp:member:registration_form @@ -214,7 +234,16 @@ Displays the custom field input form for the given field (substitute `field_name error_handling="inline" } -* Required fields
+ {if errors} + + {/if} + +* Required fields