[TYPO3-dev] Extensions need update for 4.3!

[Jigal van Hemert]

Dmitry Dulepov wrote:
> Jigal van Hemert wrote:
>> What happened to "backwards compatibility"?
>
> Nothing. It is a code error to pass non-array when function expects array.
> It was simply enforced for 4.3.

Let's forget about semantics. An extension works (as in provides the
expected functionality without producing errors) in 4.2.x and produces a
fatal error in 4.3. This extension isn't compatible with 4.3, so 4.3 isn't
backwards compatible.
You can defend the behaviour by claiming that 4.3 only enforces rules that
were already there in older versions, but the practical truth is that this
stops a lot of (perhaps poorly coded) extensions from working.

Next to the "Don't panic" sign there should be a warning that upgrading to
4.3 may cause a lot of extensions to produce fatal errors. :-)

>> I agree, but the practical side is that TYPO3 lives in a world with
>> thousands of extensions which may not all contain the best possible code
>> :-(
>
> Use better extensions ;)

For many things there isn't much choice :-(

>> If it were 5.0 I wouldn't mind stricter demands, but for 4.x I expect as
>> many extensions as possible still to function as before. (My $0.02)
>
> I would ask author for update :)

Judging by the number of "the author failed to respond or provide an
update within a reasoble amount of time" remarks in the notices from the
security team, this isn't something you can expect all the time. Even when
the author manages to update the extension in a month, what should all the
non-developers do with their websites? Just post a notice like "we had to
disable the xxx functionality while we are waiting for the author to
provide an update"??

Minor updates just shouldn't stop "a lot of extensions" (as Steffen put
it) from working.

-- 
Jigal van Hemert.