Technical Documentation
ID | Category | Req. | Element | Action |
---|---|---|---|---|
408 | integer | no | $zz['fields'][n]['factor'] factor for avoiding doubles as database fields Relations: number | Show |
11 | string: field | yes | $zz['fields'][n]['field_name'] Database field name; required, if field value shall be shown or changed in the output. Not all fields of a table have to be defined, the undefined fields will be ignored by the script. Relations: $zz['fields'][n] | Show |
994 | integer | no | $zz['fields'][n]['field_sequence | Show |
621 | array | no | $zz['fields'][n]['fielddefs'] In combination with 'values', 'fielddefs' allows to change some $zz['fields']-settings for individual detail records where values are preset.
The first numerical index of the field definition corresponds to the numerical index of the corresponding value, the second index corresponds to the field index that shall be changed. Relations: subtable; $zz['fields'][n]['values'] | Show |
364 | array | no | $zz['fields'][n]['fields'] List of fields which are used to create an identifier (`$zz['fields'][n]['type'] = 'identifier'`). If field_name of identifier-field is part of the array, the identifier won't be changed later on (write_once). Corresponding values of ID fields may be used writing `field_id[value]`. The fields are used in the same order as in the array.
vars which will be passed to function or identifier, might be in form like "select_id[field_name_from_selec | Show |
172 | string: field | no | $zz['fields'][n]['fields'][n]['d | Show |
847 | boolean | no | $zz['fields'][n]['for_action_ign Relations: $zz['fields'][n]['def_val_ignore'] | Show |
429 | string: field | no | $zz['fields'][n]['foreign_key_fi Relations: subtable | Show |
198 | string | no | $zz['fields'][n]['form_display'] - vertical (default vertical view as in standard form)
- horizontal: shows detail records in list view
- set: show detail records like set with radio buttons; works only with a detail table just with detail_table_id, foreign_key of main table and some other ID.
- inline: only works with 1 subrecord, show subfields as if they're part of the main record Relations: select; subtable | Show |
35 | string: function | no | $zz['fields'][n]['format'] Formats in form view text content of field with this markup language (e. g. Markdown), function of the same name must lie inside zzform-folder Relations: text; memo | Show |
976 | integer | no | $zz['fields'][n]['formatting_spa | Show |
399 | string: function | no | $zz['fields'][n]['function'] function which will be called to change input value
`function($vars, $field_name);`
$vars = POST vars of fields defined in an array in $zz['fields'][n]['fields']
$fie Relations: hidden | Show |
810 | string | no | $zz['fields'][n]['geo_display_be Relations: number | Show |
811 | string | no | $zz['fields'][n]['geo_format'] output of coordinate, possible values are dec, dms, deg, dm Relations: number | Show |
928 | string | no | $zz['fields'][n]['geocode_defaul Relations: $zz['fields'][n]['geocode'] | Show |
982 | array | no | $zz['fields'][n]['geocode_ignore Relations: $zz['fields'][n]['geocode'] | Show |
989 | boolean | no | $zz['fields'][n]['geocode_ignore Relations: $zz['fields'][n]['geocode'] | Show |
924 | string: SQL | no | $zz['fields'][n]['geocode_sql'] SQL query to replace ID value for geocoding with real content Relations: $zz['fields'][n]['geocode'] | Show |
923 | string | no | $zz['fields'][n]['geocode'] Mark fields for geocoding: 'postal_code', 'country', 'street', 'street_number', 'locality', 'latitude', 'longitude', 'state', 'place' 'place' is somewhat special. It adds a possibility to add the name of the place or venue if the full address is not known. In case 'place' + the rest of the address yields no results, a second query without 'place' is started | Show |
978 | mixed | no | $zz['fields'][n]['group_dependen Relations: $zz['fields'][n]['group_in_list'] | Show |
348 records total