|
filter_input_array
Gets multiple variables from outside PHP and optionally filters them
(PHP 5 >= 5.2.0, PECL filter:0.11.0)
Example 674. A filter_input_array() example<?php The above example will output: array(6) { Code Examples / Notes » filter_input_arraydarren craine
Your example code does not work. According to this page http://us.php.net/manual/en/ref.filter.php#filter.intro FILTER_FLAG_SCALAR and FILTER_FLAG_ARRAY dont exist. If you replace them with FILTER_REQUIRE_SCALAR and FILTER_REQUIRE_ARRAY (or FILTER_FORCE_ARRAY if you want to just force it) then your example will execute. .daRRen. phpnotes dot 20 dot zsh
The above example will actually output "NULL" because of the undefined variable doesnotexist - see http://bugs.php.net/bug.php?id=42608.
iam4webwork
The above example raises other questions such as how one would validate an html array. In the input form each input tag that refers to an html array would be named for example testarray[]. However, after the form is submitted, the syntax for validating the values is different from the expected $_POST['testarray[]']. Instead one has to drop the braces and validate as follows, assuming that testarray[] is supposed to be an html array of numerical values: Valid test: echo '*'; echo filter_input( INPUT_POST, 'testarray', FILTER_VALIDATE_INT, FILTER_REQUIRE_ARRAY ); echo '*'; But the following is an invalid test that results in 2 consequtive asterisks only! echo '*'; echo filter_input(INPUT_POST, 'testarray[]', FILTER_VALIDATE_INT, FILTER_REQUIRE_ARRAY ); echo '*'; So, there is a naming inconsistency going on, as after the form is submitted, one has to forget about the original name of the submitted array by dropping its braces. Maybe when the PECL/Filter extension is reviewed again, the great ones might consider making the syntax a little more forgiving. sinured
extract() is a very convenient way of copying all those variables to the local scope. (see http://www.php.net/extract)
|