7. Templating

Question 1

7.1.1 You want to create a website with four different output formats, e.g. HTML, print version, iPhone and plain text. What do you need? (1)

1. Four different servers with a TYPO3 installation on each.
2. Four TYPO3 installations on one server.
3. Four PAGE objects with different typenum.
4. Four pages in a TYPO3 installation that contain a root template.
5. Four root templates.

Answer 1

Therefore, the correct answer is 3.

Question 2

7.1.2 When you access your website in the frontend, the following error message appears: “No Template found!”. Why is this? (1)

1. No HTML template was specified.
2. The HTML template is read-only.
3. No TypoScript root template was specified.
4. The path to the HTML template is not correct.
5. No extension template was created.

Answer 2

Therefore, the correct answer is 3.

Question 3

7.1.3 When you access your website in the frontend, the following error message appears: “The page is not configured!” Why is this? (1)

1. No HTML template was specified.
2. No TypoScript root template was specified.
3. No extension template was created.
4. There is no PAGE object.
5. The “Rootlevel” check box in the root template was not activated.

Answer 3

Therefore, the correct answer is 4.

Question 4

7.1.4 When you access your website in the frontend, the following error message appears: “The page is not configured!” Which code fixes the error? (4)

1. The following TypoScript code:
page = PAGE
2. The following TypoScript code:
seite = PAGE
3. The following TypoScript code:
page = PAGE
page.10 = HTML
4. The following TypoScript code:
page = PAGE
page.50 = TEXT
page.50.value = Hello world
5. The following TypoScript code:
page = PAGE
page.10 = TEMPLATE
6. The following TypoScript code:
website = PAGE
website.foobar = 37

Answer 4

Therefore, the correct answers are 3, 4, 5 and 6.

Question 5

7.1.5 Is it possible to build a website without an HTML template? (1)

1. No, this is not possible. Every website requires at least one HTML template.
2. Yes, if you use TypoScript.
3. No, you need the “Themes” or “Grid Elements” extension at least.
4. Yes, but only if the site has no HTML output.
5. No, ever since the HTML content object was removed in TYPO3 version 6.0, this is no longer possible.

Answer 5

Therefore, the correct answer is 2.

Question 6

7.1.6 How can you display a site name in the title bar of the browser? (1)

1. The Install Tool contains a parameter for this purpose:
   $TYPO3_CONF_VARS[‘SYS’][‘sitename’]
2. You can enter the site name in the “Basic Configuration” view in the Install Tool.
3. By using Sitetitle in the “Template” module to specify the title in the TypoScript template.
4. By using the TypoScript option config.pageTitle = ….
5. By using the TSconfig option config.pageTitle = ….

Answer 6

Therefore, the correct answer is 3.

Question 7

7.1.8 What can you do, if a TypoScript template is growing increasingly bulky? (2)

Condition: You have created a TypoScript template, filled all required markers and subparts with content and configured all extensions in use. As a consequence, your template is growing increasingly bulky, which makes it hard to read, debug, review.

1. You can separate the TypoScript template into several files and include these in your master template.
2. You can separate the TypoScript template into several templates and include them in the Include basis template section.
3. You remove all line breaks in the TypoScript code to reduce the amount of data.
4. You can use the “MinimizeTypoScript” extension to compress the TypoScript code.
5. You can export the same TypoScript command code into constants to save space.

Answer 7

Therefore, the correct answers are 1 and 2.

Question 8

7.1.9 Why is it not possible to edit or create the file fileadmin/filename.text via “FILE -> Filelist” module by default? (1)

1. Only image and PDF files can be uploaded in the “FILE → Filelist” module.
2. You first have to permit the use of *.text files in the Install Tool.
3. The “FILE → Filelist” module cannot be used for this purpose either; you have to use the “Quixplorer” extension.
4. You first have to permit the use of *.text files in the Page TSconfig.
5. The file extension can only have two characters, e.g. filename.ts.

Answer 8

Therefore, the correct answer is 2.

Question 9

7.1.10 You want to include a complete directory of TypoScript files with an include statement; is this possible, and, if yes, how? (1)

1. No, it is not possible. You can only use an include statement to include individual files.
2. Yes, by using <INCLUDE_TYPOSCRIPTDIR: source=”EXT:myext/Typoscript”>.
3. Yes, by using <INCLUDE_TYPOSCRIPT: source=”DIR:EXT:myext/Typoscript”>.
4. Yes, by using <INCLUDE_TYPOSCRIPT: source=”DIR:myext/Typoscript”>.
5. Yes, by using <INCLUDE_TYPOSCRIPT: sourcedir=”EXT:myext/Typoscript”>.

Answer 9

Therefore, the correct answer is 3.

Question 10

7.1.11 By default, it is not possible to create, edit or upload PHP files in the “FILE -> Filelist” module. Why is this? (2)

1. You first have to permit the use of PHP files in the Install Tool, using the option
   $TYPO3_CONF_VARS[‘SYS’][textfile_ext]
2. These actions are prohibited for safety reasons, and you cannot change this behavior.
3. You first have to permit the use of PHP files in the Install Tool, using the option
   $TYPO3_CONF_VARS[‘SYS’][fileDenyPattern]
4. You first have to permit the use of PHP files in the Page TSconfig.

Answer 10

Therefore, the correct answers are 1 and 3.

Question 11

7.1.12 You want to use TypoScript template “A” for the current page and template “B” for all the subpages of the current page. What is the best way to proceed? (1)

1. You assign template “A” to the current page, and template “B” to each subpage.
2. You assign template “A” to the current page, and then assign template “B” in the “Template on next Level” setting.
3. You assign template “A” to the current page, and use a condition to assign template “B” to the subpages.
4. You assign template “B” to all pages and use a condition to assign template “A” to the current page.

Answer 11

Therefore, the correct answer is 2.

Question 12

7.2.1 What is the name of the TypoScript content object you need if you want to use Fluid to generate the page template? (1)

1. TEMPLATE
2. FLUID
3. FLUIDTEMPLATE
4. PAGETEMPLATE
5. FLUID_TEMPLATE
6. FLUID_ENGINE

Answer 12

Therefore, the correct answer is 3.

Question 13

7.2.2 Is it possible to access the page properties of a page template that was embedded using FLUIDTEMPLATE? (1)

1. No, that is not possible for security reasons.
2. No, not directly. You can access it via TypoScript and display the result in the template.
3. Yes, by using {pageproperties}.
4. Yes, by using {data}.
5. Yes, by using .

Answer 13

Therefore, the correct answer is 4.

Question 14

7.2.3 Which of the following Fluid ViewHelpers do not exist? (2)

1. <f:if>
   </f:if>
2. <f:base>
   </f:base>
3. <f:render>
   </f:render>
4. <f:section>
   </f:section>
5. <f:else>
   </f:else>
6. <f:format.raw>
   </f:format.raw>
7. <f:switch>
   </f:switch>
8. <f:html>
   </f:html>
9. <f:format.translate>
   </f:format.translate>
10. <f:comment>
    </f:comment>

Answer 14

Therefore, the correct answers are 8 and 9.

Question 15

7.2.4 Replace ??? in the code below, so that content is displayed as {content} in a Fluid template? (1)
page = PAGE
page {
  10 = FLUIDTEMPLATE
  10 {
    file = fileadmin/templates/Home.html
    ???
}

1. variable.content < styles.content.get
2. variables.content < styles.content.get
3. subparts.content < styles.content.get
4. marks.content < styles.content.get
5. variables.10.content < styles.content.get
6. content < styles.content.get

Answer 15

Therefore, the correct answer is 2.

Question 16

7.1.7 The following script aims to produce a debug output on the screen. Why is it not functioning by default? (1)

page = PAGE

page. 10 = TEXT
page. 10.value = Hello world!
page. 10.debugData = 1

1. The syntax is wrong, it should be page.10.stdWrap.debugData.
2. The output is always written to a log file and not displayed on screen.
3. You first have to enter the IP address of the client requesting the page in the Install Tool.
4. The function mentioned above only works for local installations. If the TYPO3 instance is on the Internet, the display of debug data does not work.
5. The output is shown in the backend in module “WEB → Info”, rather than on screen.

Answer 16

Therefore, the correct answer is 3.