TYPO3 Core

Task #78140

Updated by Josef Glatz almost 8 years ago

h1. Problem/Description 

 I needed a few hours until I understood/find that a cacheConfiguration is added to LocalConfiguration (see below) if APCu is detected.  

 <pre> 
        'caching' => [ 
             'cacheConfigurations' => [ 
                 'extbase_object' => [ 
                     'backend' => 'TYPO3\\CMS\\Core\\Cache\\Backend\\ApcuBackend', 
                     'frontend' => 'TYPO3\\CMS\\Core\\Cache\\Frontend\\VariableFrontend', 
                     'groups' => [ 
                         'system', 
                     ], 
                     'options' => [ 
                         'defaultLifetime' => 0, 
                     ], 
                 ], 
             ], 
         ], 
 </pre> 

 h2. The big problem 

 There is no information or additional code added, which automatically disables APCu on CLI. If you are not deep into what APCu is or what TYPO3 do while installing the instance, you can freak out ;-) 

 After finishing the install wizard, the install tool DB Compare shows you 
 <pre> 
  ALTER TABLE cf_extbase_object RENAME TO zzz_deleted_cf_extbase_object 
  ALTER TABLE cf_extbase_object_tags RENAME TO zzz_deleted_cf_extbase_object_tags 
 </pre> 
 which could also be very confusing. 

 --- 

 h1. Acceptance Criteria  

 h2. Possible scenario 1) 

 A TYPO3 integrator should get informed about what is added to LocalConfiguration automatically by the TYPO3 install process and what he has to do if he run CLI tasks/extbase command controllers. 

 h2. Possible scenario 2) 

 An automatically added cacheConfiguration is automatically added to AdditionalConfiguration.php and wrapped into an if with a condition something like @PHP_SAPI == 'cli'@ (or whatever is enough to fix CLI) 

 h2. Possible scenario 3) 

 Such cache backends, which are known to not work in CLI mode must be disabled transparent.

Back