| verzia 1.10, 2002/12/14 04:37:56 |
verzia 1.11, 2002/12/31 00:12:24 |
|
|
| <!-- $Platon: phpMyEdit/doc/sgml/configuration.fields.sgml,v 1.9 2002/12/13 02:55:15 nepto Exp $ --> |
<!-- $Platon: phpMyEdit/doc/sgml/configuration.fields.sgml,v 1.10 2002/12/14 04:37:56 nepto Exp $ --> |
| |
|
| <!-- Categories: |
<!-- Categories: |
| |
|
| Riadok 378 values using <varname>['filters']</>, an |
|
| Riadok 378 values using <varname>['filters']</>, an |
|
| Additional values to table lookup could be stored in |
Additional values to table lookup could be stored in |
| <varname>['values2']</varname> array. The main difference between simple |
<varname>['values2']</varname> array. The main difference between simple |
| <varname>['values']</varname> usage is, that array keys will be stored into DB |
<varname>['values']</varname> usage is, that array keys will be stored into DB |
| and array values will be printed out in input section boxes. |
and array values will be printed out in input section boxes. This is especially |
| |
useful for MySQL enumerations when you do not want to print out enumeration |
| |
keys, but rather some more user-friendly texts. See example: |
| |
|
| |
<example><title>Input restriction using additional values</title> |
| |
<programlisting><![CDATA[ |
| |
$opts['fdd']['col_name']['values2'] = array( |
| |
'hidden' => 'Hidden Article', |
| |
'showed' => 'Showed Article', |
| |
'disabled' => 'Disabled Article', |
| |
'deleted' => 'Deleted Article' |
| |
); |
| |
]]></programlisting> |
| |
</example> |
| |
|
| </para> |
</para> |
| <para> |
<para> |
| |
|
| <!-- TODO: REMOVE ME! --> |
In the example above, keywords 'hidden', 'showed', 'disabled' and 'deleted' will be |
| Well, this need more clear description, but nobody except me understand how this |
stored in database, but user-friendly expressions will be showed in select box |
| works. :GRIN: -- Nepto |
for user. Usage of <varname>['values2']</> can be combined with |
| |
<varname>['values']</> usage. |
| |
|
| </para> |
</para> |
| </sect2> |
</sect2> |