Bug #16003
closed
trouble on min and max version requirements checking
Added by Peter Niederlag over 18 years ago.
Updated over 18 years ago.
Category:
Extension Manager
Description
4.0 ships with a '4.0' version string. However some extensions (rtehtmlarea knowingly) might have a min-dependency on '4.0.0'
However current implementation in EM by using version_compare will evaluate '4.0' to not be sufficient for '4.0.0' requirement.
I put in to EM for now, althought I think it might be best to fix the dependency in rtehtmlarea to '4.0'.
Also maybe TYPO3 should always ship with a three digit version-string?
When I uninstall the system extension htmlarea and I try to reinstall it it says that it depends on Typo3 4.0.0 whereas the current version is only 4.0.
(issue imported from #M3175)
The problem is just, that the version comparison function doesn't use
t3lib_div::int_from_ver($verNumberStr) which would make the whole job of
version comparision in the EM much less complicated.
Karsten, it would be great if you could fix this soon, because we might release 4.0.1 very soon to fix the most obvious and annoying small bugs of 4.0.0.
cheers
Ingmar
Well, will 4.0.1 have 4.0.1 as version number? IMHO the bug lies with the two-digit version number of 4.0 which technically doesn't make sense it is 4.0.0, a fact we discussed a few times...
Anyway, I'll look into fixing this. BTW: why is there a history of reinventing the wheel, err, existing functions?
I came to the conclusion that using version_compare() is still the way that makes most sense. TYPO3 should definitely always ship with a three-digit version number. The bug will go away with 4.0.1 anyway.
Regarding ~8753: You can ignore those warnings when installing an extension.
Will cease to be an issue with 4.0.1. TYPO3 should always have a three-digit number. In fact it had back in the 3.6.0 times (so much for the argument of aesthetics - no harm in displaying 4.0.0 on the welcome screen).
Also available in: Atom
PDF