Chapter 6 II (6.5-6.8)

Page TSconfig

User TSconfig

In RTE extension settings

TypoScript-Setup

TypoScript constants

Page TSconfig

User TSconfig

In the user management

TypoScript setup

TypoScript constants

admPanel

options

mod

setup

user

auth

default

settings

override

overrule

In the User TSconfig

In the Page TSconfig

In the TypoScript setup

mod.web_list.hideTables = tabName1,tabName2,tabName3,..

mod.hideTables = tabName1,tabName2,tabName3,...

mod.hide = tabName1,tabName2,tabName3,...

mod.list.hideTables = tabName1,tabName2,tabName3,...

You memorize the name and specify the corresponding ID in the phpMyAdmin extension.

You enter the following code in the User TSconfig:
options.pageTree.showPageIdWithTitle = 1

You move the mouse over the page icon in the page tree and wait for the ID to appear as a tool tip.

You click the page (in Listview or Pageview), and find the ID on the top right.

You select Web > Info, click on a page and choose the Pagetree overview entry from the pull down menu. You then receive a list with page information on the current page and its subpages. The ID is also listed there.

You can activate displaying the IDs via the page tree.

In the setup area of the TypoScript root template.

In the Page TSconfig of the admin user

On the page containing the root template

On the page whose ID=0

In the Language module in the backend.

Click the List module, select the page with the TYPO3 symbol and then create a new Website language data record.

Click the Page module, select the page with the TYPO3 symbol and then create a new Website language content element.

Click the Info module, select the root page and then create a new language data record.

Select Language menu item in the Extension Manager.

In the Page module

In the List module

In the Info module

In the Template module

In the Language module

You can change the language easily in the User Settings module.

You have to add the language in the Language module.

You have to check in the Language module to find out which translations you need to transfer because they are still in the repository.

You have to transfer the new translations to your server from the repository in the Language module.

You have to activate the use of further languages in the Install Tool.

It is saved in the database in the sys_language table.

In the typo3temp/ directory

In the typo3conf/l10n/ directory

In the typo3/languages/ directory

The language information remains on the server and is not stored locally. The system only stores locally which translations are required by the installation.

You have to install the language extension.

You add a GET parameter to the URL; usually this is L.

You have to store the appropriate configuration in the TypoScript setup of the root page.

You have to introduce the required language via the URL as http://mytypo3domain.de/language/.

You have to configure the required languages in the Page TSconfig.

By translating all contents.

By hiding the page.

You select Hide default translation of page in the page properties.

By selecting Hide page if no translation for current language exists in the page properties.

By selecting Hide permanent in the page properties.

By entering defaultLanguageFlag and defaultLanguageLabel in the TypoScript setup.

By enterin defaultLanguageFlag and defaultLanguageLabel in the Page TSconfig.

In the DefaultLanguage section of the Install Tool.

In the Language tab of the root page, in the page properties.

Unfortunately that is not possible, English is always the default language.

You use the following Install Tool setting to change the backend:
$TYPO3_CONF_VARS['BE'][forceCharset]

You use the following Page TSconfig setting to change the backend:
config.forceCharset

To allow files to be given UTF-8 file names, the following settings are necessary in the Install Tool:
$TYPO3_CONF_VARS['BE'][UTF8filesystem]

You have to set the following TypoScript option for the frontend output:
config.metaCharset = utf-8

You set the following TypoScript option for the frontend output:
config.additionalHeaders = Content-Type: text/html;charset=utf-8

It is the administrator’s control center for user settings.

It can be used to configure TYPO3 in the backend.

The panel can be used to analyze the frontend output.

It provides administrators with an admin area in the frontend.

The panel controls frontend editing.

Once you have activated frontend editing, an administrator can use the panel to monitor the entry of contents.

You enter config.admPanel = 1 in the setup of the root template.

You enter config.admPanel = 1 in the User TSconfig.

You enter admPanel.enable.edit = 1 in the setup of the root template.

You enter admPanel.enable.edit = 1 in the User TSconfig.

By means of a setting in the user’s user settings.

You change the time on your desktop computer.

You change the time on the server.

You wait until 8:00 the next day.

You simulate the correct time in the backend.

You simulate the correct time in the Admin Panel.

Every content form contains the Disable Rich Text Editor switch.

You deactivate the extension that embeds the RTE.

You install a new extension, e.g. tinyRTE.

You add the following TypoScript code line in the Page TSconfig:
RTE.default.disabled = 1

You call up the backend using the &no_rte GET parameter.

The display of a table in the phpMyAdmin extension

The table output of a frontend plugin.

All options of an entry form in the backend are displayed on a page (instead of on tabs).

The display of one single table in the Web > List module.

The display of one single table in the Web > Page module.

You have to make the appropriate settings in the Page TSconfig.

You can make the settings in the Single Table View.

You can extend the showBEuserInfo option in the Install Tool correspondingly.

You require a special extension to display additional information here.

You can make the settings in User settings accordingly.

That is not possible, you have to edit each page individually.

You first have to install a suitable extension.

You can use TypoScript to create a script that performs the change
in one procedure.

You can do this in the Single Table View.

You can do this in the Page module.

You use the Delete Multiple Pages extension.

For safety reasons, you can only delete one page at a time.

You right-click the corresponding page and then select Delete.

You use the clipboard.

You have to change the User Settings to allow deleting more than one page at once.

Recursive deletion is not possible in TYPO3 for reasons of safety.

The ability to delete recursively has to be configured in User settings.

Recursive deletion is only possible using a DELETE database command.

The recursive delete function has to be activated in the User TSconfig.

Recursive deletion does not work in the page tree, but only in the Web > List module.

This is only possible if the config.baseURL TypoScript key is set to the https version of the website.

If the link is generated in TypoScript, the following configuration is necessary:
1.NO.protocol = https

This is only possible by installing a suitable extension.

You select the https:// option in the Use protocol field in the page properties.

It is necessary to select the Secure Site page type for the specific page.

Using Page TSconfig:
TCEMAIN.pages.protocol = https

No, there is only a recycling bin for data records (such as pages and content elements).

Yes, you can switch it on in the Page TSconfig:
config.file.recycler = true

Yes, but you have to install a suitable extension from the TER.

Yes, you can create a _recycler_ folder in the File > Filelist module.

Yes, you can configure this by selecting the Use recycler for file checkbox in the user settings.

Only in the Admin Tools > User admin module.

Backend users are only created on the page with ID = 0.

Backend users are only created on the page with the root flag.

Backend users can be created on all pages.

Backend users can be created on all pages of the Folder type.

Backend users can be created on all pages of the Backend User Section type.