Int the element info, there are some informations indicative only about the application, like its name, a description, the copyright, the creator name etc. Note that this element can be used also in module.xml files to identify a module. Here is an example:

<info id="testapp@jelix.org" name="testapp" createdate="2017-01-01">
    <version>1.0</version>
    <label lang="en_US">Testapp</label>
    <description lang="en_US">Application to test Jelix</description>
    <licence URL="http://www.gnu.org/licenses/gpl.html">GPL</licence>
    <copyright>2017 Laurent Jouanneau and other contributors</copyright>
    <creator name="Laurent Jouanneau" email="laurent@jelix.org"/>
    <contributor name="Superman" email="superman@superville.com"/>
    <homepageURL>http://jelix.org</homepageURL>
</info>

Only the <version> element and attributes id and name on <info> are required. Others are optionals.

The id attribute should be a unique identifiant. That's why it is recommanded to use an email as an identifiant (or a UUID but it is less readable).

The attribute name should be a "technical" name (the name of the directory of the application or of the module for instance). The label element can contain a displayable name.

The element <directories> should contain informations about dependencies of the application. For the moment, only the jelix version is required.

<dependencies>
     <jelix minversion="1.6.0" maxversion="1.6.*" />
</dependencies>

This element can be used in a module.xml file, and can contain additionnaly one or more <module> elements, which indicate modules that the installer should install in order to execute correctly the modules.

  <module name="testurls" minversion="2.2" maxversion="2.3" />
  <module name="jauthdb" />
  <module name="jacl2db" />

This element indicate paths of some directories. all elements in this example are required:

    <directories>
        <config>var/config</config>
        <log>var/log</log>
        <var>var</var>
        <www>www</www>
        <temp>../temp/testapp</temp>
    </directories>

The entrypoints element list all entry points of the application (in www/ or scripts/), with their configuration file and their type.

    <entrypoints>
        <entry file="index.php" config="index/config.ini.php" />
        <entry file="soap.php" config="soap/config.ini.php" type="soap"/>
        <entry file="jsonrpc.php" config="jsonrpc/config.ini.php" type="jsonrpc"/>
        <entry file="cmdline.php" config="cmdline/config.ini.php" type="cmdline"/>
    </entrypoints>

Usually its parameters are at the beginning of file. They define default or global values of the framework.

startModule = "jelix"
startAction = "default:index"
locale = "en_US"
charset = "UTF-8"
timeZone = "US/Pacific"

pluginsPath = lib:jelix-plugins/,app:plugins/
modulesPath = lib:jelix-modules/,app:modules/

theme = default
use_error_handler = on

Parameters in details :

• startModule, startAction : default module and action (generally re-defined for each response type. see preceding section)
• locale, charset : default language and encoding of responses
• timeZone : set the time zone for every date and time functions
• pluginsPath : path list to plugins. learn more in plugins documentation.
• theme : default selected theme. Read theme system description.
• use_error_handler : this option shoud stay on for Jelix to return useful and detailed errors or exceptions.

Contains the list of all used modules, and their access level

• 0 means the module is not used and must not be installed
• 1 means the module is used, but only by other modules (its daos, forms etc), but is not accessible directly from the web (so it has no controllers or existing controllers will never be called)
• 2 means the module is installed and usuable normally.

List all coordinator plugins Jelix has to activate. They will be loaded from the list of path defined by the pluginsPath option.

The example below demonstrates the activation of an authentication plugin. Its own set of options are defined in auth.coord.ini.php file. Learn more about authentication.

[coordplugins]
;plugin name = ini filename
auth = "auth.coord.ini.php"

this section allows to customize each response type and its alias. each line consists of a couple <response alias>=<response class>.

As for example, it is usual to overload html default response (jResponseHtml) by such a line : html=myhtmlresponse. Find more details in customizing common response

Below are the default alias and response types:

[responses]
html = jResponseHtml
redirect = jResponseRedirect
redirectUrl = jResponseRedirectUrl
binary = jResponseBinary
text = jResponseText
jsonrpc = jResponseJsonrpc
json = jResponseJson
xmlrpc = jResponseXmlrpc
xml = jResponseXml
zip = jResponseZip
rss2.0 = jResponseRss20
atom1.0 = jResponseAtom10
css= jResponseCss
tcpdf = jResponseTcpdf

Those parameters are used to configure notifications occuring during an application script execution. Details can be found in error manager documentation.

Notifications have different levels. Jelix defined levels corresponding to PHP error_reporting levels:

