[TYPO3-dev] Request: mark csh_* as obsolete

Steffen Kamper info at sk-typo3.de
Wed Feb 18 17:33:52 CET 2009


Michael Stucki schrieb:
> Hi François,
> 
>>> Since there are so many of them, I would try to change the status
>>> directly in the database and keep the version on the same number (should
>>> not be a problem because the code did not change). Are there any
>>> objections against such a procedure?
>> How will it appear in the EM? Is the status read from the extension
>> cache (so it will appear as obsolete when the cache has been updated
>> from the TER) or is it read from the ext_emconf.php file, in which case
>> it will not appear as obsolete as long as it is not updated (and it will
>> not appear as needing an update because the version hasn't changed)?
> 
> Indeed the extension will still show "alpha" state when being downloaded
> to a site. The change in the database would only affect the display on
> typo3.org - and still I am not 100% if it would work at all.
> 
> I think the problem is that people might still think that these
> extensions are neccessary, so they should see it in the EM upon download.
> 
> However, what I do not want to do is to upload > 40 extensions just
> because of this tiny problem. If someone else wants to do it, I could
> give him temporary access for all csh_* extensions and let him do it.
> 
> The other alternative is to simply delete all those extensions. Who
> needs them anyway?!
> 
> - michael

delete will be much work - in TER all versions of extensions are still 
there, and not easy to detect.
There is a possibility in DB which is used by security team to mark 
them, so they don't appear on t3.org or in EM when search for, that's 
the way i would suggest.

vg Steffen




More information about the TYPO3-dev mailing list