Bug #27675
closed
Execution of task fails with "Class does not exist"
0%
Description
When I try to manually run task "Caching framework garbage collection (scheduler)", it fails with this flash message:
Execution of task "Caching framework garbage collection (scheduler)" failed
with the following message: Class does not exist
As I had this problem with a task of mine yesterday and I tracked down the bug, it was easy to spot out the problem (comment I put in my extension for the catch):
// BEWARE: Cannot limit to t3lib_cache_exception_NoSuchCache as when instantiating
// the caching framework from a scheduler task, the object name of the
// cache frontend (t3lib_cache_frontend_VariableFrontend) is empty and
// crashes t3lib_div::makeInstance() called from t3lib_cache_Factory::cache()
// with an empty class name.
Files
Updated by Xavier Perseguers almost 13 years ago
Actually problem is not exactly the same as I had but seems to be related with an (incomplete?) caching configuration in one of the installed extensions.
Updated by Xavier Perseguers almost 13 years ago
- File 27675.diff 27675.diff added
I tracked down the problem because it was not completely the same and found another problem I fixed with the if(!isset() part.
Problem is that according to http://wiki.typo3.org/Caching_framework#Register_a_cache, one has to define the 'frontend' of the caching framework whereas when reading article from Dmitry: http://dmitry-dulepov.com/article/how-to-enable-memcached-cache-in-typo3-43.html, this is not needed.
IIRC at the beginning we had to define it and then it was said it was not needed anymore, one had only to define the backend. However I cannot find this information anymore and perhaps this is the other way around.
Updated by Francois Suter almost 13 years ago
- Status changed from New to Closed
Closed on request of the report (problem will be solved on the caching framework side).
Updated by Michael Stucki over 10 years ago
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler