CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.6 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Bug #32819

TYPO3 Versionnumbers Update does not get 4.4.latest version

Added by René Häfliger over 1 year ago. Updated 6 months ago.

Status:Needs Feedback Start date:2011-12-23
Priority:Must have Due date:
Assignee:René Häfliger % Done:

0%

Category:-
Target version:-
Votes: 0

Description

In tx_caretaker_LatestVersionsHelper::updateLatestTypo3VersionRegistry() the URL contains a limit of 40.
Therefore the 4.4.latest is not updated 4.5, 4.6 and 4.7 are OK. An increase to 100 solved the problem.

http://sourceforge.net/api/file/index/project-id/20391/mtime/desc/limit/100/rss

class.tx_caretaker_LatestVersionsHelper.php.patch - Patch to update limit from 40 to 100 (755 Bytes) Matthias Hogerheijde, 2012-01-18 19:27


Related issues

related to Caretaker - Bug #33194: TYPO3-Version *.latest does not work Needs Feedback 2012-01-14
related to Caretaker - Bug #36592: TYPO3VersionTest ".latest" fails for RC versions New 2012-04-26

History

Updated by Matthias Hogerheijde over 1 year ago

I can confirm this. With 100 as limit, typo3 4.3 won't be included. 4.3 is obsolete of course and one could argue that the last 100 edited versions should be all you are interested in.

I've included a patch to update the limit to 100, but I would say, why not fetch the entire list from http://sourceforge.net/api/file/index/project-id/20391/mtime/desc/rss ?

Updated by Lorenz Ulrich over 1 year ago

Is this related to the problem that Caretaker only accepts versions until 4.5.10 as valid? Now that 4.5.11 is out this throws unnecessary errors.

Updated by Tobias Liebig 6 months ago

  • Status changed from New to Needs Feedback
  • Assignee set to René Häfliger

I refactored the tx_caretaker_LatestVersionsHelper in my caretaker fork on Github: https://github.com/etobi/caretaker
It now uses the official JSON releases feed at get.typo3.org/json and should be much more staple.

Could you test if this issue is solved with that version? If yes, i can "pull request" it into the official repository.

Also available in: Atom PDF