first commit

This commit is contained in:
salam committed 2026-10-19 08:18:39 +02:00
commit 1218dd1517
12716 files changed
+989233

No files matched your search

@@ -0,0 +1,71 @@
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.0" xmlns:t3="http://typo3.org/schemas/xliff">
<file t3:id="1415814840" source-language="en" datatype="plaintext" original="EXT:info/Resources/Private/Language/InfoPageTsConfig.xlf" date="2011-10-17T20:22:33Z" product-name="info_pagetsconfig">
<header/>
<body>
<trans-unit id="tsconf_title" resname="tsconf_title">
<source>Page TSconfig</source>
</trans-unit>
<trans-unit id="tsconf_parts_0" resname="tsconf_parts_0">
<source>All</source>
</trans-unit>
<trans-unit id="tsconf_parts_1" resname="tsconf_parts_1">
<source>Module key ('mod') with overruling user settings</source>
</trans-unit>
<trans-unit id="tsconf_parts_1a" resname="tsconf_parts_1a">
<source>Module: Web&gt;Page</source>
</trans-unit>
<trans-unit id="tsconf_parts_1b" resname="tsconf_parts_1b">
<source>Module: Web&gt;View</source>
</trans-unit>
<trans-unit id="tsconf_parts_1c" resname="tsconf_parts_1c">
<source>Module: Web&gt;Modules</source>
</trans-unit>
<trans-unit id="tsconf_parts_1d" resname="tsconf_parts_1d">
<source>Module: Web&gt;List</source>
</trans-unit>
<trans-unit id="tsconf_parts_1e" resname="tsconf_parts_1e">
<source>Module: Web&gt;Info</source>
</trans-unit>
<trans-unit id="tsconf_parts_1f" resname="tsconf_parts_1f">
<source>Module: Web&gt;Func</source>
</trans-unit>
<trans-unit id="tsconf_parts_1g" resname="tsconf_parts_1g">
<source>Module: Web&gt;Template</source>
</trans-unit>
<trans-unit id="tsconf_configFields" resname="tsconf_configFields">
<source>View TSconfig fields content</source>
</trans-unit>
<trans-unit id="editThisColumn" resname="editThisColumn">
<source>Edit the field '%s' for all listed pages</source>
</trans-unit>
<trans-unit id="editTSconfig" resname="editTSconfig">
<source>Edit TSconfig for this page</source>
</trans-unit>
<trans-unit id="editTSconfig_all" resname="editTSconfig_all">
<source>Edit TSconfig for all shown pages</source>
</trans-unit>
<trans-unit id="editTSconfig_default" resname="editTSconfig_default">
<source>Default Configuration from TYPO3_CONF_VARS</source>
</trans-unit>
<trans-unit id="mod_pagetsconfig" resname="mod_pagetsconfig">
<source>Page TSconfig</source>
</trans-unit>
<trans-unit id="sort_alphabetic" resname="sort_alphabetic">
<source>Sort alphabetically</source>
</trans-unit>
<trans-unit id="pagetitle" resname="pagetitle">
<source>Pagetitle:</source>
</trans-unit>
<trans-unit id="included_tsconfig_files" resname="included_tsconfig_files">
<source>Included Files:</source>
</trans-unit>
<trans-unit id="written_tsconfig_lines" resname="written_tsconfig_lines">
<source>Lines:</source>
</trans-unit>
<trans-unit id="tsconf_noPageTSconfig" resname="tsconf_noPageTSconfig">
<source>There are no pages containing custom Page TSconfig settings in the page configuration.</source>
</trans-unit>
</body>
</file>
</xliff>
@@ -0,0 +1,60 @@
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.0" xmlns:t3="http://typo3.org/schemas/xliff">
<file t3:id="1415814841" source-language="en" datatype="plaintext" original="EXT:info/Resources/Private/Language/locallang_csh_tsconfigInfo.xlf" date="2011-10-17T20:22:33Z" product-name="info_pagetsconfig">
<header/>
<body>
<trans-unit id="tsconfig_hierarchy.alttitle" resname="tsconfig_hierarchy.alttitle">
<source>Page TSconfig hierarchy viewer</source>
</trans-unit>
<trans-unit id="tsconfig_hierarchy.description" resname="tsconfig_hierarchy.description">
<source>Allows the user to view the compiled Page TSconfig structure for a branch of the pagetree.</source>
</trans-unit>
<trans-unit id="tsconfig_hierarchy.details" resname="tsconfig_hierarchy.details" xml:space="preserve">
<source>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.</source>
</trans-unit>
<trans-unit id="_tsconfig_hierarchy.seeAlso" resname="_tsconfig_hierarchy.seeAlso" xml:space="preserve">
<source>_MOD_web_info:tsconfig_edit,
pages:TSconfig,
Page TSconfig objects | https://docs.typo3.org/typo3cms/TSconfigReference/PageTsconfig/Index.html</source>
<note from="developer">A part of this string is an internal text, which must not be changed. Just copy this part into the translation field and do not change it. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="_tsconfig_hierarchy.image" resname="_tsconfig_hierarchy.image" xml:space="preserve">
<source>EXT:info_pagetsconfig/Resources/Public/Images/cshimages/img_1.png,
EXT:info_pagetsconfig/Resources/Public/Images/cshimages/img_2.png,</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="tsconfig_hierarchy.image_descr" resname="tsconfig_hierarchy.image_descr" xml:space="preserve">
<source>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 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).</source>
</trans-unit>
<trans-unit id="tsconfig_edit.alttitle" resname="tsconfig_edit.alttitle">
<source>Page TSconfig content viewer</source>
</trans-unit>
<trans-unit id="tsconfig_edit.description" resname="tsconfig_edit.description">
<source>Displays the raw TSconfig code of all pages in the current root line including any default code.</source>
</trans-unit>
<trans-unit id="tsconfig_edit.details" resname="tsconfig_edit.details" xml:space="preserve">
<source>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.</source>
</trans-unit>
<trans-unit id="_tsconfig_edit.seeAlso" resname="_tsconfig_edit.seeAlso">
<source>_MOD_web_info:tsconfig_hierarchy</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="_tsconfig_edit.image" resname="_tsconfig_edit.image" xml:space="preserve">
<source>EXT:info_pagetsconfig/Resources/Public/Images/cshimages/img_3.png,
EXT:info_pagetsconfig/Resources/Public/Images/cshimages/img_4.png,
EXT:info_pagetsconfig/Resources/Public/Images/cshimages/img_5.png</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="tsconfig_edit.image_descr" resname="tsconfig_edit.image_descr" xml:space="preserve">
<source>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!
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.</source>
</trans-unit>
</body>
</file>
</xliff>
@@ -0,0 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.0" xmlns:t3="http://typo3.org/schemas/xliff">
<file t3:id="1415814862" source-language="en" datatype="plaintext" original="EXT:info/Resources/Private/Language/locallang_csh_web_info.xlf" date="2011-10-17T20:22:33Z" product-name="lang">
<header/>
<body>
<trans-unit id=".alttitle" resname=".alttitle">
<source>Web &gt; Info module</source>
</trans-unit>
<trans-unit id=".description" resname=".description">
<source>The idea of the Web&gt;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.</source>
</trans-unit>
<trans-unit id=".details" resname=".details">
<source>The Web&gt;Info module shows information rather than offering functionality. It is up to extension programmers to decide in which of these two modules they want to insert functionality.</source>
</trans-unit>
<trans-unit id="_.image" resname="_.image">
<source>EXT:info/Resources/Public/Images/cshimages/pagetree_overview_10.png</source>
</trans-unit>
<trans-unit id=".image_descr" resname=".image_descr">
<source>The Web&gt;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".</source>
</trans-unit>
</body>
</file>
</xliff>
@@ -0,0 +1,116 @@
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.0" xmlns:t3="http://typo3.org/schemas/xliff">
<file t3:id="1415814788" source-language="en" datatype="plaintext" original="EXT:info/Resources/Private/Language/locallang_csh_webinfo.xlf" date="2011-10-17T20:22:32Z" product-name="cms">
<header/>
<body>
<trans-unit id="func_0.alttitle" resname="func_0.alttitle">
<source>Basic Settings</source>
</trans-unit>
<trans-unit id="func_0.description" resname="func_0.description">
<source>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.</source>
</trans-unit>
<trans-unit id="func_0.details" resname="func_0.details" xml:space="preserve">
<source>The Basic Settings view resembles the Cache and Age view quite a lot. They are different only by the selection of fields they show.
&lt;b&gt;Batch editing page fields&lt;/b&gt;
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.</source>
</trans-unit>
<trans-unit id="_func_0.seeAlso" resname="_func_0.seeAlso" xml:space="preserve">
<source>xMOD_csh_corebe:list_module,
_MOD_web_info:func_2,
_MOD_web_info:pagetree_overview</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="_func_0.image" resname="_func_0.image" xml:space="preserve">
<source>EXT:frontend/Resources/Public/Images/cshimages/pagetree_overview_4.png,
EXT:frontend/Resources/Public/Images/cshimages/pagetree_overview_8.png,
EXT:frontend/Resources/Public/Images/cshimages/pagetree_overview_9.png</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="func_0.image_descr" resname="func_0.image_descr" xml:space="preserve">
<source>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.</source>
</trans-unit>
<trans-unit id="func_1.alttitle" resname="func_1.alttitle">
<source>Record Overview</source>
</trans-unit>
<trans-unit id="func_1.description" resname="func_1.description">
<source>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.</source>
</trans-unit>
<trans-unit id="func_1.details" resname="func_1.details" xml:space="preserve">
<source>&lt;b&gt;Notice:&lt;/b&gt; 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!
&lt;b&gt;Tree stop?&lt;/b&gt;
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.</source>
</trans-unit>
<trans-unit id="_func_1.seeAlso" resname="_func_1.seeAlso" xml:space="preserve">
<source>_MOD_web_info:pagetree_overview,
pages:php_tree_stop</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="_func_1.image" resname="_func_1.image">
<source>EXT:frontend/Resources/Public/Images/cshimages/pagetree_overview_6.png</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="func_1.image_descr" resname="func_1.image_descr">
<source>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!</source>
</trans-unit>
<trans-unit id="func_2.alttitle" resname="func_2.alttitle">
<source>Cache and Age</source>
</trans-unit>
<trans-unit id="func_2.description" resname="func_2.description">
<source>Displays a selection of fields from page records related to page caching and time settings.</source>
</trans-unit>
<trans-unit id="_func_2.seeAlso" resname="_func_2.seeAlso" xml:space="preserve">
<source>_MOD_web_info:func_0,
_MOD_web_info:pagetree_overview,
pages:TSconfig</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="_func_2.image" resname="_func_2.image" xml:space="preserve">
<source>EXT:frontend/Resources/Public/Images/cshimages/pagetree_overview_5.png,
EXT:frontend/Resources/Public/Images/cshimages/pagetree_overview_7.png</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="func_2.image_descr" resname="func_2.image_descr" xml:space="preserve">
<source>The "Cache and Age" view.
Here you see the "TSconfig" column. The overview exposes that these two pages include some Page TSconfig code!</source>
</trans-unit>
<trans-unit id="lang.details" resname="lang.details" xml:space="preserve">
<source>The overview uses colors to signal the availability and fall back situation for a given page. Here is a description for each color code:
&lt;b&gt;Green background:&lt;/b&gt; Page is translated and viewable in this language. For translations it means that an active page overlay record is present.
&lt;b&gt;Red background:&lt;/b&gt; Page &lt;em&gt;cannot&lt;/em&gt; 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.
&lt;b&gt;Gray background (not available for default language):&lt;/b&gt; 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!)
&lt;b&gt;The pages "Localization settings:"&lt;/b&gt;
It is the "Localization settings" of the page record that determines the modes above. In the column of the default language each of these settings are represented by a "N" (Hide page if no translation for current language exists) or a "D" (Hide default language 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 &lt;em&gt;not&lt;/em&gt; translated (has gray background); You might get menu items which links to non-accessible pages.
The problem basically is that "&amp;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 &lt;em&gt;always&lt;/em&gt; follow what "&amp;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.</source>
</trans-unit>
<trans-unit id="_lang.image" resname="_lang.image" xml:space="preserve">
<source>EXT:frontend/Resources/Public/Images/cshimages/localizationoverview.png,
EXT:frontend/Resources/Public/Images/cshimages/localizationoverview1.png</source>
<note from="developer">This string contains an internal text, which must not be changed. Just copy the original text into the translation field. For more information have a look at the Tutorial.</note>
</trans-unit>
<trans-unit id="lang.image_descr" resname="lang.image_descr" xml:space="preserve">
<source>Localization overview in the Web&gt;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.</source>
</trans-unit>
<trans-unit id="lang.alttitle" resname="lang.alttitle">
<source>Localization overview</source>
</trans-unit>
<trans-unit id="lang.description" resname="lang.description">
<source>Gives an overview of which pages in the page tree are translated to the system languages installed.</source>
</trans-unit>
</body>
</file>
</xliff>
@@ -0,0 +1,20 @@
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.0" xmlns:t3="http://typo3.org/schemas/xliff">
<file t3:id="1415814880" source-language="en" datatype="plaintext" original="EXT:info/Resources/Private/Language/locallang_mod_web_info.xlf" date="2011-10-17T20:22:34Z" product-name="lang">
<header/>
<body>
<trans-unit id="title" resname="title">
<source>Page information</source>
</trans-unit>
<trans-unit id="mlang_labels_tablabel" resname="mlang_labels_tablabel">
<source>Page related information, eg. hit statistics, change log, record counts</source>
</trans-unit>
<trans-unit id="mlang_labels_tabdescr" resname="mlang_labels_tabdescr">
<source>The Web&gt;Info module is focused on statistic information about pages. This includes statistics of pagehits and a changelog allowing browsing of page history changes. An overview of the number of records on each page as well as page settings presented in a classic tree structure is provided.</source>
</trans-unit>
<trans-unit id="mlang_tabs_tab" resname="mlang_tabs_tab">
<source>Info</source>
</trans-unit>
</body>
</file>
</xliff>
@@ -0,0 +1,92 @@
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.0" xmlns:t3="http://typo3.org/schemas/xliff">
<file t3:id="1415814792" source-language="en" datatype="plaintext" original="EXT:info/Resources/Private/Language/locallang_webinfo.xlf" date="2011-10-17T20:22:32Z" product-name="cms">
<header/>
<body>
<trans-unit id="page_title" resname="page_title">
<source>Pagetree overview</source>
</trans-unit>
<trans-unit id="page_sysnote" resname="page_sysnote">
<source>Internal notes</source>
</trans-unit>
<trans-unit id="pageInformation" resname="pageInformation">
<source>Page information</source>
</trans-unit>
<trans-unit id="pages_0" resname="pages_0">
<source>Basic settings</source>
</trans-unit>
<trans-unit id="pages_2" resname="pages_2">
<source>Cache and Age</source>
</trans-unit>
<trans-unit id="pages_1" resname="pages_1">
<source>Record overview</source>
</trans-unit>
<trans-unit id="stat_type_0" resname="stat_type_0">
<source>Page hits</source>
</trans-unit>
<trans-unit id="stat_type_1" resname="stat_type_1">
<source>Total hits</source>
</trans-unit>
<trans-unit id="stat_type_2" resname="stat_type_2">
<source>Hits in main sections</source>
</trans-unit>
<trans-unit id="stat_period" resname="stat_period">
<source>Statistics in the period %s back to %s</source>
</trans-unit>
<trans-unit id="pI_crUser" resname="pI_crUser">
<source>Created by</source>
</trans-unit>
<trans-unit id="pI_crDate" resname="pI_crDate">
<source>Created date</source>
</trans-unit>
<trans-unit id="pI_lastChange" resname="pI_lastChange">
<source>Last change</source>
</trans-unit>
<trans-unit id="pI_lastChangeContent" resname="pI_lastChangeContent">
<source>Last change, content</source>
</trans-unit>
<trans-unit id="hits_title" resname="hits_title">
<source>Hit Statistics</source>
</trans-unit>
<trans-unit id="lang_renderl10n_viewPage" resname="lang_renderl10n_viewPage">
<source>View page</source>
</trans-unit>
<trans-unit id="lang_title" resname="lang_title">
<source>Localization overview</source>
</trans-unit>
<trans-unit id="lang_renderl10n_editDefaultLanguagePage" resname="lang_renderl10n_editDefaultLanguagePage">
<source>Edit default language page properties</source>
</trans-unit>
<trans-unit id="lang_renderl10n_editLangOverlays" resname="lang_renderl10n_editLangOverlays">
<source>Edit all language overlay records</source>
</trans-unit>
<trans-unit id="lang_renderl10n_editPageProperties" resname="lang_renderl10n_editPageProperties">
<source>Edit all page properties</source>
</trans-unit>
<trans-unit id="lang_renderl10n_editPage" resname="lang_renderl10n_editPage">
<source>Edit page</source>
</trans-unit>
<trans-unit id="lang_renderl10n_editPageLang" resname="lang_renderl10n_editPageLang">
<source>Edit page translation</source>
</trans-unit>
<trans-unit id="lang_renderl10n_badThingThereAre" resname="lang_renderl10n_badThingThereAre">
<source>ERROR: there are two or more page overlay records for this language! Only one is allowed!</source>
</trans-unit>
<trans-unit id="lang_renderl10n_editLanguageOverlayRecord" resname="lang_renderl10n_editLanguageOverlayRecord">
<source>Edit language overlay record</source>
</trans-unit>
<trans-unit id="lang_renderl10n_page" resname="lang_renderl10n_page">
<source>Page</source>
</trans-unit>
<trans-unit id="lang_renderl10n_default" resname="lang_renderl10n_default">
<source>Default</source>
</trans-unit>
<trans-unit id="lang_getlangsta_createNewTranslationHeaders" resname="lang_getlangsta_createNewTranslationHeaders">
<source>Create new translation headers</source>
</trans-unit>
<trans-unit id="lang_renderl10n_CEcount" resname="lang_renderl10n_CEcount">
<source>Content Element Count</source>
</trans-unit>
</body>
</file>
</xliff>