Site configuration variables (meta)

Thursday 7 October 2004 by Mathieu

Variables which are configurable by the site administrator:

- default_language: Default language of the site (users can later personalise it individually).

- site_name: Name of the site (ex: Organisation Foo, default is "My Legal Case Management")

- site_description: Short description of the site (shown under the site_name). By default: "for not-for-profit organisations".

- email_sysadmin: E-mail of the main site administrator.

- case_default_read: If a case has "public=read", then other non-admin users can view the case information. Should this be suggested by default? Values: "yes", "no".

- case_read_always: Can non-admin users change the default read setting? Values: "yes", "no". Note that administrators can still change the read setting. This is useful if a site has a global policy to enforce "always public or always private", but where there can be exceptions in specific cases.

- case_default_write: If a case has "public=write", then other non-admin users can post new follow-up information to the case. Should this be suggested by default? Values: "yes", "no".

- case_write_always: Can non-admin users change the default write setting? Values: "yes", "no". Note that administrators can still change the write setting. This is useful if a site has a global policy to enforce "always public or always private", but where there can be exceptions in specific cases.

- site_open_subscription: Anyone can request a new account to the site. Values are "yes", "no", "moderated". With "moderated", subscription requests are sent to the administrator. This option is not a core feature. It aims to facilitate large "open" organisations working via the web.

  • [2004/10/22] We decided to implement this asap because it will facilitate testing.

- currency: Type of currency used by the authors (for billing).

- client_middle_name: Show the field to enter an author’s middle name? (Varies from country to country) Values: yes/no. Default: Depends on language at installation, bulgarian = yes, english = no. implementation not completed - matt

- client_citizen_number: Show the field to enter an author’s citizen ID? (Again varies from country to country, and might be illegal to ask in most circumstances). Values: yes/no. Default: no.

- case_court_archive: Show the field to enter a court archive ID for the case? (Depends on office activities). Values: yes/no. Default: yes.

- case_assignment_date: Show the assignment date for a cae? (Depends on office activities). Values: yes/no. Default: yes.

- case_allow_modif: Are authors of a case allowed to modify their case once it is created (this excludes to add follow-ups)? The possibility to modify case info is the risk of breaking the integrity of the data. The advantage is the right to make corrections. Values: yes/no. Default: yes.

- fu_sum_billed: Show the "sum billed" field for each follow-up? This depends on the office activites. Values: yes/no. Default: yes.

- fu_allow_modif: See case_allow_modif, but in this case it allows the author to correct/alter existing follow-ups. Default: yes.

- hide_emails: If yes, hides author e-mails to other non-admin authors. Default: no.


Non-user-configurable variables:

Of course, they could be configurable, but it would be a mess.

- charset: Character set of data stored in database and used in HTML. Default: UTF-8/Unicode.

- version_lcm: Current version of the installed software. Not really used, mostly informative. Perhaps not even updated.

- lcm_db_version: Current version of the structure of the database of the software. Every modification increases the version by 1. This triggers the upgrade mecanism.


Accessing and modifying variables

— -

Meta information are initialised at installation using the values in inc_meta_defaults.php. It is also called everytime the database structure is upgraded. If a meta already exists, it is not modified.

To send a message Private area xml ?