Project

General

Profile

Actions

Bug #20034

closed

Trouble with dbal deactivation in 4.2 update

Added by Bernd Warken almost 16 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2009-02-17
Due date:
% Done:

0%

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

Description

I had trouble when I updated a website from TYPO3 4.1 to 4.2. It displays a lot of error messages and warnings in the frontend and backend. In the Extension Manager, these messages block even to choose between "Loaded Extensions" and "Installed Extensions", etc. The error messages also block the creation of a new page, because the storage buttons are not even visible.

The heavy errors started when I tried to deinstall dbal. In a copy of the 4.1 version of the website, I deinstalled dbal in 4.1. Then I could update to 4.2 without problems.

Something about the position of the error messages must be done. Moreover, I am not able to reinstall dbal in order to reorder the whole mess.

I constructed a website with the bug. It's frontend is available at http://nctest.netcos.de. You can login at its backend http://nctest.netcos.de/typo3
with the user name "bug" and the password "typo3". That's an admin login, so you can check the whole problem.

This website has already the patch for bug-8231 applied. This was necessary because of dbal.

It has quixplorer and phpmyadmin. This website is totally in German.

(issue imported from #M10462)


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #18220: typo3-docheader not visible when error occuresClosedSteffen Kamper2008-02-15

Actions
Actions

Also available in: Atom PDF