Bug #24189
closed
No repository records in sys_ter if TYPO3 update from v4.4.x
Added by Michael Schams almost 14 years ago.
Updated over 10 years ago.
Description
The DB table "sys_ter" was introduced in TYPO3 version 4.5-dev and stores information about the repositories for extensions and extension updates. During a fresh and clean TYPO3 version 4.5.0beta1 installation, the DB table sys_ter is filled with an initial record: "TYPO3.org Main Repository" (wsdl_url: http://typo3.org/wsdl/tx_ter_wsdl.php).
If you update your TYPO3 instance from TYPO3 version 4.4.x to version 4.5.x (beta1), the new table is created but does not contain any records.
Impact:
TYPO3 version 4.5.0beta1 seems not to use sys_ter very extensively. The "Mirror list" in ADMIN TOOLS -> Ext Manager -> settings shows a different, larger list (typo3.org main repository plus 6 mirrors), however sys_ter only has one record.
The main impact seems to be the (new) scheduler task to update extension list automatically (introduced in TYPO3 version 4.5.0beta1, see ticket #23848). This process is not working if you updated your TYPO3 instance from an older TYPO3 version to version 4.5.0beta1 (just because sys_ter is empty).
Issue is reproducible with (update from) TYPO3 version 4.4.4 to (update to) TYPO3 version 4.5.0beta1.
(issue imported from #M16549)
The complete update also requires a "import static data" in the install tool. That should offer to fill the table.
Regarding note 0044287: this makes perfect sense. I can confirm that this solves the issue. I added a note to the official Upgrade Instructions (http://wiki.typo3.org/Upgrade#Next_steps_2). This may become obsolete with TYPO3 4.5.0beta2 (or a later version).
Would be nice to initialize the DB table as a further step in the "Update Wizard" (avoids an additional error source) because this is not obvious from my perspective. But let's see if the re-structured interface (targeted for beta2) already addresses this weakness.
- Status changed from New to Needs Feedback
- Target version deleted (
0)
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
As this happen with the dev version, this was fixed if I remember right.
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF