| 1 | <?php |
| 2 | /* |
| 3 | WHAT THIS FILE IS ABOUT - READ CAREFULLY |
| 4 | ---------------------------------------- |
| 5 | This file contains a documented list of the few configuration points |
| 6 | available from config.php. The proposed default values below are meant |
| 7 | to be the most optimized ones, or meaningful examples of what can be achieved. |
| 8 | |
| 9 | In order to have the present settings taken into account, you will need to |
| 10 | rename this file into config.php, and keep it placed at the root of eZ Publish, |
| 11 | where config.php-RECOMMENDED is currently placed. Plus, you will need to |
| 12 | *uncomment* the proposed settings. |
| 13 | */ |
| 14 | |
| 15 | |
| 16 | /* |
| 17 | PATH TO THE EZCOMPONENTS |
| 18 | ------------------------ |
| 19 | config.php can set the components path like: |
| 20 | */ |
| 21 | //ini_set( 'include_path', ini_get( 'include_path' ). PATH_SEPARATOR . '../ezcomponents/trunk' ); |
| 22 | |
| 23 | /* |
| 24 | USING BUNDLED COMPONENTS |
| 25 | ------------------------ |
| 26 | If you are using a distribution of eZ Publish with which the necessary |
| 27 | eZ Components are bundled (in lib/ezc), then you can use this setting to |
| 28 | control if the bundled eZ Components should be used (true) or not (false). |
| 29 | By default, when this setting is not present and the bundled eZ Components are |
| 30 | present, they will be used. If you're using the bundled eZ Components it's recommended |
| 31 | to define EZP_USE_BUNDLED_COMPONENTS as a boolean true anyway, for optimal speed. |
| 32 | */ |
| 33 | //define( 'EZP_USE_BUNDLED_COMPONENTS', true ); |
| 34 | |
| 35 | |
| 36 | /* |
| 37 | If you are not using the bundled eZ Components, then for optimal speed it is |
| 38 | recommended to set EZC_BASE_PATH to either ezc/Base/base.php or Base/src/base.php, |
| 39 | depending on how you installed the eZ Components. By default, if this setting |
| 40 | is not present, eZ Publish first tries to include ezc/Base/base.php in the standard |
| 41 | php include path. If that fails Base/src/base.php is included. |
| 42 | */ |
| 43 | //define( 'EZC_BASE_PATH', '/usr/lib/ezc/Base/base.php' ); |
| 44 | |
| 45 | /* |
| 46 | TIMEZONES |
| 47 | --------- |
| 48 | The recommended way of setting timezones is via php.ini. |
| 49 | However you can set the default timezone for your eZ Publish application as shown below. |
| 50 | More on supported timezones : http://www.php.net/manual/en/timezones.php |
| 51 | */ |
| 52 | //date_default_timezone_set( 'Europe/Paris' ); |
| 53 | |
| 54 | /* |
| 55 | INI FILES OPTIMIZATIONS |
| 56 | ----------------------- |
| 57 | This new setting controls whether eZINI should check if the settings have |
| 58 | been updated in the *.ini-files*. If this check is disabled eZ Publish |
| 59 | will always used the cached values, lowering the amount of stat-calls to |
| 60 | the file system, and thus increasing performance. |
| 61 | |
| 62 | Set EZP_INI_FILEMTIME_CHECK constant to false to improve performance by |
| 63 | not checking modified time on ini files. You can also set it to a string, the name |
| 64 | of a ini file you still want to check modified time on, best example would be to |
| 65 | set it to 'site.ini' to make the system still check that but not the rest. |
| 66 | */ |
| 67 | define( 'EZP_INI_FILEMTIME_CHECK', false ); |
| 68 | |
| 69 | |
| 70 | /* |
| 71 | KERNEL OVERRIDES |
| 72 | ---------------- |
| 73 | This setting controls if eZ Publish's autoload system should allow, and |
| 74 | load classes, which override kernel classes from extensions. |
| 75 | */ |
| 76 | //define( 'EZP_AUTOLOAD_ALLOW_KERNEL_OVERRIDE', false ); |
| 77 | |
| 78 | |
| 79 | /* |
| 80 | Set EZP_INI_FILE_PERMISSION constant to the permissions you want saved |
| 81 | ini and cache files to have. This setting also applies to generated autoload files. |
| 82 | Do keep an octal number as value here ( meaning it starts by a 0 ). |
| 83 | */ |
| 84 | //define( 'EZP_INI_FILE_PERMISSION', 0666 ); |
| 85 | |
| 86 | |
| 87 | |
| 88 | /* |
| 89 | CUSTOM AUTOLOAD MECHANISM |
| 90 | ------------------------- |
| 91 | It is also possible to push a custom autoload method to the autoload |
| 92 | function stack. Remember to check for class prefixes in such a method, if it |
| 93 | will not serve classes from eZ Publish and eZ Components. |
| 94 | Here is an example code snippet to be placed right in this file, in the case |
| 95 | you would be using your custom Foo framework, in which all PHP classes would be |
| 96 | prefixed by 'Foo' : |
| 97 | |
| 98 | <code> |
| 99 | ini_set( 'include_path', ini_get( 'include_path' ). ':/usr/lib/FooFramework/' ); |
| 100 | require 'Foo/ClassLoader.php'; |
| 101 | |
| 102 | function fooAutoload( $className ) |
| 103 | { |
| 104 | if ( 'Foo' == substr( $className, 0, 3 ) ) |
| 105 | { |
| 106 | FooClassLoader::loadClass( $className ); |
| 107 | } |
| 108 | } |
| 109 | spl_autoload_register( 'fooAutoload' ); |
| 110 | </code> |
| 111 | */ |
| 112 | ?> |
| 113 | |
