Bug #36183
Feature #31893: Allow XCLASSes to be defined via ext_autoload.php
Make dbal compatible with the new XCLASS schema.
| Status: | Resolved | Start date: | 2012-04-16 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Tolleiv Nietsch | % Done: | 100% |
|
| Category: | - | |||
| Target version: | Core - 6.0.0 | |||
| TYPO3 Version: | 6.0 | Tags: | ||
| Votes: | 0 |
Description
dbal is the only sysext which depends on working XCLASSES - so it should be one of the first to be migrated and check with the new XCLASS handling from #31893
Associated revisions
History
Updated by Tolleiv Nietsch about 1 year ago
- Parent task set to #31983
Updated by Tolleiv Nietsch about 1 year ago
- Parent task changed from #31983 to #31893
Updated by Tolleiv Nietsch about 1 year ago
- Project changed from Core to DBAL
Updated by Gerrit Code Review about 1 year ago
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10557
Updated by Tolleiv Nietsch about 1 year ago
What I did to test it was: installing dbal, checking whether the backend and frontend kept working and checking whether $GLOBALS['TYPO3_DB'] really had the class ux_t3lib_db --- should be enough, right?
Updated by Gerrit Code Review about 1 year ago
Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10557
Updated by Xavier Perseguers about 1 year ago
- Status changed from Accepted to Resolved
- Assignee set to Tolleiv Nietsch
- % Done changed from 0 to 100