Project

General

Profile

Actions
Copy link

Bug #58948

closed

EM in 6.2.2 not loading list of extension correctly

Added by Paul A. Auwehla over 10 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Pierrick Caillon
Category:
Extension Manager
Target version:
-
Start date:
2014-05-20
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:
Remote Sprint

Description

There are lots of reports to EM around here.
But EM still is not working stable as expected.

The problem seems that the process of getting the
extension list from TER is not stable and has no error or state checking.
Situation on a very good working installation of 6.2.2 is the following:

The extension-list is fetched from TER as 2 files in typo3temp:
1.extensions.xml.gz
1.mirrors.xml.gz
Is there any check whether this files are complete ok or not?
By hash or size or extensions included or anything else?

These 2 xml-lists are then read into 2 db-tables:
tx_extensionmanager_domain_model_repository (one row)and
tx_extensionmanager_domain_model_extension (around 20500 rows)

(1) problem seems that the fields
tx_extensionmanager_domain_model_repository-last_update and
tx_extensionmanager_domain_model_repository-extension_count
are not updated correctly.
Sometimes EM finds the list is never updated,
sometimes it is updated 2 years ago
sometimes it is yesterday, with still the same or newer extensions.xml from typo3temp.

The db-field -extension_count is not set correctly.
Sometimes it is empty, sometimes there are the 6.xxx extensions found in the extension.xml.
It does not matter which size and row-count the exntensions-table is.

(2) problem seems that the update of the db-tables from the xml
file is without any error check.
The xml is read into db-table over and over again from the very beginning.
You can see the EM fill the table from 0 to 20500 rows if you are lucky.
But most often the update process stops before reaching the full count of rows.
16000 or 11500 rows are read into table or something like this.
Looks like the process is not checking whether the data is received
from the DBserver correctly.

If the db-update process fails to get all data into db-table it tries again sending from the first row.
So if there is a tiny timing or update problem with the DBserver this is like playing for good luck.

Then the two fields from (1) problem are not set as expected ...

PS.
Removed all files in typo3temp/* and all caches over and over again,
and deleted/truncated the two db-tables and recreating them with Install-tool
does help only randomly and by good luck - sometimes.

Actions
Copy link

Also available in: Atom PDF