Which backend functions provided by the TYPO3 core by default can you use to check extensions? (3)
Scan extensions for known security vulnerabilities
Check if an extension changes the global TCA array $GLOBALS['TCA'] in an ext_tables.php file
Check of installed extensions are compatible with the currently installed version of TYPO3
Scan extensions for usage of deprecated or outdated TYPO3 API calls
Run performance tests against all currently installed extensions
Scan extensions for PSR-2 coding standard violations
Which statement about the Extension Scanner is correct? (1)
The Extension Scanner can be executed as a Scheduler task to scan for security vulnerabilities
The Extension Scanner uses static code analysis to find usages of deprecated core functions
Only extensions with unit tests can be scanned with the Extension Scanner
The TYPO3 instance must run in the “development” context to execute the Extension Scanner
The Extension Scanner writes the results to the deprecation log
How do you instruct the Extension Scanner to ignore certain parts of your extension code? (2)
Add the extension key to the “ignore list” in the Install Tool
Add the .gitignore file to the root directory of the extension
Add the annotation @extensionScannerIgnoreLine to your code to ignore certain lines
Add the annotation @extensionScannerIgnoreFile to your code to ignore an entire file
Set the property extras.scanner.ignore to true in the composer.json file
What exactly does the “check for broken extensions” in the TYPO3 backend (Install Tool) do? (1)
It runs a static code analysis against all currently installed extensions to detect PHP syntax errors
Once enabled, it generates an email to notify administrators if an extension stops working unexpectedly
It checks ext_localconf.php and ext_tables.php files of all extensions to make sure they can be loaded without breaking the system
It checks if all system extensions are up-to-date and contain valid PHP code
You installed an extension you developed on a new system and it produces errors that indicate problems with the PHP settings. What do you do? (1)
You create a PHP file with the function phpinfo() and store it one level above the DocumentRoot. TYPO3 automatically detects this file and displays the PHP settings in the backend
You execute the following command on the command line to access and review the current PHP settings: ./vendor/bin/typo3 system:phpinfo.
You access the PHP info page http://example.com/typo3/phpinfo using your browser (InstallTool password required)
You look-up the PHP settings and installed/enabled PHP modules under ADMIN TOOLS → Environment → PHP Info
