Project

General

Profile

Actions

Bug #77952

closed

Undefined index: TYPO3_DB in AbstractExceptionHandler.php

Added by Franz Holzinger about 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2016-09-14
Due date:
% Done:

0%

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

Description

The Install Tool shows this error warning:

Check for broken extensions


E_NOTICE

Undefined index: TYPO3_DB in /path/typo3_src-7.6.11/typo3/sysext/core/Classes/Error/AbstractExceptionHandler.php on line 174
Actions #1

Updated by Georg Ringer about 8 years ago

  • Status changed from New to Needs Feedback

Are any extensions installed? If yes please deactivate all to check if it is a core issue.

Thanks for giving feedback!

Actions #2

Updated by Franz Holzinger about 8 years ago

I did execute the check for broken extensions because extensions for TYPO3 6.2 had been installed and I wanted to check and maybe unstall them from the Install Tool.
Now I updated one of those extensions by FTP and the Extension Manager and the Install Tool error warning is gone.
I still think this is a TYPO3 Install Tool issue. The "check of broken extensions" should offer the broken extension to uninstall them.

Actions #3

Updated by Christian Kuhn about 8 years ago

well, the 'check for broken extensions' only allows to unload extension that it actually detects as faulty. the 'broken ext check' only tests ext_localconf and ext_tables loading, nothing more - this is NOT a foolproof system to check every detail of an extension: it basically only takes care that probably you backend will not fatal anymore after an upgrade (in case no extension has additional low-level backend hooks that also may fatal a backend call).

if i read you correctly franz, you propose a functionality in the install tool to force unloading any extension (except the protected ones). i think that would actually be a useful feature. would be nice to have that.

Actions #4

Updated by Franz Holzinger about 8 years ago

But if an extension raises an exception then this could be detected and reported as well by the Install Tool.
The feature to unload the extensions would be nice. However if it is done automatically then there should be a notice or a log file entry for the user in order to tell him which extensions have been deinstalled.

Actions #5

Updated by Christian Kuhn almost 8 years ago

Well no, the install tool can not check if some extension raises an exception in any use case.

Actions #6

Updated by Riccardo De Contardi over 7 years ago

  • Status changed from Needs Feedback to Closed

Sorry, but we are closing it: the install tool checker can not detect every possible problem an extension may have.

If you think that this is the wrong decision, then please reopen it or open a new issue with a reference to this one. Thank you.

Actions

Also available in: Atom PDF