Changeset 2794
- Timestamp:
- 11/23/06 20:45:47 (2 years ago)
- Files:
-
- trunk/data/config/settings.yml (modified) (1 diff)
- trunk/data/skeleton/app/app/config/cache.yml (modified) (1 diff)
- trunk/data/skeleton/app/app/config/settings.yml (modified) (1 diff)
- trunk/data/tasks/sfPakeUpgrade.php (modified) (13 diffs)
- trunk/doc/book/content/cache.txt (modified) (13 diffs)
- trunk/doc/book/content/configuration_practice.txt (modified) (4 diffs)
- trunk/doc/book/content/fillin.txt (modified) (3 diffs)
- trunk/doc/book/content/plugin.txt (modified) (2 diffs)
- trunk/doc/book/content/validate_form.txt (modified) (3 diffs)
- trunk/lib/config/sfCacheConfigHandler.class.php (modified) (2 diffs)
- trunk/lib/controller/sfController.class.php (modified) (2 diffs)
- trunk/lib/filter/sfExecutionFilter.class.php (modified) (1 diff)
- trunk/lib/test/sfTestBrowser.class.php (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/backend/config/cache.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/backend/config/settings.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/cache/config/cache.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/cache/config/settings.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/cache/modules/cache/config/cache.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/cache/modules/nocache/config/cache.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/crud/config/cache.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/crud/config/settings.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/frontend/config/cache.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/frontend/config/settings.yml (modified) (2 diffs)
- trunk/test/functional/fixtures/project/apps/frontend/modules/validation/validate/index.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/i18n/config/cache.yml (modified) (1 diff)
- trunk/test/functional/fixtures/project/apps/i18n/config/settings.yml (modified) (1 diff)
- trunk/test/unit/config/fixtures/sfDefineEnvironmentConfigHandler/prefix_all.yml (modified) (1 diff)
- trunk/test/unit/config/fixtures/sfDefineEnvironmentConfigHandler/prefix_default.yml (modified) (1 diff)
- trunk/test/unit/config/fixtures/sfDefineEnvironmentConfigHandler/prefix_result.php (modified) (1 diff)
- trunk/test/unit/config/fixtures/sfValidatorConfigHandler/alternate_format.yml (modified) (1 diff)
- trunk/test/unit/config/fixtures/sfValidatorConfigHandler/standard_format.yml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/data/config/settings.yml
r2679 r2794 56 56 use_flash: on 57 57 58 activated_modules:[default]58 enabled_modules: [default] 59 59 60 60 strip_comments: on trunk/data/skeleton/app/app/config/cache.yml
r1982 r2794 1 1 default: 2 activate:off2 enabled: off 3 3 with_layout: false 4 4 lifetime: 86400 trunk/data/skeleton/app/app/config/settings.yml
r2679 r2794 78 78 # use_flash: on 79 79 # 80 # activated_modules:[default]80 # enabled_modules: [default] 81 81 # 82 82 # strip_comments: on trunk/data/tasks/sfPakeUpgrade.php
r2734 r2794 56 56 _upgrade_1_0_propel_model(); 57 57 58 // migrate activate to enabled 59 _upgrade_1_0_activate(); 60 58 61 // find all applications for this project 59 62 $apps = pakeFinder::type('directory')->name(sfConfig::get('sf_app_module_dir_name'))->mindepth(1)->maxdepth(1)->relative()->in(sfConfig::get('sf_apps_dir_name')); … … 178 181 $count = 0; 179 182 $content = str_replace($old, $new, $content, $count); 183 if ($count) 184 { 185 $updated = true; 186 } 180 187 if ($count && !isset($seen[$old])) 181 188 { 182 $updated = true;183 189 $seen[$old] = true; 184 190 pake_echo_comment(sprintf('%s is deprecated', $old)); … … 190 196 { 191 197 file_put_contents($php_file, $content); 198 } 199 } 200 } 201 202 function _upgrade_1_0_activate() 203 { 204 pake_echo_action('upgrade 1.0', 'migrate activate to enabled'); 205 206 $config_files = array( 207 'settings.yml' => array( 208 'activated_modules:' => 'enabled_modules: ', 209 ), 210 'cache.yml' => array( 211 'activate:' => 'enabled: ', 212 ), 213 'apps/*/modules/*/validate/*.yml' => array( 214 'activate:' => 'enabled: ', 215 ), 216 ); 217 $seen = array(); 218 foreach ($config_files as $config_file => $changed) 219 { 220 list($dir, $config_file) = array(dirname($config_file), basename($config_file)); 221 $yml_files = pakeFinder::type('file')->name($config_file)->in(sfConfig::get('sf_root_dir').DIRECTORY_SEPARATOR.$dir); 222 foreach ($yml_files as $yml_file) 223 { 224 $content = file_get_contents($yml_file); 225 226 $updated = false; 227 foreach ($changed as $old => $new) 228 { 229 $content = str_replace($old, $new, $content, $count); 230 if ($count) 231 { 232 $updated = true; 233 } 234 if ($count && !isset($seen[$config_file.$old])) 235 { 236 $seen[$config_file.$old] = true; 237 238 pake_echo_comment(sprintf('%s is deprecated in %s', $old, $config_file)); 239 pake_echo_comment(sprintf(' use %s', $new)); 240 } 241 } 242 243 if ($updated) 244 { 245 file_put_contents($yml_file, $content); 246 } 192 247 } 193 248 } … … 216 271 $count = 0; 217 272 $content = str_replace($old, $new, $content, $count); 273 if ($count) 274 { 275 $updated = true; 276 } 218 277 if ($count && !isset($seen[$old])) 219 278 { 220 $updated = true;221 279 $seen[$old] = true; 222 280 pake_echo_comment(sprintf('%s is deprecated', $old)); … … 246 304 $updated = false; 247 305 $content = preg_replace_callback('/type\:(\s*)(.+)$/m', '_upgrade_1_0_cache_yml_callback', $content, -1, $count); 306 if ($count) 307 { 308 $updated = true; 309 } 248 310 if ($count && !$seen) 249 311 { 250 $updated = true;251 312 $seen = true; 252 313 pake_echo_comment('"type" has been removed in cache.yml'); … … 278 339 foreach ($yml_files as $yml_file) 279 340 { 341 $updated = false; 280 342 foreach ($deprecated_str as $old => $new) 281 343 { … … 283 345 284 346 $count = 0; 285 $updated = false;286 347 $content = str_replace($old, $new, $content, $count); 348 if ($count) 349 { 350 $updated = true; 351 } 287 352 if ($count && !isset($seen[$old])) 288 353 { 289 354 $seen[$old] = true; 290 $updated = true;291 355 pake_echo_comment(sprintf('%s() has been removed', $old)); 292 356 pake_echo_comment(sprintf(' use %s()', $new)); … … 323 387 $count = 0; 324 388 $content = str_replace($old, $new, $content, $count); 389 if ($count) 390 { 391 $updated = true; 392 } 325 393 if ($count && !isset($seen[$old])) 326 394 { 327 $updated = true;328 395 $seen[$old] = true; 329 396 pake_echo_comment(sprintf('%s has been removed', $old)); … … 361 428 $count = 0; 362 429 $content = preg_replace('#<\?php\s+(echo)?\s+include_javascripts\(\);?\s*\?>#', '', $content, -1, $count); 430 if ($count) 431 { 432 $updated = true; 433 } 363 434 if ($count && !isset($seen['include_javascripts'])) 364 435 { 365 $updated = true;366 436 $seen['include_javascripts'] = true; 367 437 pake_echo_comment('include_javascripts() has been removed'); … … 369 439 370 440 $content = preg_replace('#<\?php\s+(echo)?\s+include_stylesheets\(\);?\s*\?>#', '', $content, -1, $count); 441 if ($count) 442 { 443 $updated = true; 444 } 371 445 if ($count && !isset($seen['include_stylesheets'])) 372 446 { 373 $updated = true;374 447 $seen['include_stylesheets'] = true; 375 448 pake_echo_comment('include_stylesheets() has been removed'); … … 379 452 { 380 453 $content = str_replace($old, $new, $content, $count); 454 if ($count) 455 { 456 $updated = true; 457 } 381 458 if ($count && !isset($seen[$old])) 382 459 { 383 $updated = true;384 460 $seen[$old] = true; 385 461 pake_echo_comment(sprintf('%s has been removed', $old)); … … 522 598 $content = str_replace('require_once \'model', 'require_once \'lib/model', $content, $count1); 523 599 $content = str_replace('include_once \'model', 'include_once \'lib/model', $content, $count2); 600 if ($count1 || $count2) 601 { 602 $updated = true; 603 } 524 604 if (($count1 || $count2) && !$seen) 525 605 { 526 $updated = true;527 606 $seen = true; 528 607 pake_echo_comment('model require must be lib/model/...'); … … 555 634 $updated = false; 556 635 $content = str_replace('<database', '<database package="lib.model"', $content, $count); 636 if ($count) 637 { 638 $updated = true; 639 } 557 640 if ($count && !$seen) 558 641 { 559 $updated = true;560 642 $seen = true; 561 643 pake_echo_comment('schema.xml must now have a database package'); trunk/doc/book/content/cache.txt
r2034 r2794 12 12 The principle of HTML caching is simple: part or all of the HTML code that is sent to a user upon a request can be reused for a similar request, so this HTML code is stored in a special place (the `cache` folder in symfony), where the front controller will look for it before executing an action. If a cached version is found, it is sent without executing the action, thus greatly speeding up the process. If there is no cached version found, the action is executed, and its result (the view) is stored in the cache folder for future requests. 13 13 14 As all the pages may contain dynamic information, the HTML cache is disabled by default. It is up to the site administrator to activate it in order to improve performance.14 As all the pages may contain dynamic information, the HTML cache is disabled by default. It is up to the site administrator to enable it in order to improve performance. 15 15 16 16 Symfony handles four different types of HTML cache: … … 28 28 --------------------- 29 29 30 For each application of a project, the HTML cache mechanism can be activated or deactivated completely per environment. In the `settings.yml` configuration file, notice the `cache` parameter:30 For each application of a project, the HTML cache mechanism can be enabled or disabled completely per environment. In the `settings.yml` configuration file, notice the `cache` parameter: 31 31 32 32 prod: … … 57 57 The result of the above-mentioned action is a processed template (`listSuccess.php`), and this is what is going to be cached. 58 58 59 To activate the cache on such actions, simply add a `cache.yml` file in the `myproject/apps/myapp/modules/user/config/` directory, with the following content:59 To enable the cache on such actions, simply add a `cache.yml` file in the `myproject/apps/myapp/modules/user/config/` directory, with the following content: 60 60 61 61 list: 62 activate:on62 enabled on 63 63 type: slot 64 64 … … 73 73 74 74 show: 75 activate:on75 enabled: on 76 76 type: slot 77 77 … … 88 88 <?php include_partial('mymodule/mypartial') ?> 89 89 90 A partial is as easy to cache as an action. To activate it, create a `cache.yml` in the partial module `config/` directory (in the example above, in `modules/mymodule/config/`) and activate the cache for the partials by declaring their names with a leading underscore:90 A partial is as easy to cache as an action. To enable it, create a `cache.yml` in the partial module `config/` directory (in the example above, in `modules/mymodule/config/`) and enable the cache for the partials by declaring their names with a leading underscore: 91 91 92 92 _mypartial: 93 activate: on93 enabled: on 94 94 95 95 all: 96 activate: off96 enabled: off 97 97 98 98 Now all the templates using this partial won't actually execute the PHP code of the partial, but use the cached version instead. … … 113 113 114 114 _day: 115 activate: on115 enabled: on 116 116 117 117 >**Note**: Global components (the ones located in the application `templates/` directory) can be cached, provided you declare the activation in the application `cache.yml` file. … … 127 127 128 128 show: 129 activate:on129 enabled: on 130 130 type: page 131 131 132 132 list: 133 activate:on133 enabled: on 134 134 type: page 135 135 … … 194 194 195 195 list: 196 activate: off196 enabled: off 197 197 198 198 After requesting twice the `http://myapp.example.com/user/list` URL, notice that the second execution is faster than the first. However, the answer is not as fast as when the cache was set to `slot` or `page`, since the template is partially processed and the decoration is made for every request. … … 335 335 ### Staging environment 336 336 337 The caching system is prone to new errors in the production environment that can't be detected in the development environment, since the HTML cache is d eactivated by default in development. If you use the HTML cache, it is strongly recommended to add a new environment, that will be called `staging` here, which is a copy of the production environment (thus with cache activated) but with the web debug set to on.337 The caching system is prone to new errors in the production environment that can't be detected in the development environment, since the HTML cache is disabled by default in development. If you use the HTML cache, it is strongly recommended to add a new environment, that will be called `staging` here, which is a copy of the production environment (thus with cache enabled) but with the web debug set to on. 338 338 339 339 To set it up, edit the `settings.yml` of your application and add at the top: … … 360 360 After a bunch of flags, this debug box also displays the process duration. Go ahead, clear the cache and make some tests: the second time you request a page, depending on the complexity of the action and template, can be several times faster with caching turned on. 361 361 362 To get more details about the caching impact, activate the debug mode by editing the `myapp_staging.php` and changing the `SF_DEBUG` value:362 To get more details about the caching impact, enable the debug mode by editing the `myapp_staging.php` and changing the `SF_DEBUG` value: 363 363 364 364 [php] … … 390 390 ### ETags 391 391 392 When `ETag` is activated, the web server adds to the response a special header containing a md5 hash of the response itself.392 When `ETag` is enabled, the web server adds to the response a special header containing a md5 hash of the response itself. 393 393 394 394 ETag: "1A2Z3E4R5T6Y7U" … … 396 396 The user's browser will store this hash, and send it again together with the request the next time it needs the same page. If the new hash shows that the page didn't change since the first request, the browser doesn't sent the response back. Instead, it just sends a '304: not modified' header. It saves cpu time (gzipping) and bandwidth (page transfer) for the server, and cpu time (page rendering) for the client. Overall, pages in cache with an etag are even faster to load than pages in cache without etag. 397 397 398 In symfony, you activate the etags feature for the whole application in the `settings.yml`. Here is the default setting:398 In symfony, you enable the etags feature for the whole application in the `settings.yml`. Here is the default setting: 399 399 400 400 all: … … 440 440 ### Cache-Control 441 441 442 Up to now, even by adding headers, the browser kept sending requests to the server even if it held a cached version of the page. There is a way to avoid that by adding `Cache-Control` and `Expires` headers to the response. These headers are d eactivated by default in PHP, but symfony can override this behaviour to avoid unecessary requests to your server.442 Up to now, even by adding headers, the browser kept sending requests to the server even if it held a cached version of the page. There is a way to avoid that by adding `Cache-Control` and `Expires` headers to the response. These headers are disabled by default in PHP, but symfony can override this behaviour to avoid unecessary requests to your server. 443 443 444 444 Beware that the major consequence of turning this mechanism on is that your server logs won't show all the requests issued by the users, but only the ones received. If the performance gets better, the apparent popularity of the site may decrease in the statistics. trunk/doc/book/content/configuration_practice.txt
r2446 r2794 19 19 ------------ 20 20 21 The symfony configuration system is inspired by the way [Mojavi][3]handles configuration. Although not appreciated by everyone, this system is extremely powerful.21 The symfony configuration system is inspired by the way Mojavi handles configuration. Although not appreciated by everyone, this system is extremely powerful. 22 22 23 23 Configuration is distributed into files, by subject. The files contain parameter definitions, or settings. … … 62 62 * `routing.yml`: The routing rules, that allow transforming unreadable and unbookmarkable URLs into "smart" and explicit ones, are stored in this file. For new applications, a few default rules exist. See more in the [routing chapter](routing.txt). 63 63 * `settings.yml*`: The main settings of a symfony application are defined in this file. This is where you specify if your application has internationalization, its default language, the request timeout, whether caching is turned on or not, and whether routing is turned on. With a one line change in this file, you can shut down the application so you can perform maintenance or upgrade one of its components. This is a perfect example of the benefit of using a single front web controller. [_see more below_](#settings) 64 * `tidy.yml*`: If the use of [HTML Tidy][1] is activated in the `settings.yml`, then you can modify the options of this utility to alter the HTML code output to, for instance, re-indent the tags properly, or remove comments, or collapse all spaces and carriage returns to save bandwidth, or to correct missing closing tags that were missed by the developers.65 64 * `view.yml`: The structure of the default View (name of the layout, title and metas, default .js and .css files to be included, name of the included slots, etc.) is set in this file. These settings can be overridden for each module. This file also defines the default value of the `meta` and `title` tags. [_see more below_](#view) 66 65 … … 127 126 * `use_security`: If your application has restricted areas, authentication and credentials, set this parameter to `on` (see the [security chapter](security.txt) for more details) 128 127 * `compressed`: Activates the HTML compression to reduce bandwidth requirements and improve performance 129 * `tidy`: Activates the use of [HTML Tidy][1]130 128 * `i18n`: Must be set to `on` for sites/applications available in multiple languages 131 129 * `default_culture`: Specifies the default parameter used to format dates, numbers, currencies (`en` in the default configuration) … … 497 495 [php] 498 496 $myarray = sfYaml::load('/tmp/myfile.yml'); 499 500 [1]: http://www.w3.org/People/Raggett/tidy/ "HTML Tidy"501 [2]: http://www.mojavi.org/ "Mojavi"502 [3]: http://www.mojavi.org/ "Mojavi project"trunk/doc/book/content/fillin.txt
r1284 r2794 25 25 But try to imagine more complicated cases, where the default value comes from the server, or where you have a radiobutton tag or a select tag. Handling all that becomes long and painful in the long run, especially if you have forms with a large number of controls. 26 26 27 Symfony can handle repopulation automatically. To enable that behaviour, you just need to add a `filters.yml` in your module `config/` folder and activate the `sfFillInFormFilter`:27 Symfony can handle repopulation automatically. To enable that behaviour, you just need to add a `filters.yml` in your module `config/` folder and enable the `sfFillInFormFilter`: 28 28 29 29 myFillInFormFilter: … … 40 40 41 41 fillin: 42 activate: on42 enabled: on 43 43 44 44 Filter parameters … … 65 65 66 66 fillin: 67 activate: on67 enabled: on 68 68 param: 69 69 name: search # name of the form trunk/doc/book/content/plugin.txt
r2082 r2794 63 63 ### Module activation 64 64 65 Some plugins contain a whole module. The only difference between module plugins and classical modules is that module plugins don't appear in the `myproject/apps/myapp/modules/` directory (to keep them easily upgradeable) and need to be activated in the `settings.yml` file:65 Some plugins contain a whole module. The only difference between module plugins and classical modules is that module plugins don't appear in the `myproject/apps/myapp/modules/` directory (to keep them easily upgradeable) and need to be enabled in the `settings.yml` file: 66 66 67 67 all: 68 68 .settings: 69 activated_modules: [default, sfMyPluginModule]69 enabled_modules: [default, sfMyPluginModule] 70 70 71 71 This is to avoid that a plugin module becomes available by mistake for an application that doesn't require it, which could open a security breach. … … 142 142 * **Model classes** in `myplugin/lib/model/` specialize the model classes generated by the Propel builder (in `myplugin/lib/model/om/` and `myplugin/lib/model/map/`). They are, of course, autoloaded. Beware that you cannot override the generated model classes of a plugin in your own project directories. 143 143 144 * **Modules** provide new actions accessible from the outside, provided that you declare them in the ` activated_module` setting in your application. Think about a plugin that provides frontend and backend modules. You will need to enable the frontend modules only in your `frontend` application, and the backend ones only in the `backend` application. This is why plugin modules are not activated by default.144 * **Modules** provide new actions accessible from the outside, provided that you declare them in the `enabled_module` setting in your application. Think about a plugin that provides frontend and backend modules. You will need to enable the frontend modules only in your `frontend` application, and the backend ones only in the `backend` application. This is why plugin modules are not enabled by default. 145 145 146 146 * **Web** assets are made available to the server, by creating a symlink to the project `web/` directory, if the system allows it, or by copying the content of the module `web/` directory into the project one. Beware that the module assets are automatically supported only when you install a plugin via the command line. If the plugin is installed from an archive or a version control repository, the copy to the project `web/` directory has to be done by hand, and the README bundled with the plugin should mention it. trunk/doc/book/content/validate_form.txt
r2709 r2794 333 333 334 334 fillin: 335 activate: on # activate the form repopulation335 enabled: on # enable the form repopulation 336 336 param: 337 337 name: test # name of the form … … 344 344 345 345 fillin: 346 activate: on346 enabled: on 347 347 param: 348 348 name: test … … 351 351 htmlspecialchars: [comments] 352 352 353 The repopulation feature is based on a filter called `sfFillInFormFilter`, and it means that you can take advantage of form repopulation even if you don't use the symfony validation files. To activate the filter, just add it to your `filters.yml` as you would do with a normal filter (see more in the [filter chapter](filters.txt)).353 The repopulation feature is based on a filter called `sfFillInFormFilter`, and it means that you can take advantage of form repopulation even if you don't use the symfony validation files. To enable the filter, just add it to your `filters.yml` as you would do with a normal filter (see more in the [filter chapter](filters.txt)). 354 354 355 355 Complex validation needs trunk/lib/config/sfCacheConfigHandler.class.php
r2319 r2794 82 82 $data = array(); 83 83 84 // activated?85 $ activate = $this->getConfigValue('activate', $actionName);84 // enabled? 85 $enabled = $this->getConfigValue('enabled', $actionName); 86 86 87 87 // cache with or without loayout … … 89 89 90 90 // lifetime 91 $lifeTime = !$ activate? '0' : $this->getConfigValue('lifetime', $actionName, '0');91 $lifeTime = !$enabled ? '0' : $this->getConfigValue('lifetime', $actionName, '0'); 92 92 93 93 // client_lifetime 94 $clientLifetime = !$ activate? '0' : $this->getConfigValue('client_lifetime', $actionName, $lifeTime, '0');94 $clientLifetime = !$enabled ? '0' : $this->getConfigValue('client_lifetime', $actionName, $lifeTime, '0'); 95 95 96 96 // contextual trunk/lib/controller/sfController.class.php
r2750 r2794 64 64 * @param boolean $throwExceptions whether to throw exceptions if the controller doesn't exist 65 65 * 66 * @throws sfConfigurationException thrown if the module is not activated66 * @throws sfConfigurationException thrown if the module is not enabled 67 67 * @throws sfControllerException thrown if the controller doesn't exist and the $throwExceptions 68 68 * parameter is set to true … … 73 73 { 74 74 $dirs = sfLoader::getControllerDirs($moduleName); 75 foreach ($dirs as $dir => $check Activated)76 { 77 // plugin module activated?78 if ($check Activated && !in_array($moduleName, sfConfig::get('sf_activated_modules')) && is_readable($dir))79 { 80 $error = 'The module "%s" is not activated.';75 foreach ($dirs as $dir => $checkEnabled) 76 { 77 // plugin module enabled? 78 if ($checkEnabled && !in_array($moduleName, sfConfig::get('sf_enabled_modules')) && is_readable($dir)) 79 { 80 $error = 'The module "%s" is not enabled.'; 81 81 $error = sprintf($error, $moduleName); 82 82 trunk/lib/filter/sfExecutionFilter.class.php
r2666 r2794 191 191 { 192 192 // automatically register the fill in filter if it is not already loaded in the chain 193 if (isset($parameters[' activate']) && $parameters['activate'] && !$filterChain->hasFilter('sfFillInFormFilter'))193 if (isset($parameters['enabled']) && $parameters['enabled'] && !$filterChain->hasFilter('sfFillInFormFilter')) 194 194 { 195 195 // register the fill in form filter trunk/lib/test/sfTestBrowser.class.php
r2748 r2794 188 188 $cacheManager = $this->getContext()->getViewCacheManager(); 189 189 190 // check that cache is activated190 // check that cache is enabled 191 191 if (!$cacheManager) 192 192 { trunk/test/functional/fixtures/project/apps/backend/config/cache.yml
r2217 r2794 1 1 default: 2 activate:off2 enabled: off 3 3 with_layout: false 4 4 lifetime: 86400 trunk/test/functional/fixtures/project/apps/backend/config/settings.yml
r2459 r2794 78 78 # use_flash: on 79 79 # 80 # activated_modules:[default]80 # enabled_modules: [default] 81 81 # 82 82 # strip_comments: on trunk/test/functional/fixtures/project/apps/cache/config/cache.yml
r2169 r2794 1 1 default: 2 activate:on2 enabled: on 3 3 with_layout: false 4 4 lifetime: 86400 trunk/test/functional/fixtures/project/apps/cache/config/settings.yml
r2459 r2794 78 78 # use_flash: on 79 79 # 80 # activated_modules:[default]80 # enabled_modules: [default] 81 81 # 82 82 # strip_comments: on trunk/test/functional/fixtures/project/apps/cache/modules/cache/config/cache.yml
r2558 r2794 1 1 _contextualCacheableComponent: 2 activate:on2 enabled: on 3 3 contextual: true 4 4 5 5 _contextualComponent: 6 activate:off6 enabled: off 7 7 contextual: true 8 8 9 9 _cacheableComponent: 10 activate:on10 enabled: on 11 11 12 12 _component: 13 activate:off13 enabled: off 14 14 15 15 _contextualCacheablePartial: 16 activate:on16 enabled: on 17 17 contextual: true 18 18 19 19 _contextualPartial: 20 activate:off20 enabled: off 21 21 contextual: true 22 22 23 23 _cacheablePartial: 24 activate:on24 enabled: on 25 25 26 26 _partial: 27 activate:off27 enabled: off 28 28 29 29 multi: 30 activate:off30 enabled: off 31 31 32 32 multiBis: 33 activate:off33 enabled: off 34 34 35 35 specificCacheKey: 36 activate:off36 enabled: off 37 37 38 38 action: 39 activate:on39 enabled: on 40 40 with_layout: off 41 41 trunk/test/functional/fixtures/project/apps/cache/modules/nocache/config/cache.yml
r2169 r2794 1 1 all: 2 activate:off2 enabled: off trunk/test/functional/fixtures/project/apps/crud/config/cache.yml
r2126 r2794 1 1 default: 2 activate:off2 enabled: off 3 3 with_layout: false 4 4 lifetime: 86400 trunk/test/functional/fixtures/project/apps/crud/config/settings.yml
r2459 r2794 78 78 # use_flash: on 79 79 # 80 # activated_modules:[default]80 # enabled_modules: [default] 81 81 # 82 82 # strip_comments: on trunk/test/functional/fixtures/project/apps/frontend/config/cache.yml
r2069 r2794 1 1 default: 2 activate:off2 enabled: off 3 3 with_layout: false 4 4 lifetime: 86400 trunk/test/functional/fixtures/project/apps/frontend/config/settings.yml
r2459 r2794 23 23 all: 24 24 .settings: 25 activated_modules:[default, autoloadPlugin]25 enabled_modules: [default, autoloadPlugin] 26 26 27 27 # .actions: … … 81 81 # use_flash: on 82 82 # 83 # activated_modules:[default]83 # enabled_modules: [default] 84 84 # 85 85 # strip_comments: on trunk/test/functional/fixtures/project/apps/frontend/modules/validation/validate/index.yml
r2586 r2794 7 7 8 8 fillin: 9 activate:on9 enabled: on 10 10 11 11 names: trunk/test/functional/fixtures/project/apps/i18n/config/cache.yml
r2740 r2794 1 1 default: 2 activate:off2 enabled: off 3 3 with_layout: false 4 4 lifetime: 86400 trunk/test/functional/fixtures/project/apps/i18n/config/settings.yml
r2750 r2794 78 78 # use_flash: on 79 79 # 80 activated_modules:[default, sfI18NPlugin]80 enabled_modules: [default, sfI18NPlugin] 81 81 # 82 82 # strip_comments: on trunk/test/unit/config/fixtures/sfDefineEnvironmentConfigHandler/prefix_all.yml
r2218 r2794 13 13 i18n: off 14 14 15 activated_modules:[default, user]15 enabled_modules: [default, user] trunk/test/unit/config/fixtures/sfDefineEnvironmentConfigHandler/prefix_default.yml
r2218 r2794 9 9 i18n: off 10 10 11 activated_modules:[default]11 enabled_modules: [default] trunk/test/unit/config/fixtures/sfDefineEnvironmentConfigHandler/prefix_result.php
r2386 r2794 7 7 'sf_available' => false, 8 8 'sf_i18n' => true, 9 'sf_ activated_modules' => array (9 'sf_enabled_modules' => array ( 10 10 0 => 'default', 11 11 1 => 'user', trunk/test/unit/config/fixtures/sfValidatorConfigHandler/alternate_format.yml
r2655 r2794 1 1 fillin: 2 activate:Yes2 enabled: Yes 3 3 4 4 validators: trunk/test/unit/config/fixtures/sfValidatorConfigHandler/standard_format.yml
r2655 r2794 3 3 4 4 fillin: 5 activate:Yes5 enabled: Yes 6 6 7 7 names: