GoConqr hat ein neues Design! Sag uns, wie es dir gefällt.

Quiz

6. TypoScript

Ma Hi 25 Fragen

Quiz starten

Fragen in diesem Quiz (25)

  1. 1The size and complexity of a TypoScript setup template that is maintained through the backend is growing rapidly and becomes confusing. What can you do to simplify working with it? (1)
    1. ADivide the TypoScript template into several files and include/import them into your main template.
    2. BUse gzip to compress the TypoScript files to reduce their size.
    3. CRemove all line breaks in the TypoScript code to reduce its size.
    4. DMove the TypoScript setup template to the TypoScript constants field to save space.
    5. EUse the Optimize TypoScript function to remove redundant and unused TypoScript code.
  2. 2The error message “No TypoScript record found!” comes up when you access the frontend of a TYPO3 site. What causes this issue? (1)
    1. ANo HTML template was specified.
    2. BThe TypoScript record for the site is not stored in the root page (page ID 0).
    3. CThe path to the HTML template is not correct.
    4. DNo TypoScript record has been specified for the root page of the site.
  3. 3The error message “No page configured for type=0.” comes up when you access the frontend of a TYPO3 site. What causes this issue? (1)
    1. ANo HTML template was specified.
    2. BThe Rootlevel toggle switch in the TypoScript record is not enabled.
    3. CNo valid PAGE object is defined.
    4. DThe page does not contain any content elements.
    5. EThe site configuration is missing.
  4. 4How do you import/include a TypoScript configuration file in your TypoScript setup? (2)
    1. ABy a right mouse-click on the file in the File → Filelist backend module and selecting Include TypoScript records.
    2. BBy using the following TypoScript instruction to include the file (one line):
      @INCLUDE_TYPOSCRIPT FILE='EXT:site/Configuration/TypoScript/setup.typoscript'
    3. CBy using the following TypoScript instruction to include the file (one line):
      <INCLUDE_TYPOSCRIPT:
      source="FILE:EXT:site/Configuration/TypoScript/setup.typoscript">
    4. DBy using the following TypoScript instruction to include the file (one line):
      @import 'EXT:site/Configuration/TypoScript/setup.typoscript'
  5. 5What are possible methods of including all TypoScript configuration files, that are stored in a directory, into your system? (2)
    1. AUse the following statement to include the directory (e.g. extension “sitepackage”):
      <INCLUDE_TYPOSCRIPT: directory="EXT:sitepackage/Configuration/Typoscript/">
    2. BUse the following statement to include the directory (e.g. extension “sitepackage”):
      <INCLUDE_TYPOSCRIPT: source="DIR:EXT:sitepackage/Configuration/Typoscript/">
    3. CUse the following statement to include the directory (e.g. extension “sitepackage”):
      @include 'EXT:sitepackage/Configuration/TypoScript/'
    4. DUse the following statement to include the directory (e.g. extension “foobar”):
      @import 'EXT:foobar/Configuration/TypoScript/'
    5. EUse the following statement to include the directory (e.g. extension “foobar”):
      @require 'EXT:foobar/Configuration/TypoScript/'
  6. 6Consider the following two instructions to import/include TypoScript configuration files. Which statements are correct? (4)
    <INCLUDE_TYPOSCRIPT: source="DIR:EXT:sitepackage/Configuration/Typoscript/Foobar/">
    @import 'EXT:sitepackage/Configuration/TypoScript/Foobar/'
    1. AYou can not use both, the old “<INCLUDE_TYPOSCRIPT>” and the new “@import” syntax at the same time.
    2. BMultiple files stored in a directory are imported in alphabetical order when importing the directory.
    3. CFiles included by the “@import” statement can contain further “@import” statements.
    4. DThe “@import” statement lets you import files and directories.
    5. EThe “<INCLUDE_TYPOSCRIPT>” statement supports relative paths if the statement is used in a file.
    6. FThe “@import” statement supports the “*” character as a wildcard.
  7. 7The following @import statement in TypoScript does not work. What causes the problem? (1)
    @import fileadmin/Configuration/TypoScript/setup.typoscript
    1. AThe keyword “FILE:” is missing. The line shoud read:
      @import FILE:fileadmin/Configuration/TypoScript/setup.typoscript
    2. BThe @import statement was removed in TYPO3 v13 and can’t be used anymore.
    3. CYou can not store TypoScript configuration files in the fileadmin/ path. You must use an extension, for example:
      @import EXT:sitepackage/Configuration/TypoScript/setup.typoscript
    4. DSingle or double quotes are missing. The line should read:
      @import "fileadmin/Configuration/TypoScript/setup.typoscript"
  8. 8You changed a setting in the TypoScript Object Browser. Where does TYPO3 store the new value? (2)
    1. AAt the start of the TypoScript “Setup” template.
    2. BAt the end of the TypoScript “Setup” template.
    3. CAt the start of the TypoScript “Constant” template.
    4. DAt the end of the TypoScript “Constant” template.
    5. EIn the config/system/settings.php file.
  9. 9Which backend module or utility reports possible TypoScript syntax errors and can help locating the cause of the issue? (1)
    1. AIn Site Management → TypoScript, the TypoScript Overview submodule.
    2. BIn Site Management → TypoScript, the Active TypoScript submodule (TypoScript Object Browser).
    3. CIn Site Management → TypoScript, the Included TypoScript submodule.
    4. DIn Admin Tools → Environment, the Environment Status submodule.
    5. EThe Admin Panel.
  10. 10What is the impact of the following two lines of TypoScript code in the constants section? (2)
    # cat=foobar/ctext/a; type=color; label=text color
    mytextcolor = red
    1. ATYPO3 ignores the first line because of the comment # character.
    2. BThe value red is assigned to the constant mytextcolor.
    3. CThe value red is assigned to the variable foobar.ctext.a.
    4. DThe Constant Editor shows a selection field that allows backend users to select a colour.
    5. EThis first line results in an error as # is an invalid character in TypoScript constants.

Informationen

Beschreibung
TYPO3 TYPO3 CI v13 Quiz am 6. TypoScript, erstellt von Ma Hi am 10/10/2025.
Autor
Ma Hi
Sprache
Deutsch
Aufrufe
0
Schlagwörter
typo3 ci v13typo3
Bewertung
Noch keine Bewertungen
Bewerte dieses Quiz
Bewerte dieses Quiz

Feedback

Worum geht es?

Wie gefällt dir das neue Design?

Dein Eindruck