Project

General

Profile

Actions

Bug #27675

closed

Execution of task fails with "Class does not exist"

Added by Xavier Perseguers over 13 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
scheduler
Target version:
-
Start date:
2011-06-24
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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

27675.diff (1.26 KB) 27675.diff Xavier Perseguers, 2011-06-24 09:54

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #27677: Caching Framework: use t3lib_cache_frontend_VariableFrontend as fallback frontendClosedXavier Perseguers2011-06-24

Actions
Is duplicate of TYPO3 Core - Bug #27674: Execution of task fails with "Class does not exist"Closed2011-06-24

Actions
Actions #1

Updated by Francois Suter over 13 years ago

  • Status changed from New to Closed

Duplicate

Actions #2

Updated by Xavier Perseguers over 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.

Actions #3

Updated by Francois Suter over 13 years ago

  • Status changed from Closed to New
Actions #4

Updated by Xavier Perseguers over 13 years ago

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.

Actions #5

Updated by Francois Suter over 13 years ago

  • Status changed from New to Closed

Closed on request of the report (problem will be solved on the caching framework side).

Actions #6

Updated by Michael Stucki almost 11 years ago

  • Category set to scheduler
Actions #7

Updated by Michael Stucki almost 11 years ago

  • Project changed from 739 to TYPO3 Core
  • Category changed from scheduler to scheduler
Actions

Also available in: Atom PDF