typo3 manual info module.pdf

7/29/2019 TYPO3 Manual Info Module.pdf

1/9

Web > Info module

The idea of the Web>Info module is to be a host module for backend applications that wish to present information / analysis of

pages or branches of the page tree. This could be website statistics, caching status information etc.

Details:

Conceptually the Web>Info module is different from the Web>Functions module only by primarily showing information rather

than offering functionality. It is up to extension programmers to decide in which of these two modules they want to insert

functionality.

The Web>Info module as provided by the core is an empty shell. It provides an API that extensions can use to attach function

menu items to the Info module. Here you see the "Page TSconfig" overview from the extension "info_pagetsconfig".

See also:

Web > Functions module

More about Web>Info module framework

Web > Info module: Pagetree Overview

The Pagetree Overview shows information related to pages for a branch of the page tree. This includes start- and stop-times,

cache settings etc.

One of the features of the Pagetree Overview module is that you can see what types of records are found on pages in a branch.

Here record counts are shown for a page tree branch 2 levels down.

See also:


2/9

Web > Info module / Basic Settings

Web > Info module / Record Overview

Web > Info module / Cache and Age

Web > Info module / Page Hit statistics

Web > Info module: Basic Settings

Displays a selection of fields from page records which are regarded as foundational settings for pages. That includes aliases,

start- and stop times, access restriction information etc.

Details:

The Basic Settings view resembles the Cache and Age view quite a lot. They are different only by the selection of fields they

show.

Batch editing page fields

You will find multiple edit-icons around the interface. All edit icons in head lines will bring you to an editing dialog where you can

change exactly that field for all listed tables! Very useful for batch-editing of say all "Start" times.

If you click the edit icon at the ID numbers of pages you will get straight to the regular editing of a whole page record.

The Basic Settings view offers a very convenient overview of page aliases, start times and access restriction settings in the tree

branch.

If you click an edit-icon in the header you will be able to edit that field for all listed pages.


3/9

See also:

TYPO3 Core / The Web>List module

Web > Info module / Cache and Age

Web > Info module / Pagetree Overview

Web > Info module: Record Overview

Record overview gives you an indispensable overview of the distribution of records in the page tree. Each database table in thesystem is represented with a column and for each page you can see the number of records from that table located on the page.

Details:

Notice: Be careful with the level-setting. A high level-setting may cause the module to respond very slowly if there are many

pages and many records in the database as well!

Tree stop?

Notice the red "+" next to a page in the page tree? This is due to a setting for that page record which means that the page tree

will not expand for this page. Typically this is set for protection when there are a large amount of subpages underneath

(hundreds of pages typically). If you click the icon/title the overview will jump to make this page the new root of the overview.

You can easily see the distribution of Content Elements on a page. You can also see where Template Records - and basically any

record! - are located in the page tree!

See also:


Page / Stop page tree

Web > Info module: Cache and Age

Displays a selection of fields from page records related to page caching and time settings.


4/9

The "Cache and Age" view.

Here you see the "TSconfig" column. The overview exposes that these two pages include some Page TSconfig code!

See also:

Web > Info module / Basic Settings


Page / TSconfig

Web > Info module: Page Hit statistics

Displays website hit statistics for a branch of the page tree. Based on the simple, internal MySQL statistics table which records

page impressions and sessions only.

Details:

Notice: This function requires the extension "Simple hit statistics" (sys_stat) to be installed. Also you must configure TypoScript

to register page hits in the statistics database table.

Web > Info module: Localization overview

Gives an overview of which pages in the page tree are translated to the system languages installed.

Details:

The overview uses colors to signal the availability and fall back situation for a given page. Here is a description for each color

code:

Green background: Page is translated and viewable in this language. For translations it means that an active page overlay

record is present.

Red background: Page cannotbe viewed in this language and you will see an error message if you try. Menus should

automatically filter out links to pages with this translation.

Gray background (not available for default language): Page will fall back to the specified fallback mode for content.Depends on configuration. (sys_language_mode = content_fallback is recommended for most flexible fallback,

sys_language_mode = strict will prevent this and issue an error instead!)

The pages "Localization settings:"

It is the "Localization settings" of the page record that determines the modes above. In the column of the default translation


5/9

each of these settings are represented by a "N" (Hide page if no translation for current language exists) or a "D" (Hide default

translation of page).

As you can see the page "Startpage" has the N flag set and therefore any access to the german version of that page will be

