TYPO3 Core

Proposal:

Add an option in caching configuration to declare the backend to be manually handled:

$TYPO3_CONF_VARS['SYS']['caching']['cacheConfigurations']['egovapi'] = array(
        'backend' => 't3lib_cache_backend_DbBackend',
        'options' => array(
                'manualFlush' => TRUE,
        )
);

Hey Xavier,

I thought about your issue as well since you raised it in the v4 list. Your solution is one option, and another one would be to handle this in the cacheManager class with a hook or something. In any case we should synchronize this with FLOW3, they might have the same issue. I'll trigger the FLOW3 team in this regard.

Christian

Hey Christian,

Thanks for the information. I know you did not forget about it, I just wanted to raise the awareness of this to the whole community because I'd like to integrate this "final" change into beta3, tomorrow.

Having a hook is fine as well of course and would even be slightly better since it allows even finer tuning and is more in line with our policy not to introduce new features after freeze (a hook being NOT considered as a new feature in our policy).

As you see, I linked to my own problem in egovapi, I may implement whichever solution for testing right away!

Another idea that would work without any changes:

You create an own frontend that overwrites flush():
flush() {
if (func_get_args === 0) {
noop();
} else {
if ($param¹ === 'really-flush') {
parent::flush();
}
}
}

This way flush() would do nothing if you do not add some special parameter.

This might be a bit hacky, but it could be a solution until we come up with some serious solution from FLOW3.

Very good idea! Thanks.