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

Michael Stucki michael at typo3.org
Wed Feb 18 16:46:04 CET 2009


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
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/




More information about the TYPO3-dev mailing list