0byt3m1n1
Path:
/
data
/
applications
/
aps
/
typo3
/
4.2.1-6
/
standard
/
htdocs
/
typo3
/
sysext
/
cms
/
[
Home
]
File: locallang_csh_webinfo.xml
<?xml version="1.0" encoding="utf-8" standalone="yes" ?> <T3locallang> <meta type="array"> <description>CSH for Web>Info module(s)</description> <type>CSH</type> <csh_table>_MOD_web_info</csh_table> </meta> <data type="array"> <languageKey index="default" type="array"> <label index="pagetree_overview.alttitle">Pagetree Overview</label> <label index="pagetree_overview.description">The Pagetree Overview shows information related to pages for a branch of the page tree. This includes start- and stop-times, cache settings etc.</label> <label index="_pagetree_overview.seeAlso">_MOD_web_info:func_0, _MOD_web_info:func_1, _MOD_web_info:func_2, _MOD_web_info:stat</label> <label index="_pagetree_overview.image">EXT:cms/cshimages/pagetree_overview_1.png</label> <label index="pagetree_overview.image_descr">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.</label> <label index="func_0.alttitle">Basic Settings</label> <label index="func_0.description">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.</label> <label index="func_0.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. <b>Batch editing page fields</b> 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.</label> <label index="_func_0.seeAlso">xMOD_csh_corebe:list_module, _MOD_web_info:func_2, _MOD_web_info:pagetree_overview</label> <label index="_func_0.image">EXT:cms/cshimages/pagetree_overview_4.png, EXT:cms/cshimages/pagetree_overview_8.png, EXT:cms/cshimages/pagetree_overview_9.png</label> <label index="func_0.image_descr">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.</label> <label index="func_1.alttitle">Record Overview</label> <label index="func_1.description">Record overview gives you an indispensable overview of the distribution of records in the page tree. Each database table in the system is represented with a column and for each page you can see the number of records from that table located on the page.</label> <label index="func_1.details"><b>Notice:</b> 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! <b>Tree stop?</b> 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.</label> <label index="_func_1.seeAlso">_MOD_web_info:pagetree_overview, pages:php_tree_stop</label> <label index="_func_1.image">EXT:cms/cshimages/pagetree_overview_6.png</label> <label index="func_1.image_descr">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!</label> <label index="func_2.alttitle">Cache and Age</label> <label index="func_2.description">Displays a selection of fields from page records related to page caching and time settings.</label> <label index="_func_2.seeAlso">_MOD_web_info:func_0, _MOD_web_info:pagetree_overview, pages:TSconfig</label> <label index="_func_2.image">EXT:cms/cshimages/pagetree_overview_5.png, EXT:cms/cshimages/pagetree_overview_7.png</label> <label index="func_2.image_descr">The "Cache and Age" view. Here you see the "TSconfig" column. The overview exposes that these two pages include some Page TSconfig code!</label> <label index="stat.alttitle">Page Hit statistics</label> <label index="stat.description">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.</label> <label index="stat.details"><b>Notice:</b> 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.</label> <label index="_stat.image">EXT:cms/cshimages/pagetree_overview_3.png</label> <label index="lang.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: <b>Green background:</b> Page is translated and viewable in this language. For translations it means that an active page overlay record is present. <b>Red background:</b> Page <em>cannot</em> be 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. <b>Gray background (not available for default language):</b> 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!) <b>The pages "Localization settings:"</b> It is the "Localization settings" of the page record that determines the modes above. In the column of the default translation 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 be accessed for that language. But combined with the "localization settings" of pages which may block page access this becomes a problem with pages which are <em>not</em> translated (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 <em>always</em> 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.</label> <label index="_lang.image">EXT:cms/cshimages/localizationoverview.png, EXT:cms/cshimages/localizationoverview1.png</label> <label index="lang.image_descr">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. The "Localization settings" that affect availability of pages in the various languages.</label> <label index="func_hits.alttitle">Statistic Views</label> <label index="func_hits.description">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.</label> <label index="func_hits.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: <b>Page hits</b> This shows page hits/sessions for each page. <b>Total hits</b> 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. <b>Hits in main sections</b> 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)</label> <label index="_func_hits.image">EXT:cms/cshimages/pagetree_overview_2.png</label> <label index="lang.alttitle">Localization overview</label> <label index="lang.description">Gives an overview of which pages in the page tree are translated to the system languages installed.</label> </languageKey> </data> </T3locallang>