To understand what the deprecation of SCA's means, one has to understand what they are and why they are used. And to describe this, we need to start at the very beginning, the definition of a plugin which is split into two different calls to static methods.
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin()\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin()The naming of those methods is bit irritating as registerPlugin does indicate that it needs to be called
| <?php | |
| declare(strict_types=1); | |
| namespace FriendsOfTYPO3\Rector\TYPO3\Rector\Extbase; | |
| use Rector\Core\Rector\AbstractRector; | |
| use Symplify\RuleDocGenerator\ValueObject\RuleDefinition; | |
| use Symplify\RuleDocGenerator\ValueObject\CodeSample\CodeSample; | |
| use PhpParser\Node\Param; |
| <?php | |
| /** @see https://www.jetbrains.com/help/phpstorm/ide-advanced-metadata.html */ | |
| namespace PHPSTORM_META { | |
| override(\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(0), type(0)); | |
| override(\TYPO3\CMS\Extbase\Object\ObjectManagerInterface::get(0), type(0)); | |
| } |
| # Upload | |
| rsync -av -e "ssh -A JUMP_HOST ssh" FILE_TO_SEND DEST_HOST:/home/gareth/ | |
| # Download | |
| rsync -av -e "ssh -A JUMP_HOST ssh" DEST_HOST:~/FILE_TO_DOWNLOAD ~/Downloads/ |
Dear members of the development team, CU a few days ago I commented the announcement, that Neos and Flow get rid of "TYPO3" as part of their names, as follows:
Removing "TYPO3" from Neos and Flow makes it easier to quietly abandon these products. \o/
Additionally to this tweet I had a small twitter conversation resulting in this tweet:
This is statement regarding my tweet:
Still don't get that #TYPO3 Surf Hype. It's a NIH product and resembles everything we try to avoid in the community recently.
People started asking me about what I use instead, what NIH means and why exactly the problem with TYPO3.Surf is. As twitter only allows 140 chars, I decided to shortly write down this gist.
This document gives an overview of the issues I see in the current composer implementation in TYPO3. First of all I'll write it in the form of user stories and afterwards write an actual text.
As a developer I want to:
[UPDATE] 19.04.17
TemplaVoila 7.6 is available on packagist and github.
https://packagist.org/packages/schnitzler/templavoila
https://github.com/alexanderschnitzler/templavoila
[UPDATE] 16.08.16
There is a crowdfunding campaign to keep the development of TemplaVoilà alive.
To be found here: https://www.templavoila.support/typo3-76/
tl;dr
EXT:templavoilaplus? Does anybody know why this #typo3 ext can not use the key EXT:templatevoila? Did we miss something? 😳
https://twitter.com/t3extensions/status/842975264942379008
There is a short answer and a long one.