| <?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/ |
| <?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; |
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
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:
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.
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.
Well, earlier this day I read an interview with Robert Lemke on the website of the german PHP magazine about the split off of Neos.
There is one quote from the article I used in one of my tweets. https://twitter.com/alex_schnitzler/status/600672348900065280 It says "Neos und TYPO3 haben sich zu unterschiedlichen Produkten entwickelt." which can be translated to "Neos and TYPO3 have evolved into different products." and I commented it as such "Falsch, Neos wurde nicht als Nachfolger für TYPO3 entwickelt." which means "Wrong, Neos has not been developed as a successor of TYPO3."
Later that day I received a direct message with the hint, that Neos actually has been developed as a successor of TYPO3. It's the moment I realized (again) that 140 chars maybe really are made for telling people how awesome your food is. However, I never intended to say that Neos wasn't planned to be the successor of TYPO3 – the Berlin Manifesto would p
[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