Bug #28561
closed
Extension manager has 2 different last update dates
0%
Description
I upgraded some TYPO3 installations from 4.2.10 to 4.5.4 using the install tool.
Using Scheduler, I configured a daily schedule to update the Extension Manager and ran this manually.
On the Extension Manager - Check for extension updates is the following message:
Last update of the list of extensions: 06-10-10, 14:40.
To get and update the list, go to the section "Import extensions" and use the button "Retrieve/Update".
On the Extension Manager - Extension Manager, Remote Repository tab, is:
Last Update: 29/07/2011 02:02 Extensions in repository: 4721
Clicking the Retrieve/Update icon loads the repository and going back to the Extension Manager - Check for extension updates now shows the extensions that need updating, but still has the 06-10-10, 14:40 last update message.
I am able to reproduce this issue on other installations. One has "Last update of the list of extensions: 01-01-70, 02:00." on the "Check for extension updates" and "Last update: 16/06/2011 23:46 Extensions in repository: 5116" on the Extension Manager - Remote Repository tab.
Updated by Markus Klein over 13 years ago
- Target version deleted (
4.5.5)
Hello!
Good catch ;-) But the reason for these different dates is simply that the old and the new EM are using different "list of extensions"-file.
So updating this list using the new EM does not automatically force an update of the file for the old EM.
In general it should be enough to use the new EM. To check for updated extensions, just load the current extension list und select the last entry in the filter box on the left side of the toolbar.
Regards, Markus
Updated by Chris topher over 13 years ago
The reason for this error is that these two screens do not(!) use the same file with the extension list:
The old modules create and check the file "typo3temp/extensions.xml.gz".
The new module (and the task) however use a file called "typo3temp/1.extensions.xml.gz".
IMO this is a mistake and should be changed so that both use the same file, preferably typo3temp/extensions.xml.gz.
Updated by
Updated by Björn Pedersen over 13 years ago
I guess the number is the uid of the used repository, so it is needed in case of multiple configured repositories ( something, that only the new EM uses).
Updated by Helmut Hummel about 13 years ago
- Priority changed from Should have to Could have
Updated by Anja Leichsenring over 11 years ago
- Status changed from New to Rejected
We have no longer the old EM, so the problem does not exist anymore.