Actions
Bug #40508
closedEM 6.0 fails if DB is empty
Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Extension Manager
Target version:
-
Start date:
2012-09-01
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
6.0
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
After pulling the current master, running Compare Database and updating the DB, I get the following error in the BE when trying to access the EM.
#1: PHP Catchable Fatal Error: Argument 1 passed to TYPO3\CMS\Extensionmanager\Utility\Repository\Helper::setRepository() must be an instance of TYPO3\CMS\Extensionmanager\Domain\Model\Repository, null given, called in typo3/sysext/extensionmanager/Classes/Utility/Repository/Helper.php on line 88 and defined in typo3/sysext/extensionmanager/Classes/Utility/Repository/Helper.php line 101
The reason is that the repository table not existing or empty.
Unfortunately I'm not able to add the table via Static Data of the EM extension as I need a working EM for that.
(Chicken+Egg)
Possible solution:
Provide an upgrade wizard which ensures that this table exists and contains at least one repository.
Updated by Susanne Moog about 12 years ago
- Project changed from TYPO3 Core to 2269
- Category deleted (
Extension Manager) - Target version deleted (
6.0.0-beta2)
Updated by Francois Suter about 12 years ago
I agree with the need for an upgrade wizard.
Updated by Gerrit Code Review about 12 years ago
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14506
Updated by Gerrit Code Review about 12 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14506
Updated by Christian Kuhn about 12 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
- PHP Version set to 5.3
Updated by Oliver Hader over 11 years ago
- Project changed from 2269 to TYPO3 Core
Actions