Zusammenfassung der Ressource
Frage 1
Frage
Which of the following rules applies to the extension key? (1)
Antworten
-
The company name must not be part of the extension key
-
The extension key must start with either tt_ or tx_
-
The minimum length of an extension key is 3 characters
-
The extension key must be registered at typo3.org
-
The extension key must not start or end with a number or underscore
Frage 2
Frage
What is the purpose of ext_localconf.php file? (2)
Antworten
-
This file is loaded after the file LocalConfiguration.php and can therefore extend the global configuration
-
This file contains configuration which are predominantly used in the backend
-
This file contains configuration which are predominantly used in the frontend
-
According to TYPO3/Extbase conventions, this file contains TCA settings
-
TypoScript can be copied from the file setup.typoscript to ext_localconf.php to exclude it from caching
Frage 3
Frage
Which extension states are officially supported and can be defined in file ext_emconf.php? (2)
Antworten
-
alpha
-
excludeFromUpdates
-
warning
-
patched
-
hidden
Frage 4
Frage
What is the application context in TYPO3? (2)
Antworten
-
The application contexts allows developers to switch between PHP versions
-
Certain TYPO3 settings can be configured in specific application contexts
-
TYPO3 supports the contexts authored, proofread, translated, reviewed and published by default
-
TYPO3 extensions can react differently, depending on the configured application context
Frage 5
Frage
Where can you set the application context? (1)
Antworten
-
In the Install Tool
-
In the file ext_tables.php
-
In the file ext_localconf.php
-
As an environment variable
-
In TypoScript
Frage 6
Frage
How can a “live” system and a “staging” system be differentiated, if both have the application context
Production? (1)
Antworten
-
This is (currently) technically not possible
-
By using “sub-contexts”, e.g. Production/Live and Production/Staging
-
By using the environment variable TYPO3_SUBCONTEXT
-
By using numbering such as TYPO3_CONTEXT_01
Frage 7
Frage
What should be considered when adding multiple instances of an extension plugin to a page? (1)
Antworten
-
A plugin can only be used once on a page
-
Each plugin can be configured individually by using TypoScript
-
Each plugin can be configured individually by using its own FlexForm
-
A unique number must be configured in the content element’s properties to distinguish between each instance
Frage 8
Frage
How can a field in the backend be hidden from an editor? (2)
Antworten
-
To be able to hide a field, its name has to end in _exclude
-
The property exclude in the model should be set to 1
-
The exclude property for this field in the TCA must be set to true
-
The field can be hidden in settings of the backend user group
-
The field can be hidden in settings of the backend user
Frage 9
Frage
What is required to extend the page properties with a custom field? (2)
Antworten
-
A file pages.php in directory Configuration/TCA/Overrides/
-
An entry in file ext_localconf.php
-
An entry in file ext_tables.sql
-
An entry in file Configuration/TypoScript/setup.typoscript
-
An entry in file ext_emconf.php
Frage 10
Frage
Which statements about extension icons are correct? (2)
Antworten
-
To display an extension icon in the Extension Manager, the extension needs to be uploaded to the TER first
-
An SVG image file stored as Resources/Public/Icons/Extension.svg is shown in the Extension Manager automatically
-
Extension icons need to be registered using the ExtensionIconRegistry class
-
Extension icons should be stored in Resources/Private/Assets/ per convention
-
Officially supported image types for extension icons are GIF, PNG and SVG