Technical Documentation

IDCategoryReq.Element Action
408integerno$zz['fields'][n]['factor'] factor for avoiding doubles as database fields

Relations: number

Show
11string: fieldyes$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
994integerno$zz['fields'][n]['field_sequence'] If you like a different order of your fields than the order in the definition file, you can set a sequence here. It is even possible to mix the main table and subtables if form_display for the subtable is set to 'lines'Show
621arrayno$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
364arrayno$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_select]" as well, this refers to a field "select_id" with an associated sql-query and returns the value of the "field_name_from_select" of the query instead. Values from subtables will have a table_name. or table. prefix. first value is chosen if more than one (more than one record not recommended!). {0,4} or {4} ... will call a substr()-function to return just a part of the field value if identifier must not be changed after set, include field_name of identifier in list Show
172string: fieldno$zz['fields'][n]['fields'][n]['detail_key'] inserts in field id_field from different detail_recordShow
847booleanno$zz['fields'][n]['for_action_ignore'] field will be ignored when action is determined

Relations: $zz['fields'][n]['def_val_ignore']

Show
429string: fieldno$zz['fields'][n]['foreign_key_field_name'] Normally, zzform uses maintable.id_field as WHERE maintable.id_field = id_value for subtables. This variable allows to set a different key_field_name, e. g. if you use table aliases

Relations: subtable

Show
198stringno$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
35string: functionno$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
976integerno$zz['fields'][n]['formatting_spaces'] sets numbers of maximal spaces that are allowed; on saving a record, all spaces are removedShow
399string: functionno$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'] $field_name = $zz['fields'][n]['field_name']

Relations: hidden

Show
810stringno$zz['fields'][n]['geo_display_behind'] will display coordinate behind coordinate field, possible values are dec, dms, deg, dm

Relations: number

Show
811stringno$zz['fields'][n]['geo_format'] output of coordinate, possible values are dec, dms, deg, dm

Relations: number

Show
928stringno$zz['fields'][n]['geocode_default'] default Value used for geocoding, if no value is transmitted via record

Relations: $zz['fields'][n]['geocode']

Show
982arrayno$zz['fields'][n]['geocode_ignore_if'] ignore a record if another field in the same record has value x

Relations: $zz['fields'][n]['geocode']

Show
989booleanno$zz['fields'][n]['geocode_ignore_update'] if set to true, changes in this field are ignored if a record is updated for the determination if a new geocoding shall take place

Relations: $zz['fields'][n]['geocode']

Show
924string: SQLno$zz['fields'][n]['geocode_sql'] SQL query to replace ID value for geocoding with real content

Relations: $zz['fields'][n]['geocode']

Show
923stringno$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 startedShow
978mixedno$zz['fields'][n]['group_dependent_tables'] string with one or array of table names for tables that are directly dependent on field content (foreign key, another table joined) if this table is in sort order before the immediate foreign table

Relations: $zz['fields'][n]['group_in_list']

Show

348 records total

in