Bug #20145
A check in the caching DB backend for the existence of the specified caching table causes mysql warnings
| Status: | Needs Feedback | Start date: | 2009-03-08 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| TYPO3 Version: | 4.3 | Complexity: | ||
| PHP Version: | 5.0 | |||
| Votes: | 0 |
Description
The check is located in the setCacheTable() method and should either be removed or fixed before 4.3.0 final
The check causes mysql warnings when not being logged in and calling typo3/backend.php or the install tool. Reason: the caches in typo3/init.php get initialized before a DB connection has been established.
Related Question: Why aren't there warnings in the FE as the caches get initialized in tslib_fe's constructor which is also before a DB conection exsits?
(issue imported from #M10638)
History
Updated by Alexander Opitz 15 days ago
- Status changed from New to Needs Feedback
- Target version deleted (
-1)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?