Install and setup     >     Configuration

config.xml

The config.xml file holds the default configuration of yeager. You should never alter this file as it might get overwritten when installing updates. Instead you can overwrite all of it's values by setting them in the server specific configuration file. 
 
In order to to activate the server specific configuration file you need to rename config-<IP/DOMAIN_POSTFIX>.xml.php and replace <IP/DOMAIN_POSTFIX> with either the IP address of the server or the domain the installation is running at.
 
All of these settings should be configured correctly by following the instructions from the installation section.
 
Following you will find an explanation of all relevant configuration settings:

Database connection

This section stores the database configuration which is used by yeager.
  1. <DB>
  2.     <DSN
  3.            id="yeager"
  4.            driver="mysql"
  5.            host="db_host_ip"
  6.            user="db_user_name"
  7.            password="db_password"
  8.            db="db_name"
  9.    />
  10. </DB>

Logging

The LOGGING block specifies log levels for various different logging methods. The log levels used for the logging config block correspond to PHP error levels:

Loglevel Constant PHP error level
1 ERROR E_ERROR
2 WARNING E_WARNING
3 LOG NONE
4 DEBUG E_STRICT

You can find an explanation of yeager's logging capabilities at Developer Guide: Logging and debugging.
  1. <LOGGING>
  2.     <BUCKETS>
  3.         <BUCKET TYPE="FILE" URI="[SYSTMP]/nas-[YEAR][MONTH][DAY].log" LEVEL="1" />
  4.         <BUCKET TYPE="PLUGIN" URI="Echo" LEVEL="0" />
  5.         <BUCKET TYPE="PLUGIN" URI="FireBug" LEVEL="1" />
  6.     </BUCKETS>
  7. </LOGGING>

Cache

This section specifies wether to use frontend caching or not. If set to true the cache configuration settings from the cache.xml will be used.
  1. <CACHE>
  2.     <FRONTEND>false</FRONTEND>
  3. </CACHE>

Directory path settings

This section is responsible for storing paths to the directories which are needed for YEAGER.
  1. <DIRECTORIES>
  2.     <DOCPATH>/yeager/</DOCPATH>
  3.     <USERPICDIR>../frontend/files/</USERPICDIR>
  4.     <UPDATES>updates/</UPDATES>
  5.     <FRONTEND>/frontend/templates/</FRONTEND>
  6.     <TEMPLATEPREVIEWDIR>../frontend/templates/previews/</TEMPLATEPREVIEWDIR>
  7.     <TEMPLATEDIR>../frontend/templates/</TEMPLATEDIR>
  8.     <TEMPLATEDOC>/frontend/templates/</TEMPLATEDOC>
  9.     <FILESDIR>../frontend/files/</FILESDIR>
  10.     <FILESDOC>/frontend/files/</FILESDOC>
  11.     <PROCESSORSDIR>../frontend/processors/</PROCESSORSDIR>
  12.     <EXTENSIONSDIR>../frontend/extensions/</EXTENSIONSDIR>
  13.     <EXTENSIONSDOC>/frontend/extensions/</EXTENSIONSDOC>
  14.     <WEBROOT>/</WEBROOT>
  15. </DIRECTORIES>  

Mailings

This section allows you to specify a custom SMTP server in case you do not wish to use sendmail for all E-Mails sent by yeager. The FORCE_RECIPIENT tag allows you to specify an E-Mail address which is, as its name suggests, forced as the recipient to every E-Mail sent through yeager. This is useful for testing personalized E-Mailings without having to set every users E-Mail address to the one you wish to test with.
  1. <MAILINGS>
  2.     <!--FORCE_RECIPIENT>test@example.com</FORCE_RECIPIENT-->
  3.     <!--SMTP>mail.example.com</SMTP-->
  4. </MAILINGS>

Reserved Site names

The RESERVED_SITENAMES tag specifies a comma seperated list of strings which are not allowed as Site names throughout the whole system.
  1. <RESERVED_SITENAMES>yeager,download,image</RESERVED_SITENAMES>

Page directories

The PAGEDIR block allows the specification of the default amount of items which are displayed on one page in yeager's administration panels which make use of a page directory.
  1. <PAGEDIR>
  2.     <DEFAULT_PER_PAGE>40</DEFAULT_PER_PAGE>
  3. </PAGEDIR>

Temp directory

TMP allows the configuration of a custom temp directory. If left empty yeager will use the temp directory configured via PHP.
  1. <PATH>
  2.         <TMP></TMP>
  3. </PATH>

Reference tracker

yeager's link tracker requires the INTERNALPREFIX value to include a relative path to yeager's PHP file.
  1. <REFTRACKER>
  2.       <INTERNALPREFIX>/POSSIBLE_SUBDIRECTORY/yeager/y.php/</INTERNALPREFIX>
  3. </REFTRACKER>

Embedded Content Block folder

This tag specifies which folder ID is used to store embedded contentblocks.
  1. <EMBEDDED_CBLOCKFOLDER>2</EMBEDDED_CBLOCKFOLDER>

System users

The SYSTEMUSERS block specifies the User and Usergroup IDs for the admin (root) & anonymous user accounts.
  1. <SYSTEMUSERS>
  2.     <ROOTUSERID>1</ROOTUSERID>
  3.     <ROOTGROUPID>1</ROOTGROUPID>
  4.     <ANONUSERID>2</ANONUSERID>
  5.     <ANONGROUPID>2</ANONGROUPID>
  6. </SYSTEMUSERS>

Timezones

This config block defines what timezones are used on your server and in the frontend by default.
  1. <TIMEZONES>
  2.     <SERVER>Europe/Berlin</SERVER>
  3.     <FRONTEND>Europe/Berlin</FRONTEND>
  4. </TIMEZONES>

UI synchronization

The GUISYNC tags specify a timeframe (in seconds) after which a GUI sync request is made (GUISYNC_INTERVAL) and how long it may take for this request to trigger a timeout (GUISYNC_TIMEOUT).
  1. <GUISYNC_INTERVAL>125</GUISYNC_INTERVAL>
  2. <GUISYNC_TIMEOUT>160</GUISYNC_TIMEOUT>

Object locks

The OBJECTLOCK tags specify a timeframe (in seconds) after which an object lock is requested or updated (OBJECTLOCK_INTERVAL) and how long it takes for an acquired object lock to get removed if the user has not actively navigated away from the locked object, e.g. the user refreshed the page with F5 or just closed his browser window (OBJECTLOCK_TIMEOUT).
  1. <OBJECTLOCK_TIMEOUT>120</OBJECTLOCK_TIMEOUT>
  2. <OBJECTRELOCK_INTERVAL>10</OBJECTRELOCK_INTERVAL>

Case sensitive URLs

The CASE_SENSITIVE_URLS tag specifies whether URLs generated by yeager will contain only lower case letters (0) or may also contain upper case letters (1).
  1. <CASE_SENSITIVE_URLS>0</CASE_SENSITIVE_URLS>