[TYPO3-core] Bypass version compatibility check in 6.2 extension manager

[Steffen Gebert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Loek, I agree with you here. I had the pleasure to work with a TYPO3
web site this week (after not doing this for a while) and running 6.2
and downloading extensions is really annoying.

Given the fact that most extensions are still compatible, there should
be really a way to use them.

btw. I went to typo3.org and downloaded the extensions, then uploaded
it with the EM.

Kind regards
Steffen

- -- 
Steffen Gebert
TYPO3 Server Administration Team Member

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org

My wish list:
https://www.amazon.de/registry/wishlist/922E3JYSQ7CV/ref=cm_wl_sb_v?sort=priority

On 14/11/13 15:23, Loek Hilgersom wrote:
> Hi all,
> 
> While test-driving 6.2-dev I'm running into the new compatibility
> check in the extension manager. It refuses to install extensions
> which do not have explicit 6.2 support in ext_emconf.php, and
> therefor there are very few extensions which can be installed at
> all.
> 
> Normally I would download AND install the extension in my 
> dev-environment to test if it works. If it would break the
> installation I would de-install and remove, or fix the code and
> re-install.
> 
> I would expect a warning, and maybe refuse to install without
> prior warnings, but now I can not even download it to fix it
> myself. Trying out older extensions gets really annoying this way,
> because I'd first have to figure out where the git or
> svn-repository is - if it exists at all - and otherwise download
> the extension in some older TYPO3-installation, or some other
> lengthy procedure.
> 
> Also, if the extension manager refuses to even download older 
> extensions, there is no point in showing them either.
> 
> I think it should just present a severe warning before allowing you
> to install older extensions, or at least download them. There could
> also be an install tool option that would allow this behaviour, so
> that it the default remains as it is now.
> 
> What do you think? Or did I miss something?
> 
> Loek
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJShN7oAAoJEIskG/rSlyw4jF4H/RvyTStRAtYBIFTPoyThQ/V9
M7Ex2XKIKIIBI84KKODTXV4Z6C0dMOB0LAz/n0Q+s/xwPHAweboUT1Vw3ArTpVVV
XOQqu5heHLzsxKCNEDXNQc+1ZYDjqmRBNERuhIffZG0Rt089a9pvIPxtBdG0SpMz
m/dd6RVACXBFDbIvgcqZZ5C320+v6ph4Z+93z1RDJngd3BOf1bMdEgKjSQOxIL4y
9Ff9yM/NuQWa867EEREpXqjhM8vg5KHbxj4lGDNbZwbHtGgocFM1DCDClkq0zIqD
iWKO4E3hkbYeDDGCumweQTGaUWHYSdejLJDXTIwSRJtzqMgx4iBg5rrbR6yEQ/4=
=mtfx
-----END PGP SIGNATURE-----