Consider the following example:
$config = $clq→resolve(‘Config’);
$dgcfg = $config→stdModel(‘datagrid’, ‘dbcollection’, ‘string’);
Datagrid is a Service. You would expect to find a Record in the list of Services which contained the following data:
; Datagrid.Cfg - Standard Config file for a Gijgo Data Grid
primaryKey = 'id'
uiLibrary = 'bootstrap4'
iconsLibrary = 'fontawesome'
headerFilter = 'true'
fontSize = '14px'
notFoundText = '144:No records available'
limit = 15
rightControls = false
sizes = [10,15,20]
icon = 'pencil'
formid = 'columnform'
icon = 'eye'
formid = 'columnform'
icon = 'trash'
The Gijgo datagrid has default options for primaryKey and uiLibrary which need to be updated / overwritten from data sent by the Server.
As will be observed in the next section, the values for “primaryKey” and “uiLibrary” are not overwritten by entries in Collections or Models, thus these entries will be utilized. The same is also true for the rowicons.. However it is not unusual to see the entries for “pager” overwritten by the Model.
In the Administration system (henceforth referred to as “Admin”) you will observe in the left hand menu system, an itm heading entitled Structure and within that submenu, an entry entitled Services. Clicking on the entry will display a list of the services currently recorded in the system. Currently there are about 20 services available for a Production version of Cliqon. As explained previously, these master service configuration files cover every area including Admin display facilities such as the Datagrid or the Datatree, administrative menus and other administrative facilities such as the Sitemap or Siteupdate.
The datagrid for Services includes all the facilities to create a new configuration record or edit an existing one. As was explained previously the Admin system can accept Service records as plain text files with a .cfg extension which, when used, are located in /admin/config subdirectory.
When you are augmenting a Cliqon system, it is entirely possible to work with a configuration file and when you have completely tested the result, copy the contents of the file to a Service record.
When you create or edit a Service record, you will notice that the value of ‘Reference’ and the file name should be the same. Thus the database record with reference “Sitemap” would be found on the file system in /admin/config as sitemap.cfg.
When you open a configuration file or a configuration record, you will notice that the content is in plain text TOML format. We provide an administrative facility to maintain and edit files in the file system. The form for Service records (and others of a similar format) provides an instance of Codemirror to assist with the editing of the record. As a matter of note, the form preview facility converts the content of the Configuration field into an array before displaying the result. This is a useful tip to ensure that the generated array is as you would wish it to be.
As another matter of note, the User Access Control Level system can be amended to hide individual entries or an entire submenu from some administration operators. Therefore any fears that providing unauthorised or untrained operators access to these structurally sensitive files, should be allayed.
As Services are fundamental to the operation of the system and the ability to access the database versions of the configuration records is central to being able to maintain any of the content of a system, you are reminded of the process of recovery.
Irrespective of the direction of record maintenance – you create database records from edited files or vice versa – the solution to any requirement for recovery is to use a raw database management facility such as a copy of Adminer, that we provide with the Cliqon system. All administrative records such as Service will be found in the Table “dbcollection” and in the case of “Service”, have a type (c_type) value of “service”. You can either amend the value portion of the record (c_common) or delete it, flush the cache and re-enter the data in Cliqon. Alternatively you might just delete the erroneous record and use the file system until the problem is resolved.
Created with the Personal Edition of HelpNDoc: Easily create CHM Help documents