• default = selected level if no other level corresponds
• error = notify an error stopping a script execution
• warning = notifu an error which doesn't stop a script
• notice = notify a possible error
• deprecated = notify a deprecated function (php 5.3)
• strict = notify core PHP messages about compatibility and interoperability

Below are the whole list of parameters:

[error_handling]
messageLogFormat = "%date%\t%ip\t[%code%]\t%msg%\t%file%\t%line%\n"
logFile = error.log
email = root@localhost
emailHeaders = "Content-Type: text/plain; charset=UTF-8\nFrom: webmaster@yoursite.com\nX-Mailer: Jelix\nX-Priority: 1 (Highest)\n"
quietMessage="A technical error has occured. Sorry for this trouble."

showInFirebug = off

; keywords you can use : ECHO, ECHOQUIET, EXIT, LOGFILE, SYSLOG, MAIL, TRACE
default      = ECHO EXIT
error        = ECHO EXIT
warning      = ECHO
notice       = ECHO
deprecated   = ECHO
strict       = ECHO
; exceptions implicitly use EXIT
exception    = ECHO

• messageLogFormat and logFile configure a log file output (LOGFILE or SYSLOG)
• email et emailHeaders configure mail ouptut (MAIL)
• quietMessage defines a neutral message for user (ECHOQUIET)
• showInFirebug : if on, all notifications will be redirected to firebug extension of firefox browser using its console api.

The last set of options allows to associate ouptut formats to each level of notification. Each level can have more than one output format. For example, in production, you'll probably want to set :error = ECHOQUIET EXIT LOGFILE and so on.

Defines the template behavior of Jelix template engine. And more precisely of its compilation step. Find in-depth details in templates.

[compilation]
checkCacheFiletime  = on
force  = off

• checkCacheFiletime : if on template will be compiled if its file modification date is more recent than its already PHP compiled file.
• force : if on, template is systematically compiled

There is an option to globally disable zone caching. It is useful during development environment but should be set to off in production.

To disable zone caching :

[zones]
disableCache = on  // default to off

Defines how the url engine works.

[urlengine]
engine        = significant

enableParser = on
multiview = off

scriptNameServerVariable =
pathInfoInQueryParameter =

basePath = ""
jelixWWWPath = "jelix/"

defaultEntrypoint= index

simple_urlengine_https =

Details:

• engine : name of the used engine. Available engines are: simple, basic_significant and significant
• enableParser : activate the parsing of the url. Deactivate it if the url is parsed by the web server (with the mod_rewrite of Apache for exemple), and is given to Jelix as a simple url without pathinfo, like for the simple url engine.
• multiView : indicate if the ".php" part of the entrypoints name should be added or not into generated url. It is possible to activate it if the multiview option in Apache is activated or if there is a rewrite rule into the web server that adds the ".php".
• scriptNameServerVariable : the name of the variable into $_SERVER containing the script name. Example: for the url http://mysite.com/foo/index.php, it is the variable which contains "/foo/index.php". The name can be SCRIPT_NAME, ORIG_SCRIPT_NAME, PHP_SELF or REDIRECT_SCRIPT_URL. It is automatically detected by jelix, but in some server configuration, it may not work and you should indicate the variable name.
• pathInQueryParameter : if the webserver has some rewrite rules that move the pathinfo into a query parameter (like RewriteRule ^(.*)$ index.php/?jpathinfo=$1 [L,QSA]) then you must indicate the name of this query parameter into pathInfoInQueryParameter (here "jpathinfo").
• basePath : this parameter is the web path to your index.php. It is automatically detected, but some time the detection fails, and you should indicate it. For example, if the url of the index.php is http://foo.com/aaa/bbb/www/index.php, then you should indicate /aaa/bbb/www/. If the url is simply http://foo.com/index.php, then the base path is /.
• jelixWWWPath : contains the web path to the lib/jelix-www/ content. If you modify it, modify also path into the htmleditors, wikieditors, datepickers, jquery. See below.
• jqueryPath : contains the web path to the directory having jQuery/jQueryUI files of jelix (typically, web path to lib/jelix-www/jquery/). You can modify it, if you want to provide your own jQuery/jQueryUI files. But in this case, the content should have same filenames. However, jqueryPath is deprecated since Jelix 1.6.20, as there is a new way to define your own jQuery files. See the jquery section below.
• defaultEntrypoint : contains the default entrypoint name
• simple_urlengine_https : contains the list of actions that need HTTPS

notfound ¶

notfoundAct =