Configuration File (appdata.inc.php)

The file appdata.inc.php at this moment still is a kind of mixture of functional code and configuration options. Here, we just explain few lines of code with relevant configuration options. Since version 5.3, relevant configuration options are part of an administration interface: Configuration
Important: Do never touch this file without being sure about what you are doing. Changes might lead to misfunction of conceptcms.

In your installtion, you find the file under the following path:

./includes/appdata.inc.php

tmp Folder

Here you can set a different path for the tmp folder in your installation:

    //set CMS temp folder
    //the cms installer will replace the single quotes, too
    $path2TempFolderByInstaller = '~cms_tmp_dir~';
    if(   ($path2TempFolderByInstaller != $GLOBALS['CMSApplicationPath'].'tmp/')
       && (  !is_dir($path2TempFolderByInstaller)
          || !is_writable($path2TempFolderByInstaller)
          )
      ){
        define('PATH_TMP_FOLDER',               $GLOBALS['CMSApplicationPath'].'tmp/');
    }else{
        define('PATH_TMP_FOLDER',               $path2TempFolderByInstaller);
    }

Different Path for External Programs

Here, the path for some external programs is configured (usually, no change should be required): 

//---------------------------------------------
    //set absolute paths to external progs
    //---------------------------------------------
    define ('PATH_2_USER_CONFIG_FILE',   $GLOBALS['CMSApplicationPath'].'cms_user_config.php');
    if(file_exists(PATH_2_USER_CONFIG_FILE) && is_readable(PATH_2_USER_CONFIG_FILE)){
        include_once(PATH_2_USER_CONFIG_FILE);
    }else{
        $progUserConfigList = array();
    }
    define ('CPGS_PROG_TAR',         (isset($progUserConfigList['tar']) ? $progUserConfigList['tar'] : '/bin/tar'));
    define ('CPGS_PROG_CONVERT',     (isset($progUserConfigList['convert']) ? $progUserConfigList['convert'] : '/usr/bin/convert'));
    define ('CPGS_PROG_IDENTIFY',    (isset($progUserConfigList['identify']) ? $progUserConfigList['identify'] : '/usr/bin/identify'));
    define ('CPGS_PROG_PHP',         (isset($progUserConfigList['php']) ? $progUserConfigList['php'] : '/usr/bin/php'));
    define ('CPGS_PROG_PHPCONFIG',   (isset($progUserConfigList['phpconfig']) ? $progUserConfigList['phpconfig'] : '/etc/php5/apache2/php.ini'));
       
    unset($progUserConfigList);

Automatic Update Checker

By default, the system checks for updates; you can deactivate this here (0 is deactivated):

    define('CPGS_SYS_ENABLE_UPDATE_CHECKING', 1);

SSL Port

Here you can change the SSL port (should usually never be required):

            //SSL Configuration
            'SSL_PORT'          =>  443,

Session Duration

Here you can define the duration of a session in seconds. Default is 18000 seconds (=5 hours).

//define the expiration time of the sessions created with UM lib
    'sysExpirationTime'     => 18000,

CON-API Access Data

If you use conceptcms as Content Server (CON-API, see CON-API (Content Server)), you need to set some parameters here:

    // ----------------------------------------------------
    // auth server system access
    // ----------------------------------------------------
    "auth_sys_id"           => "~cms_auth_sys_id~",
    "auth_sys_pass"         => "~cms_auth_sys_pass~",
    "auth_app_label"        => "as_cm20",
   
    // ----------------------------------------------------
    // auth server applink variables name
    // ----------------------------------------------------
    "auth_sid_var"  => "aus_id",

Configuration of Indexed Search and Document Indexing

Here you define the time mfor the daily document indexing. In addition, you can define the configuration for search result relevance.

    // ------------------------------------
    // DOCIDX configuration
    // enter a list of hours to run the indexing process
    // format: 10.30,22.30
    // ------------------------------------
    'docidx_config' => array(
                    //comma separated value, 18.48,19.35
                    'runIndexingAt'    =>  '23.00',
                    'weightRules'      => array(
                        'title' =>    20, 
                        'h1'    =>    10,
                        'h2'    =>    5,
                        'h3'    =>    4,
                        'h4'    =>    3,
                        'h5'    =>    2
                    )
    ),

Relevance works based on styles for an element and frequency of occurance. Using styles to distinguish relevance makes sense, as modern Websites anyway use elements like <title>, <h1>, <h2> not only for design purposes, but also for search engine optimisation. You can add new elements and can change the weight.

The default configuration is explained as follows: If a search keyword is found within a  <title> of a document, it has a weight of 20. Does it appear within <h1>, weight is 10. Formatting with <h2> results in a weight of 5, etc. Occurance without any of the formattings mentioned results in a weight of 1.

Every occurance is multiplied with the weight. If a keyword appears two times within <title>, as a reult the weight will be 2 x 20 = 40. Three occurances without defined formatting would result in a weight of 3 x 1 = 3.

Important Note: Content not displayed on the Website (CE is not part of the HTML Template of the respective document) is not covered by the indexed search, as it is not part of the published document. If this is a problem, you might want to include the content (CE) into the template via an invisible DIV.

YAML Configuration

Here you can define whether YAML integration is active (only relevant if YAML has been installed) and can modify the YAML-path and the link to YAML-Builder.

    // ------------------------------------
    // YAML configuration
    // ------------------------------------
    'yaml_config'   =>  array(
                    'enable'        =>  1,
                    'builderUrl'    =>  'http://builder.yaml.de/',
                    'imagesPath'    =>  './external/yaml/v_3.0.5/',

Note: This configuration has been moved to the file cm_defines.inc.php in version 5.1. This is the reason why it is not available in the new configuration interface (version 5.3).

 

Cache-Configuration

Here you can enable/disable the cache; default is that the cache is enabled (enable = 1). In addition, you could define a text that should be displayed in "debugging" mode if a document is delivered from the cache.

    // ------------------------------------
    // Cache configuration
    // ------------------------------------
    'cache_config' => array(
    'enable'       =>  1,  
    'debugCode'    =>  '<h1>this is a cached copy</h1>',                   
                    ),