Search for forms
- Search 7.x for forms
- Search 9.5.x for forms
- Search 10.3.x for forms
- Search 11.x for forms
- Other projects
| Title | Object type | File name | Summary |
|---|---|---|---|
| FieldLayoutTest::testLayoutForms | function | core/ |
Tests layout plugins with forms. |
| FileModuleTest::testFileSaveUploadSingleErrorFormSize | function | core/ |
Tests file size upload errors. |
| FormAjaxException::$formState | property | core/ |
The form state. |
| FormAjaxException::getFormState | function | core/ |
Gets the form state. |
| FormBuilder::$formSubmitter | property | core/ |
The form submitter. |
| FormBuilderTest::formStateResponseProvider | function | core/ |
Provides test data for testHandleFormStateResponse(). |
| FormBuilderTest::testHandleFormStateResponse | function | core/ |
Tests the handling of FormStateInterface::$response. |
| FormCache::loadCachedFormState | function | core/ |
Loads the cached form state. |
| FormCacheTest::$formState | property | core/ |
|
| FormCacheTest::$formStateCacheStore | property | core/ |
The expirable key value store used by form state cache. |
| FormCacheTest::testLoadCachedFormState | function | core/ |
@covers ::loadCachedFormState |
| FormCacheTest::testLoadCachedFormStateWithFiles | function | core/ |
@covers ::loadCachedFormState |
| FormErrorHandler::setElementErrorsFromFormState | function | core/ |
Stores errors and a list of child element errors directly on each element. |
| FormErrorHandlerTest::testSetElementErrorsFromFormState | function | core/ |
@covers ::handleFormErrors @covers ::setElementErrorsFromFormState |
| FormState | class | core/ |
Stores information about the state of a form. |
| FormState.php | file | core/ |
|
| FormState::$always_process | property | core/ |
If TRUE and the method is GET, a form_id is not necessary. |
| FormState::$anyErrors | property | core/ |
Tracks if any errors have been set on any form. |
| FormState::$build_info | property | core/ |
An associative array of information stored by Form API that is necessary to build and rebuild the form from cache when the original context may no longer be available: |
| FormState::$buttons | property | core/ |
A list containing copies of all submit and button elements in the form. |
| FormState::$cache | property | core/ |
If set to TRUE the original, unprocessed form structure will be cached, which allows the entire form to be rebuilt from cache. A typical form workflow involves two page requests; first, a form is built and rendered for the user to fill in. Then, the… |
| FormState::$cleanValueKeys | property | core/ |
An associative array of form value keys to be removed by cleanValues(). |
| FormState::$complete_form | property | core/ |
The complete form structure. |
| FormState::$errors | property | core/ |
Contains errors for this form. |
| FormState::$executed | property | core/ |
If TRUE, the form was submitted and has been processed and executed. |
| FormState::$groups | property | core/ |
Contains references to details elements to render them within vertical tabs. |
| FormState::$has_file_element | property | core/ |
If TRUE, there is a file element and Form API will set the appropriate 'enctype' HTML attribute on the form. |
| FormState::$input | property | core/ |
The array of values as they were submitted by the user. |
| FormState::$invalidToken | property | core/ |
If set to TRUE the form will skip calling form element value callbacks, except for a select list of callbacks provided by Drupal core that are known to be safe. |
| FormState::$limit_validation_errors | property | core/ |
Stores which errors should be limited during validation. |
| FormState::$method | property | core/ |
The HTTP form method to use for finding the input for this form. |
| FormState::$must_validate | property | core/ |
Ordinarily, a form is only validated once, but there are times when a form is resubmitted internally and should be validated again. Setting this to TRUE will force that to happen. This is most likely to occur during Ajax operations. |
| FormState::$no_cache | property | core/ |
If set to TRUE the form will NOT be cached, even if 'cache' is set. |
| FormState::$no_redirect | property | core/ |
If set to TRUE the form will NOT perform a redirect, even if self::$redirect is set. |
| FormState::$process_input | property | core/ |
TRUE signifies correct form submission. This is always TRUE for programmed forms coming from \Drupal\Core\Form\FormBuilderInterface::submitForm() (see 'programmed' key), or if the form_id coming from the \Drupal::request()->request data… |
| FormState::$programmed | property | core/ |
If TRUE, the form was submitted programmatically, usually invoked via \Drupal\Core\Form\FormBuilderInterface::submitForm(). Defaults to FALSE. |
| FormState::$programmed_bypass_access_check | property | core/ |
If TRUE, programmatic form submissions are processed without taking #access into account. Set this to FALSE when submitting a form programmatically with values that may have been input by the user executing the current request; this will cause #access… |
| FormState::$rebuild | property | core/ |
Normally, after the entire form processing is completed and submit handlers have run, a form is considered to be done and \Drupal\Core\Form\FormSubmitterInterface::redirectForm() will redirect the user to a new page using a GET request (so a browser… |
| FormState::$rebuild_info | property | core/ |
Similar to self::$build_info, but pertaining to \Drupal\Core\Form\FormBuilderInterface::rebuildForm(). |
| FormState::$redirect | property | core/ |
Used to redirect the form on submission. |
| FormState::$requestMethod | property | core/ |
The HTTP method used by the request building or processing this form. |
| FormState::$response | property | core/ |
Used when a form needs to return some kind of a \Symfony\Component\HttpFoundation\Response object, e.g., a \Symfony\Component\HttpFoundation\BinaryFileResponse when triggering a file download. If you use self::setRedirect() or… |
| FormState::$storage | property | core/ |
This is not a special key, and no specific support is provided for it in the Form API. By tradition it was the location where application-specific data was stored for communication between the submit, validation, and form builder functions, especially… |
| FormState::$submitted | property | core/ |
If TRUE, the form has been submitted. Defaults to FALSE. |
| FormState::$submit_handlers | property | core/ |
Stores the gathered submission handlers. |
| FormState::$temporary | property | core/ |
Holds temporary data accessible during the current page request only. |
| FormState::$triggering_element | property | core/ |
The form element that triggered submission, which may or may not be a button (in the case of Ajax forms). This key is often used to distinguish between various buttons in a submit handler, and is also used in Ajax handlers. |
| FormState::$validate_handlers | property | core/ |
Stores the gathered validation handlers. |
| FormState::$validation_complete | property | core/ |
Tracks if the form has finished validation. |
| FormState::$values | property | core/ |
An associative array of values submitted to the form. |
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.