einpraegsam

Github actions gives you the possibility to run some code after a special trigger (e.g. a push into a repo) is recognized.
This can be used for running tests or - in our case - to deploy the software to TYPO3 TER when a new tag is pushed.

1) First of all, you should login on extensions.typo3.org and create some access token (API Token) to use the new REST API of typo3.org
to publish your extensions (see https://github.com/TYPO3/tailor#prerequisites for some more help on this).

2) After that you can add three secret tokens in your github repository 
(see https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-environment for some more details):
TYPO3_API_USERNAME (your username for FE-login on typo3.org)
TYPO3_API_PASSWORD (your password for FE-login on typo3.org)

einpraegsam

$GLOBALS['TYPO3_CONF_VARS']['HTTP']['verify'] = false;

einpraegsam

<?php
declare(strict_types=1);
namespace Vendor\Sitepackage\PageHandler;

use Psr\Http\Message\ResponseInterface;
use Psr\Http\Message\ServerRequestInterface;
use TYPO3\CMS\Core\Error\PageErrorHandler\PageErrorHandlerInterface;
use TYPO3\CMS\Core\Http\RedirectResponse;
use TYPO3\CMS\Core\Http\Uri;
use TYPO3\CMS\Core\Site\Entity\Site;

einpraegsam

<?php
declare(strict_types=1);
namespace Vendor\Extension\Factory;

use GuzzleHttp\Psr7\Uri;
use TYPO3\CMS\Core\Exception\SiteNotFoundException;
use TYPO3\CMS\Core\Http\Request;
use TYPO3\CMS\Core\Http\ServerRequest;
use TYPO3\CMS\Core\Routing\SiteMatcher;
use TYPO3\CMS\Core\Site\Entity\Site;

einpraegsam

<?php
declare(strict_types=1);
namespace In2code\In2template\Middleware;

use CodeZero\BrowserLocale\BrowserLocale;
use CodeZero\BrowserLocale\Filters\LanguageFilter;
use In2code\In2template\Utility\ObjectUtility;
use Psr\Http\Message\ResponseInterface;
use Psr\Http\Message\ServerRequestInterface;
use Psr\Http\Server\MiddlewareInterface;

einpraegsam

<?php
namespace In2code\In2template\ViewHelpers\JsonLdSchema;

use TYPO3\CMS\Fluid\Core\ViewHelper\AbstractViewHelper;

/**
 * Class AbstractJsonLdSchemaViewHelper
 */
abstract class AbstractJsonLdSchemaViewHelper extends AbstractViewHelper
{

einpraegsam

# Read: Show real path in sys_file_storage
select name, uid, ExtractValue(configuration, '//T3FlexForms/data/sheet[@index="sDEF"]/language/field[@index="basePath"]/value') path from sys_file_storage where uid > 0 

# Write: Set a new value (in this case a detail pid) in FlexForm of a tt_news plugin
UPDATE tt_content SET pi_flexform = UpdateXML(pi_flexform, '//T3FlexForms/data/sheet[@index="s_misc"]/language/field[@index="PIDitemDisplay"]/value', CONCAT('<value index="vDEF">', 123, '</value>' )) WHERE uid=11107

einpraegsam

Hier findest du 10 Anzeichen dafür, dass du vielleicht zu viel für 
deine TYPO3 Extension bezahlt hast lieber Kunde:


1. Das Icon der für dich entwickelten Extension ist das schwarz/graue TYPO3-Zeichen. 
Datensätze in der Listenansicht haben komischerweise alle ein E-Symbol 
und das obowhl die Extension gar nicht mit E anfängt.

2. Der Status der Extension steht schon seit über einem Jahr 
auf 0.0.0 alpha.

einpraegsam

<T3DataStructure>
	<meta>
		<langDisable>1</langDisable>
	</meta>
	<sheets>
		<main>
			<ROOT>
				<TCEforms>
					<sheetTitle>LLL:EXT:in2studyfinder/Resources/Private/Language/locallang_db.xlf:listView</sheetTitle>
				</TCEforms>

einpraegsam

<?php
namespace TYPO3\CMS\Core\Utility;

use GuzzleHttp\Exception\RequestException;
use TYPO3\CMS\Core\Core\ApplicationContext;
use TYPO3\CMS\Core\Core\ClassLoadingInformation;
use TYPO3\CMS\Core\Crypto\Random;
use TYPO3\CMS\Core\Database\ConnectionPool;
use TYPO3\CMS\Core\Http\RequestFactory;
use TYPO3\CMS\Core\Service\OpcodeCacheService;