Project

General

Profile

Actions

Bug #59353

closed

TYPO3 Upgrade to 6.2.3

Added by Jainish Senjaliya almost 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Won't have this time
Category:
Backend User Interface
Target version:
-
Start date:
2014-06-05
Due date:
% Done:

0%

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

Description

Hello,

I have upgrade typo3 project 4.5 to 4.7 its was successfully upgraded.
Then I have upgrade typo3 4.7 to 6.1.9 and its successfully upgraded.
But while i upgrading 6.1.9 to 6.2.3 that time i got below error.

Fatal error: Class 'TYPO3\CMS\Extbase\SignalSlot\Dispatcher' not found in /typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 4280

Can anyone help me in finding the solution?

Actions #1

Updated by Dmitry Dulepov almost 10 years ago

  • Status changed from New to Closed
  • Priority changed from Should have to Won't have this time

Please, ask support questions in TYPO3 mailing lists. The bug tracker is for bugs, not for questions :) People in TYPO3 mailing lists should be able to help you with this. Most likely it is a simple cache issue.

Here is the address for the mailing list you should use: http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english

Actions #2

Updated by Markus Klein almost 10 years ago

Or use the forum if you like it better than the mailing list:
http://forum.typo3.org/index.php/f/10/

Actions #3

Updated by Jainish Senjaliya almost 10 years ago

I think this is bug..
While i am upgrading to 6.2 then throw this error message.

Actions #4

Updated by Dmitry Dulepov almost 10 years ago

How can you be sure that it is a bug and not an improper upgrade? Did you follow all steps to upgrade? Did you clear all caches? Do you have any leftovers, which could cause the issue?

If you think it is a bug, it should be reproducible by others. I upgraded several installations from 6.1.x to 6.2 -> no such issue. Therefore I think your upgrade could somehow go wrong and you should seek help in mailing lists before saying it is a bug in TYPO3.

Please, ask in the mailing lists first.

Actions

Also available in: Atom PDF