blocked with an error message because there is no translation in german. By default "german access" to a non-translated page

will just show the english content.

There is also a page with the D flag ("[Dummy]"). The D flag means that the page is only available in one of the translations, in

this case Danish. So any attempt to access the page in the default language or german will show an error message.

So, when the "Localization settings" checkboxes for a page are used, you will get an error message when you try to request a

page which has been blocked. This is a feature. The trick is not to create links to those pages.

Menus generated from HMENU objects will always take "sys_language" into account and display only pages which can beaccessed for that language. But combined with the "localization settings" of pages which may block page access this becomes a

problem with pages which are nottranslated (has gray background); You might get menu items which links to non-accessible

pages.

The problem basically is that "&L=xx" is different from internal "sys_language". You would like to avoid that and to do so you

should configure "sys_language_mode" to "content_fallback". If you do that sys_language will always follow what "&L=" instructs

it to and your menus will be right. At the same time you will get the default content displayed if no translation exists (because

content selection falls back).

Finally, the number found in each column tells you how many content elements are found in the specified language.

Localization overview in the Web>Info module. Use the buttons to edit, view and create new page translation headers. Use the

regular page module to put localized content on the pages.


6/9

The "Localization settings" that affect availability of pages in the various languages.

Web > Info module: Statistic Views

You can select between three views of the statistics in the selector box; "Page hits", "Total hits", "Hits in main sections". Use the

right selector box to select the depth of the overview in the pagetree.

Details:

You can view the page hit statistics 30 days back. Each day is shown in its own column.

For each page in the page tree you can see the page hits each day as a number formatted like [page hits]/[user sessions]. So if

the number is "286/34" it means that the page had 286 page hits that day and that there were at least 34 unique visitors

(measured by at least two hits by a user accepting a cookie from the site).

This is an overview of the meaning of each view mode:

Page hits

This shows page hits/sessions for each page.

Total hits

This will show statistics for only pages that have a Template Record (with Root-flag set) on it. This means that page hits are

shown as totals for a whole website.

Hits in main sections

Will show the total number of page hits/sessions within main sections of a website. A "main section" is all subpages to a page on

the first level of a website (defined by a Template Record with the Root flag set)


7/9

Web > Info module: Page TSconfig hierarchy viewer

Allows the user to view the compiled Page TSconfig structure for a branch of the pagetree.

Details:

This viewer is indispensable for getting an overview of Page TSconfig settings as they apply to various branches in the page tree.

You can see the configuration structure of any page where all inherited Page TSconfig is parsed and the result shown. This helps

you to evaluate that the settings you have applied are actually found at the correct position in the configuration tree.

You can also see the Page TSconfig TypoScript code for each page in the root line with the viewer.

See the links for more information about what Page TSconfig is.

This is how the parsed Page TSconfig tree can look. It contains the "sum" of all the configuration code from the root line and any

default settings. This shows the whole tree but you can also select other top level objects (TLO) in the selector box in the top if

you want to limit the view to a single branch

One of the branches in Page TSconfig has the special property that it is overridden with any User TSconfig in the same object


8/9

path given for the current backend user. When you view only the "mod" TLO any user settings for the current backend user are

applied as well. Here it is evident that some additional settings must apply for the user since only "mod.SHARED.colPos_list" was

actually found in Page TSconfig (according to the "All" view in the first image).

See also:

Web > Info module / Page TSconfig content viewer

Page / TSconfig

Page TSconfig objects

Web > Info module: Page TSconfig content viewer

Displays the raw TSconfig code of all pages in the current root line including any default code.

Details:

The parsed Page TSconfig tree you see in the default view is actually compiled from this TSconfig code in the order it appears

here. This view lets you see how the parsed version came to be.

You can also click the edit-icons of the various pages to go directly to the TSconfig fields of the pages.

Shows the raw Page TSconfig code. First you see the default content from TYPO3_CONF_VARS (probably added by extensions),

then the content from the "TSconfig" field of the first page in the root line ("Intro") and then for each root line page up to the

current page (not shown in screenshot).

In the bottom of the page you will see a link which will open editing forms for all of the TSconfig fields shown in the list!


9/9

Here you see specifically the TSconfig fields of the first and second page in the rootline being edited. Notice the "TS" icon next to

the first field - this will bring up a wizard that helps you to select among available Page TSconfig properties.

See also:

Web > Info module / Page TSconfig hierarchy viewer

typo3 manual info module.pdf

Documents