Hu: In order to transfer # data from our HTML-form, into the db, we need a transient | variable<Turing>, that is declared in our dash-edit.php file; we will assign the value of the data in the form # to this variable, in the PHPxHTML-form portion, then update the db-table, with this variable.
W3Schools<a-r>: The PHP superglobals $_GET and $_POST are used to collect form-data. Both GET and POST create an array (e.g. array( key1 => value1, key2 => value2, key3 => value3, …)). This array holds key/value | pairs, where keys are the names of the form controls and values are the input data from the user. Both GET and POST are treated as $_GET and $_POST. These are superglobals, which means that they are always accessible, regardless of scope – and you can access them from any function, class or file without having to do anything special. $_GET is an array of variables passed to the current script via the URL parameters. $_POST is an array of variables passed to the current script via the HTTP POST method.
W3Schools<a-r>: Information sent from a form with the POST method is invisible to others (all names/values are embedded within the body of the HTTP request) and has no | limits on the amount of information to send. Developers prefer POST for sending form data.
Hu: Since the post | request<WP.MIC-H2S10> is triggered from our HTML file, and the dash-edit.php, never displayed to the end | user, we can consider this php-file to be running in the background #
H3S1: PHP form validation:
H3S2: Client-side form validation:
Hu: We will use some combination of # client-side, HTML form validation and server-side, PHP validation to ensure that form.submitted-content is in the correct format, for the db, and mitigates the risk of any security attacks #
Hu: The maxlength input-line param will stop the form entry, by disallowing further kb-strokes, after the user has entered the 12th | character with no error | message by default.
https://www.w3schools.com/php/php_forms.asp: has 5 pages.