Project

General

Profile

Actions
Copy link

Bug #25278

closed

t3lib_extjs_ExtDirectDebug::__destruct() missing

Added by Björn Pedersen about 13 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-03-08
Due date:
% Done:

100%

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

Description

From my Developerlog:
PHP Warning: (Registered shutdown functions) Unable to call t3lib_extjs_ExtDirectDebug::__destruct() - function does not exist in Unknown line 0

(issue imported from #M17891)

Files

adminlog.jpg (105 KB) adminlog.jpg Screenshot of Administrator Log Markus Klein, 2011-04-26 10:27

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #67610: Unable to call TYPO3\CMS\Core\ExtDirect\ExtDirectDebug::__destructor()Closed2015-06-18

Actions
Actions
Copy link
 #1

Updated by Markus Klein almost 13 years ago

  • Target version deleted (0)

Administrator Log says:

Core: Error handler (BE): PHP Warning: (Registered shutdown functions) Unable to call t3lib_extjs_ExtDirectDebug::__destructor() - function does not exist in Unknown line 0

Note the difference between __destruct() and __destructor().

Actions
Copy link
 #2

Updated by Björn Pedersen almost 13 years ago

Here it really says __destruct, not __destructor. I just checked again.

Actions
Copy link
 #3

Updated by Mr. Hudson almost 13 years ago

Patch set 6 of change I42595a7ebbc3c941bf64bc0699ff908059c107bb has been pushed to the review server.
It is available at http://review.typo3.org/1092

Actions
Copy link
 #4

Updated by Markus Klein almost 13 years ago

I also rechecked with 4.5 branch.
In the Administrator Log (not developer log) it definitely says __destructor.
See my attached screen shot.

So please also check, where this exception comes from, or why different method names are stated.

Actions
Copy link
 #5

Updated by Björn Pedersen almost 13 years ago

Here I have _destruct also in the the admin log.

Check, that you are not affected by: http://bugs.typo3.org/view.php?id=16468 or http://forge.typo3.org/issues/10948.

Actions
Copy link
 #6

Updated by Markus Klein almost 13 years ago

Ok. Thanks for this hint. It was fire_debug.
Having the same error on master with _destruct.
So you have my go on this!

Actions
Copy link
 #7

Updated by Björn Pedersen almost 13 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
Actions
Copy link
 #8

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF