[DOCS] Proofreading and moving of feature rst files for 7.4 Part 2 73/42273/21
authorDaniel Maier <dani-maier@gmx.de>
Wed, 5 Aug 2015 12:05:00 +0000 (14:05 +0200)
committerAnja Leichsenring <aleichsenring@ab-softlab.de>
Thu, 6 Aug 2015 17:59:54 +0000 (19:59 +0200)
Official documentations have been updated according to rst-files
mentioned here

Resolves: #68752
Releases: master
Change-Id: Ic9c4142807bae35b05d1d577c3b601ef70a181d6
Reviewed-on: http://review.typo3.org/42273
Reviewed-by: Daniel Maier <dani-maier@gmx.de>
Tested-by: Daniel Maier <dani-maier@gmx.de>
Reviewed-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
Tested-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
36 files changed:
typo3/sysext/core/Documentation/Changelog/7.4/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-33071-AddTheHttpHeaderContent-LanguageWhenRenderingAPage.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-43984-AddStdWrapFunctionalityToTreatIdAsReferenceTypoScript.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-45725-AddedRecursiveOptionToFolderBasedFileCollections.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-61308-AllowPlaceholderAttribute.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-61903-PageTSDataproviderForBackendLayouts.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-64200-AllowIndividualContentCaching.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-65550-MakeTableDisplayOrderConfigurableInListModule.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-67360-CustomAttributeNameAndMultipleValuesForMetaTags.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-67603-IntroduceTcaDescriptionColumn.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-67658-IntroduceDataProcessorsForSplittingValues.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-67662-DataProcessorForFiles.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-67663-IntroduceDataProcessorForMediaGalleries.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-67880-AddedCountToListNum.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-68094-DatabaseQueryDataProcessor.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-68191-TypoScriptSelectOptionLanguageFieldIsActiveByDefault.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-68315-IncludeAPageTSconfigFileInPagePropertiesLikeTSStaticTemplates.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/7.4/Feature-68600-IntroducedResourceStorageSanitizeFileNameSignal.rst [new file with mode: 0644]
typo3/sysext/core/Documentation/Changelog/master/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-33071-AddTheHttpHeaderContent-LanguageWhenRenderingAPage.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-43984-AddStdWrapFunctionalityToTreatIdAsReferenceTypoScript.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-45725-AddedRecursiveOptionToFolderBasedFileCollections.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-61308-AllowPlaceholderAttribute.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-61903-PageTSDataproviderForBackendLayouts.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-64200-AllowIndividualContentCaching.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-65550-MakeTableDisplayOrderConfigurableInListModule.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-67360-CustomAttributeNameAndMultipleValuesForMetaTags.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-67603-IntroduceTcaDescriptionColumn.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-67658-IntroduceDataProcessorsForSplittingValues.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-67662-DataProcessorForFiles.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-67663-IntroduceDataProcessorForMediaGalleries.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-68094-DatabaseQueryDataProcessor.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-68191-TypoScriptSelectOptionLanguageFieldIsActiveByDefault.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-68315-IncludeAPageTSconfigFileInPagePropertiesLikeTSStaticTemplates.rst [deleted file]
typo3/sysext/core/Documentation/Changelog/master/Feature-68600-IntroducedResourceStorageSanitizeFileNameSignal.rst [deleted file]
typo3/sysext/form/Documentation/Configuration/Reference/Objects/Index.rst

diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst
new file mode 100644 (file)
index 0000000..7a4c260
--- /dev/null
@@ -0,0 +1,38 @@
+==============================================================
+Feature: #22175 - Support IEC/SI units in file size formatting
+==============================================================
+
+Description
+===========
+
+Size formatting supports two keywords additionally to the list of labels:
+- iec: uses the Ki, Mi, etc prefixes and binary base (power of two, 1024)
+- si: uses the k, M, etc prefixes and decimal base (power of ten, 1000)
+
+The default formatting is set to "iec" base size calculations on the same base as before.
+The fractional part, when present, is changed to two numbers instead of only one.
+
+The list of labels is still supported and defaults to using binary base. It is also
+possible to explicitly choose between binary or decimal base when it is used.
+
+
+Impact
+======
+
+Default formatted output of file sizes changes, see example below.
+
+TypoScript ``stdWrap`` property ``bytes`` defaults to a different label set.
+``bytes.labels = iec``, a specifically defined label string with pipe separated
+label keywords is obsolete, but can still be used if required. The keyword
+``iec`` resolves to `` | Ki| Mi| Gi| Ti| Pi| Ei| Zi| Yi`` (binary base) and ``si`` resolves
+to `` | k| M| G| T| P| E| Z| Y`` (based on ten).
+
+
+Example
+=======
+
+.. code-block:: php
+
+       echo GeneralUtility::formatSize(85123);
+       // => Before "83.1 K"
+       // => Now "83.13 Ki"
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-33071-AddTheHttpHeaderContent-LanguageWhenRenderingAPage.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-33071-AddTheHttpHeaderContent-LanguageWhenRenderingAPage.rst
new file mode 100644 (file)
index 0000000..2f25f17
--- /dev/null
@@ -0,0 +1,19 @@
+==============================================================================
+Feature: #33071 - Add the http header "Content-Language" when rendering a page
+==============================================================================
+
+Description
+===========
+
+By default a header "Content-language: XX" is sent where "XX" is the iso code of the sys_language_content if that is
+properly defined by the sys_language record representing the sys_language_uid.
+The "config.disableLanguageHeader" will disable that.
+
+
+
+Impact
+======
+
+By default in new and existing installations a header "Content-language: XX" is sent where "XX" is the iso code of the
+sys_language_content if that is properly defined by the sys_language record representing the sys_language_uid.
+You must set "config.disableLanguageHeader" to disable that and get previous behavior (no header).
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-43984-AddStdWrapFunctionalityToTreatIdAsReferenceTypoScript.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-43984-AddStdWrapFunctionalityToTreatIdAsReferenceTypoScript.rst
new file mode 100644 (file)
index 0000000..6e7a8d4
--- /dev/null
@@ -0,0 +1,9 @@
+============================================================================
+Feature: #43984 - Add stdWrap functionality to TreatIdAsReference TypoScript
+============================================================================
+
+Description
+===========
+
+The new TypoScript property "treatIdAsReference" for the getImgResource object
+can now be used with stdWrap properties.
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-45725-AddedRecursiveOptionToFolderBasedFileCollections.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-45725-AddedRecursiveOptionToFolderBasedFileCollections.rst
new file mode 100644 (file)
index 0000000..afee6e7
--- /dev/null
@@ -0,0 +1,24 @@
+=========================================================================
+Feature: #45725 - Added recursive option to folder based file collections
+=========================================================================
+
+Description
+===========
+
+Folder based file collections have now an option to fetch all files recursively for
+the given folder. The option is also available in the TypoScript Object ``FILES``.
+
+Usage:
+
+.. code-block:: typoscript
+
+       filecollection = FILES
+       filecollection {
+               folders = 1:images/
+               folders.recursive = 1
+
+               renderObj = IMAGE
+               renderObj {
+                       file.import.data = file:current:uid
+               }
+       }
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-61308-AllowPlaceholderAttribute.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-61308-AllowPlaceholderAttribute.rst
new file mode 100644 (file)
index 0000000..1b2370b
--- /dev/null
@@ -0,0 +1,10 @@
+=============================================
+Feature: #61308 - Allow Placeholder attribute
+=============================================
+
+Description
+===========
+
+System extension ``form`` allows a placeholder attribute in textfields
+by adding it in a form configuration. However, there is no option to add
+placeholder using the form wizard, yet.
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-61903-PageTSDataproviderForBackendLayouts.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-61903-PageTSDataproviderForBackendLayouts.rst
new file mode 100644 (file)
index 0000000..d4644aa
--- /dev/null
@@ -0,0 +1,61 @@
+=========================================================
+Feature: #61903 - PageTS dataprovider for backend layouts
+=========================================================
+
+Description
+===========
+
+Over the last year, several extensions appeared on TER that implemented the very same basic feature:
+Deploying backend layouts without database records by providing them via PageTS.
+
+Implement a generic PageTS provider for backend layouts to unify those approaches and to make backend layouts reusable
+across installations.
+
+
+Impact
+======
+
+It is now possible to define backend layouts via PageTSConfig on every page.
+
+
+Example
+-------
+
+.. code-block:: typoscript
+
+       mod {
+               web_layout {
+                       BackendLayouts {
+                               exampleKey {
+                                       title = Example
+                                       config {
+                                               backend_layout {
+                                                       colCount = 1
+                                                       rowCount = 2
+                                                       rows {
+                                                               1 {
+                                                                       columns {
+                                                                               1 {
+                                                                                       name = LLL:EXT:frontend/Resources/Private/Language/locallang_ttc.xlf:colPos.I.3
+                                                                                       colPos = 3
+                                                                                       colspan = 1
+                                                                               }
+                                                                       }
+                                                               }
+                                                               2 {
+                                                                       columns {
+                                                                               1 {
+                                                                                       name = Main
+                                                                                       colPos = 0
+                                                                                       colspan = 1
+                                                                               }
+                                                                       }
+                                                               }
+                                                       }
+                                               }
+                                       }
+                                       icon = EXT:example_extension/Resources/Public/Images/BackendLayouts/default.gif
+                               }
+                       }
+               }
+       }
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-64200-AllowIndividualContentCaching.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-64200-AllowIndividualContentCaching.rst
new file mode 100644 (file)
index 0000000..77715bc
--- /dev/null
@@ -0,0 +1,61 @@
+==================================================
+Feature: #64200 - Allow individual content caching
+==================================================
+
+Description
+===========
+
+The ``stdWrap.cache.`` property is now available as first-class function to all
+content objects. This skips the rendering even for content objects that evaluate
+``stdWrap`` after rendering (e.g. ``COA``).
+
+Usage:
+
+.. code-block:: typoscript
+
+       page = PAGE
+       page.10 = COA
+       page.10 {
+               cache.key = coaout
+               cache.lifetime = 60
+               #stdWrap.cache.key = coastdWrap
+               #stdWrap.cache.lifetime = 60
+               10 = TEXT
+               10 {
+                       cache.key = mycurrenttimestamp
+                       cache.lifetime = 60
+                       data = date : U
+                       strftime = %H:%M:%S
+                       noTrimWrap = |10: | |
+               }
+               20 = TEXT
+               20 {
+                       data = date : U
+                       strftime = %H:%M:%S
+                       noTrimWrap = |20: | |
+               }
+       }
+
+The commented part is ``stdWrap.cache.`` property available since 4.7,
+that does not stop the rendering of ``COA`` including all sub-cObjects.
+
+Additionally, stdWrap support is added to key, lifetime and tags.
+
+
+Impact
+======
+
+If you've previously used the ``cache.`` property in your custom cObject,
+this will now fail, because ``cache.`` is unset to avoid double caching.
+You are encouraged to rely on the core methods for caching cObjects or
+rename your property.
+
+``stdWrap.cache`` continues to exists and can be used as before. However
+the top level ``stdWrap`` of certain cObjects (e.g. ``TEXT`` cObject)
+will not evaluate ``cache.`` as part of ``stdWrap``, but before starting
+the rendering of the cObject. In conjunction the storing will happen
+after the ``stdWrap`` processing right before the content is returned.
+
+Top level ``cache.`` will not evaluate the hook
+``$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['stdWrap_cacheStore']``
+any more.
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-65550-MakeTableDisplayOrderConfigurableInListModule.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-65550-MakeTableDisplayOrderConfigurableInListModule.rst
new file mode 100644 (file)
index 0000000..63ad7e4
--- /dev/null
@@ -0,0 +1,19 @@
+======================================================================
+Feature: #65550 - Make table display order configurable in List module
+======================================================================
+
+Description
+===========
+
+The new ``PageTSconfig`` configuration option ``mod.web_list.tableDisplayOrder`` has been added
+for the List module to allow flexible configuration of the order in which tables are displayed.
+The keywords ``before`` and ``after`` can be used to specify an order relative to other table names.
+
+Example:
+
+.. code-block:: typoscript
+
+       mod.web_list.tableDisplayOrder.<tableName> {
+         before = <tableA>, <tableB>, ...
+         after = <tableA>, <tableB>, ...
+       }
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67360-CustomAttributeNameAndMultipleValuesForMetaTags.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67360-CustomAttributeNameAndMultipleValuesForMetaTags.rst
new file mode 100644 (file)
index 0000000..29f4cc8
--- /dev/null
@@ -0,0 +1,53 @@
+=========================================================================
+Feature: #67360 - Custom attribute name and multiple values for meta tags
+=========================================================================
+
+Description
+===========
+
+``page.meta`` is extented to support different attribute names like ``property`` used for OG tags. You may also supply
+multiple values for one name, which results in multiple meta tags with the same name to be rendered.
+
+See http://ogp.me/ for more information about the Open Graph protocol and its properties.
+
+.. code-block:: typoscript
+
+    page {
+        meta {
+            X-UA-Compatible = IE=edge,chrome=1
+            X-UA-Compatible.attribute = http-equiv
+
+            keywords = TYPO3
+
+            og:site_name = TYPO3
+            og:site_name.attribute = property
+
+            description = Inspiring people to share Normal
+
+            dc\.description = Inspiring people to share [DC tags]
+
+            og:description = Inspiring people to share [OpenGraph]
+            og:description.attribute = property
+
+            og:locale = en_GB
+            og:locale.attribute = property
+
+            og:locale:alternate {
+                attribute = property
+                value {
+                    1 = fr_FR
+                    2 = de_DE
+                }
+            }
+
+            refresh = 5; url=http://example.com/
+            refresh.attribute = http-equiv
+
+        }
+    }
+
+
+Impact
+======
+
+Meta tags with a different attribute name are supported now like the Open Graph meta tags.
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67603-IntroduceTcaDescriptionColumn.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67603-IntroduceTcaDescriptionColumn.rst
new file mode 100644 (file)
index 0000000..2325ee6
--- /dev/null
@@ -0,0 +1,18 @@
+==========================================================
+Feature: #67603 - Introduce TCA > ctrl > descriptionColumn
+==========================================================
+
+Description
+===========
+
+To annotate database table column fields as internal description for editors and admins a new setting
+for TCA is introduced. Setting is called ``['TCA']['ctrl']['descriptionColumn']`` and holds column name.
+
+This description should only displayed in the backend to guide editors and admins.
+
+Usage of descriptionColumn is added under different issues.
+
+Impact
+======
+
+None, since annotation itself is added only. Does not impact.
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67658-IntroduceDataProcessorsForSplittingValues.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67658-IntroduceDataProcessorsForSplittingValues.rst
new file mode 100644 (file)
index 0000000..2d737db
--- /dev/null
@@ -0,0 +1,73 @@
+===============================================================
+Feature: #67658 - Introduce DataProcessors for splitting values
+===============================================================
+
+Description
+===========
+
+Two new DataProcessors are added to allow flexible processing for comma-separated
+values. To use e.g. with the FLUIDTEMPLATE content object.
+
+The SplitProcessor allows to split values separated with a delimiter inside a single database field
+into an array to loop over it.
+
+The CommaSeparatedValueProcessor allows to split values into a two-dimensional array used for
+CSV files or tt_content records of CType "table".
+
+Using the SplitProcessor the following scenario is possible:
+
+.. code-block:: typoscript
+
+       page.10 = FLUIDTEMPLATE
+       page.10.file = EXT:site_default/Resources/Private/Template/Default.html
+       page.10.dataProcessing.2 = TYPO3\CMS\Frontend\DataProcessing\SplitProcessor
+       page.10.dataProcessing.2 {
+               if.isTrue.field = bodytext
+               delimiter = ,
+               fieldName = bodytext
+               removeEmptyEntries = 1
+               filterIntegers = 1
+               filterUnique = 1
+               as = keywords
+       }
+
+
+In the Fluid template then iterate over the split data:
+
+.. code-block:: html
+
+       <f:for each="{keywords}" as="keyword">
+               <li>Keyword: {keyword}</li>
+       </f:for>
+
+
+Using the CommaSeparatedValueProcessor the following scenario is possible:
+
+.. code-block:: typoscript
+
+       page.10 = FLUIDTEMPLATE
+       page.10.file = EXT:site_default/Resources/Private/Template/Default.html
+       page.10.dataProcessing.4 = TYPO3\CMS\Frontend\DataProcessing\CommaSeparatedValueProcessor
+       page.10.dataProcessing.4 {
+               if.isTrue.field = bodytext
+               fieldName = bodytext
+               fieldDelimiter = |
+               fieldEnclosure =
+               maximumColumns = 2
+               as = table
+       }
+
+
+In the Fluid template then iterate over the processed data:
+
+.. code-block:: html
+
+       <table>
+               <f:for each="{table}" as="columns">
+                       <tr>
+                               <f:for each="{columns}" as="column">
+                                       <td>{column}</td>
+                               </f:for>
+                       <tr>
+               </f:for>
+       </table>
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67662-DataProcessorForFiles.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67662-DataProcessorForFiles.rst
new file mode 100644 (file)
index 0000000..aa72c1d
--- /dev/null
@@ -0,0 +1,67 @@
+=========================================
+Feature: #67662 - DataProcessor for files
+=========================================
+
+Description
+===========
+
+A new Files DataProcessor has been introduced, which can be used to prepare data to be handled by a ContentObject
+implementing the processors, e.g. the FLUIDTEMPLATE ContentObject. The FilesProcessor resolves File References, Files,
+or Files inside a folder or collection to be used for output in the Frontend. A FLUIDTEMPLATE can then simply iterate
+over processed data automatically.
+
+
+.. code-block:: typoscript
+
+       tt_content.image.20 = FLUIDTEMPLATE
+       tt_content.image.20 {
+               file = EXT:myextension/Resources/Private/Templates/ContentObjects/Image.html
+
+               dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
+               dataProcessing.10 {
+                       # the field name where relations are set
+                       # + stdWrap
+                       references.fieldName = image
+
+                       # the table name where relations are put, defaults to the currently selected record from $cObj->getTable()
+                       # + stdWrap
+                       references.table = tt_content
+
+                       # A list of sys_file UID records
+                       # + stdWrap
+                       files = 21,42
+
+                       # A list of File Collection UID records
+                       # + stdWrap
+                       collections = 13,14
+
+                       # A list of FAL Folder identifiers and files fetched recursive from all folders
+                       # + stdWrap
+                       folders = 1:introduction/images/,1:introduction/posters/
+                       folders.recursive = 1
+
+                       # Property of which the files should be sorted after they have been accumulated
+                       # can be any property of sys_file, sys_file_metadata
+                       # + stdWrap
+                       sorting = description
+
+                       # Can be "ascending", "descending" or "random", defaults to "ascending" if none given
+                       # + stdWrap
+                       sorting.direction = descending
+
+                       # The target variable to be handed to the ContentObject again, can be used
+                       # in Fluid e.g. to iterate over the objects. defaults to "files" when not defined
+                       # + stdWrap
+                       as = myfiles
+               }
+       }
+
+In the Fluid template then iterate over the files:
+
+.. code-block:: html
+
+       <ul>
+       <f:for each="{myfiles}" as="file">
+               <li><a href="{file.publicUrl}">{file.name}</a></li>
+       </f:for>
+       </ul>
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67663-IntroduceDataProcessorForMediaGalleries.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67663-IntroduceDataProcessorForMediaGalleries.rst
new file mode 100644 (file)
index 0000000..73f2339
--- /dev/null
@@ -0,0 +1,63 @@
+=============================================================
+Feature: #67663 - Introduce DataProcessor for media galleries
+=============================================================
+
+Description
+===========
+
+The logic for working with galleries and calculating the maximum asset size is done in a separate GalleryProcessor.
+The GalleryProcessor uses the files already present in the processedData array for his calculations. The FilesProcessor can be used to fetch the files.
+
+.. code-block:: typoscript
+
+       tt_content.textmedia.20 = FLUIDTEMPLATE
+       tt_content.textmedia.20 {
+               file = EXT:myextension/Resources/Private/Templates/ContentObjects/Image.html
+
+               dataProcessing {
+
+                       # Process files
+                       10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
+
+                       # Calculate gallery info
+                       20 = TYPO3\CMS\Frontend\DataProcessing\GalleryProcessor
+                       20 {
+
+                               # filesProcessedDataKey :: Key in processedData array that holds the files (default: files) + stdWrap
+                               filesProcessedDataKey = files
+
+                               # mediaOrientation :: Media orientation, see: TCA[tt_content][column][imageorient] (default: data.imageorient) + stdWrap
+                               mediaOrientation.field = imageorient
+
+                               # numberOfColumns :: Number of columns (default: data.imagecols) + stdWrap
+                               numberOfColumns.field = imagecols
+
+                               # equalMediaHeight :: Equal media height in pixels (default: data.imageheight) + stdWrap
+                               equalMediaHeight.field = imageheight
+
+                               # equalMediaWidth :: Equal media width in pixels (default: data.imagewidth) + stdWrap
+                               equalMediaWidth.field = imagewidth
+
+                               # maxGalleryWidth :: Max gallery width in pixels (default: 600) + stdWrap
+                               maxGalleryWidth = 1000
+
+                               # maxGalleryWidthInText :: Max gallery width in pixels when orientation intext (default: 300) + stdWrap
+                               maxGalleryWidthInText = 1000
+
+                               # columnSpacing :: Column spacing width in pixels (default: 0) + stdWrap
+                               columnSpacing = 0
+
+                               # borderEnabled :: Border enabled (default: data.imageborder) + stdWrap
+                               borderEnabled.field = imageborder
+
+                               # borderWidth :: Border width in pixels (default: 0) + stdWrap
+                               borderWidth = 0
+
+                               # borderPadding :: Border padding in pixels  (default: 0) + stdWrap
+                               borderPadding = 10
+
+                               # as :: Name of key in processedData array where result is placed (default: gallery) + stdWrap
+                               as = gallery
+                       }
+               }
+       }
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67880-AddedCountToListNum.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-67880-AddedCountToListNum.rst
new file mode 100644 (file)
index 0000000..9835337
--- /dev/null
@@ -0,0 +1,23 @@
+========================================
+Feature: #67880 - Added count to listNum
+========================================
+
+Description
+===========
+
+A new property ``returnCount`` is added to the stdWrap property ``split``.
+
+When dealing with comma separated values like the content of field:records or similar,
+in some cases we need to know, how many items are present inside the csv.
+
+Example:
+
+.. code-block:: typoscript
+
+       # should return 9
+       1 = TEXT
+       1 {
+               value = x,y,z,1,2,3,a,b,c
+               split.token = ,
+               split.returnCount = 1
+       }
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-68094-DatabaseQueryDataProcessor.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-68094-DatabaseQueryDataProcessor.rst
new file mode 100644 (file)
index 0000000..5de464b
--- /dev/null
@@ -0,0 +1,61 @@
+==============================================
+Feature: #68094 - Database Query DataProcessor
+==============================================
+
+Description
+===========
+
+A new Database Query DataProcessor has been introduced, which can be used to fetch data from the Database
+to be handled by a ContentObject implementing the processors, e.g. the FLUIDTEMPLATE ContentObject.
+
+The Database Query Processor works like the code from the Content Object CONTENT, except for just handing
+over the result as array. A FLUIDTEMPLATE can then simply iterate over processed data automatically.
+
+.. code-block:: typoscript
+
+       tt_content.mycontent.20 = FLUIDTEMPLATE
+       tt_content.mycontent.20 {
+               file = EXT:myextension/Resources/Private/Templates/ContentObjects/MyContent.html
+
+               dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor
+               dataProcessing.10 {
+                       # regular if syntax
+                       if.isTrue.field = records
+
+                       # the table name from which the data is fetched from
+                       # + stdWrap
+                       table = tt_address
+
+                       # All properties from .select can be used directly
+                       # + stdWrap
+                       colPos = 1
+                       pidInList = 13,14
+
+                       # The target variable to be handed to the ContentObject again, can be used
+                       # in Fluid e.g. to iterate over the objects. defaults to "records" when not defined
+                       # + stdWrap
+                       as = myrecords
+
+                       # The fetched records can also be processed by DataProcessors.
+                       # All configured processors are applied to every row of the result.
+                       dataProcessing {
+                               10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
+                               10 {
+                                       references.fieldName = image
+                               }
+                       }
+               }
+       }
+
+In the Fluid template then iterate over the files:
+
+.. code-block:: html
+
+       <ul>
+       <f:for each="{myrecords}" as="record">
+               <li>
+                       <f:image image="{record.files.0}" />
+                       <a href="{record.data.www}">{record.data.first_name} {record.data.last_name}</a>
+               </li>
+       </f:for>
+       </ul>
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-68191-TypoScriptSelectOptionLanguageFieldIsActiveByDefault.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-68191-TypoScriptSelectOptionLanguageFieldIsActiveByDefault.rst
new file mode 100644 (file)
index 0000000..dfe1642
--- /dev/null
@@ -0,0 +1,58 @@
+==============================================================================
+Feature: #68191 - TypoScript .select option languageField is active by default
+==============================================================================
+
+Description
+===========
+
+The TypoScript .select option which is used for Content Objects like "CONTENT", has the property "languageField". This option allows to set the name of the database field that has the information about the sys_language_uid value in order to have only records shown that are translated or set to "-1" (show in all langauges) when showing translated pages.
+
+Previously this functionality had to be set explicitly:
+
+.. code-block:: typoscript
+
+       config.sys_language_uid = 2
+       page.10 = CONTENT
+       page.10 {
+               table = tt_content
+               select.where = colPos=0
+               select.languageField = sys_language_uid
+               renderObj = TEXT
+               renderObj.field = header
+               renderObj.htmlSpecialChars = 1
+       }
+
+The languageField line is not necessary anymore, as the information is now fetched automatically from the TCA information structure:
+
+.. code-block:: typoscript
+
+       config.sys_language_uid = 2
+       page.10 = CONTENT
+       page.10 {
+               table = tt_content
+               select.where = colPos=0
+               renderObj = TEXT
+               renderObj.field = header
+               renderObj.htmlSpecialChars = 1
+       }
+
+If the functionality should be disabled, this can be achieved like this:
+
+.. code-block:: typoscript
+
+       config.sys_language_uid = 2
+       page.10 = CONTENT
+       page.10 {
+               table = tt_content
+               select.where = colPos=0
+               select.languageField = 0
+               renderObj = TEXT
+               renderObj.field = header
+               renderObj.htmlSpecialChars = 1
+       }
+
+
+Impact
+======
+
+All records that have language-relevant information in the TCA "ctrl"-section displayed via .select in the frontend on translated pages are now translated by default.
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-68315-IncludeAPageTSconfigFileInPagePropertiesLikeTSStaticTemplates.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-68315-IncludeAPageTSconfigFileInPagePropertiesLikeTSStaticTemplates.rst
new file mode 100644 (file)
index 0000000..c42b2e4
--- /dev/null
@@ -0,0 +1,27 @@
+=========================================================================================
+Feature: #68315 - Include a pageTSconfig file in page properties like TS static templates
+=========================================================================================
+
+Description
+===========
+
+In the Page properties an option is added to include a page TSconfig file (the same way as TypoScript static templates are included).
+The included files from the pages in the rootline are included after the default page TSconfig and before the normal TSconfig
+from the pages in the rootline.
+To add files to the selector in the Page properties a new function ``registerPageTSConfigFile`` is added to
+``\TYPO3\CMS\Core\Utility\ExtensionManagementUtility`` to register a pageTSconfig file.
+
+
+Impact
+======
+
+No effect on existing installations.
+
+Usage
+=====
+
+In ``Configuration/TCA/Overrides/pages.php`` of any extension, register PageTS config files, which will be shown afterwards at the newly introduced field.
+
+.. code-block:: php
+
+       \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::registerPageTSConfigFile('extension_name', 'Configuration/PageTS/myPageTSconfigFile.txt', 'My special config');
diff --git a/typo3/sysext/core/Documentation/Changelog/7.4/Feature-68600-IntroducedResourceStorageSanitizeFileNameSignal.rst b/typo3/sysext/core/Documentation/Changelog/7.4/Feature-68600-IntroducedResourceStorageSanitizeFileNameSignal.rst
new file mode 100644 (file)
index 0000000..6ac1f65
--- /dev/null
@@ -0,0 +1,20 @@
+====================================================================
+Feature: #68600 - Introduced ResourceStorage SanitizeFileName signal
+====================================================================
+
+Description
+===========
+
+In order to check whether an uploaded/newly added file already exists before uploading it or to ask for
+user preferences about already existing files only when needed, the final name for the uploaded file is needed.
+
+In order to let extensions do custom sanitizing of a file name the signal ``sanitizeFileName`` is introduced in
+``TYPO3\CMS\Core\Resource\ResourceStorage``.
+The signal is emitted when ``ResourceStorage::sanitizeFileName`` or ``ResourceStorage::addFile`` are called.
+
+
+Impact
+======
+
+All installations with extensions that use the PreFileAdd signal to change/sanitize a file name.
+This logic should be moved to the new sanitizeFileName signal.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-22175-SupportIecSiUnitsInFileSizeFormatting.rst
deleted file mode 100644 (file)
index 7a4c260..0000000
+++ /dev/null
@@ -1,38 +0,0 @@
-==============================================================
-Feature: #22175 - Support IEC/SI units in file size formatting
-==============================================================
-
-Description
-===========
-
-Size formatting supports two keywords additionally to the list of labels:
-- iec: uses the Ki, Mi, etc prefixes and binary base (power of two, 1024)
-- si: uses the k, M, etc prefixes and decimal base (power of ten, 1000)
-
-The default formatting is set to "iec" base size calculations on the same base as before.
-The fractional part, when present, is changed to two numbers instead of only one.
-
-The list of labels is still supported and defaults to using binary base. It is also
-possible to explicitly choose between binary or decimal base when it is used.
-
-
-Impact
-======
-
-Default formatted output of file sizes changes, see example below.
-
-TypoScript ``stdWrap`` property ``bytes`` defaults to a different label set.
-``bytes.labels = iec``, a specifically defined label string with pipe separated
-label keywords is obsolete, but can still be used if required. The keyword
-``iec`` resolves to `` | Ki| Mi| Gi| Ti| Pi| Ei| Zi| Yi`` (binary base) and ``si`` resolves
-to `` | k| M| G| T| P| E| Z| Y`` (based on ten).
-
-
-Example
-=======
-
-.. code-block:: php
-
-       echo GeneralUtility::formatSize(85123);
-       // => Before "83.1 K"
-       // => Now "83.13 Ki"
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-33071-AddTheHttpHeaderContent-LanguageWhenRenderingAPage.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-33071-AddTheHttpHeaderContent-LanguageWhenRenderingAPage.rst
deleted file mode 100644 (file)
index 2f25f17..0000000
+++ /dev/null
@@ -1,19 +0,0 @@
-==============================================================================
-Feature: #33071 - Add the http header "Content-Language" when rendering a page
-==============================================================================
-
-Description
-===========
-
-By default a header "Content-language: XX" is sent where "XX" is the iso code of the sys_language_content if that is
-properly defined by the sys_language record representing the sys_language_uid.
-The "config.disableLanguageHeader" will disable that.
-
-
-
-Impact
-======
-
-By default in new and existing installations a header "Content-language: XX" is sent where "XX" is the iso code of the
-sys_language_content if that is properly defined by the sys_language record representing the sys_language_uid.
-You must set "config.disableLanguageHeader" to disable that and get previous behavior (no header).
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-43984-AddStdWrapFunctionalityToTreatIdAsReferenceTypoScript.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-43984-AddStdWrapFunctionalityToTreatIdAsReferenceTypoScript.rst
deleted file mode 100644 (file)
index 6e7a8d4..0000000
+++ /dev/null
@@ -1,9 +0,0 @@
-============================================================================
-Feature: #43984 - Add stdWrap functionality to TreatIdAsReference TypoScript
-============================================================================
-
-Description
-===========
-
-The new TypoScript property "treatIdAsReference" for the getImgResource object
-can now be used with stdWrap properties.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-45725-AddedRecursiveOptionToFolderBasedFileCollections.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-45725-AddedRecursiveOptionToFolderBasedFileCollections.rst
deleted file mode 100644 (file)
index afee6e7..0000000
+++ /dev/null
@@ -1,24 +0,0 @@
-=========================================================================
-Feature: #45725 - Added recursive option to folder based file collections
-=========================================================================
-
-Description
-===========
-
-Folder based file collections have now an option to fetch all files recursively for
-the given folder. The option is also available in the TypoScript Object ``FILES``.
-
-Usage:
-
-.. code-block:: typoscript
-
-       filecollection = FILES
-       filecollection {
-               folders = 1:images/
-               folders.recursive = 1
-
-               renderObj = IMAGE
-               renderObj {
-                       file.import.data = file:current:uid
-               }
-       }
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-61308-AllowPlaceholderAttribute.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-61308-AllowPlaceholderAttribute.rst
deleted file mode 100644 (file)
index 1b2370b..0000000
+++ /dev/null
@@ -1,10 +0,0 @@
-=============================================
-Feature: #61308 - Allow Placeholder attribute
-=============================================
-
-Description
-===========
-
-System extension ``form`` allows a placeholder attribute in textfields
-by adding it in a form configuration. However, there is no option to add
-placeholder using the form wizard, yet.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-61903-PageTSDataproviderForBackendLayouts.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-61903-PageTSDataproviderForBackendLayouts.rst
deleted file mode 100644 (file)
index d4644aa..0000000
+++ /dev/null
@@ -1,61 +0,0 @@
-=========================================================
-Feature: #61903 - PageTS dataprovider for backend layouts
-=========================================================
-
-Description
-===========
-
-Over the last year, several extensions appeared on TER that implemented the very same basic feature:
-Deploying backend layouts without database records by providing them via PageTS.
-
-Implement a generic PageTS provider for backend layouts to unify those approaches and to make backend layouts reusable
-across installations.
-
-
-Impact
-======
-
-It is now possible to define backend layouts via PageTSConfig on every page.
-
-
-Example
--------
-
-.. code-block:: typoscript
-
-       mod {
-               web_layout {
-                       BackendLayouts {
-                               exampleKey {
-                                       title = Example
-                                       config {
-                                               backend_layout {
-                                                       colCount = 1
-                                                       rowCount = 2
-                                                       rows {
-                                                               1 {
-                                                                       columns {
-                                                                               1 {
-                                                                                       name = LLL:EXT:frontend/Resources/Private/Language/locallang_ttc.xlf:colPos.I.3
-                                                                                       colPos = 3
-                                                                                       colspan = 1
-                                                                               }
-                                                                       }
-                                                               }
-                                                               2 {
-                                                                       columns {
-                                                                               1 {
-                                                                                       name = Main
-                                                                                       colPos = 0
-                                                                                       colspan = 1
-                                                                               }
-                                                                       }
-                                                               }
-                                                       }
-                                               }
-                                       }
-                                       icon = EXT:example_extension/Resources/Public/Images/BackendLayouts/default.gif
-                               }
-                       }
-               }
-       }
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-64200-AllowIndividualContentCaching.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-64200-AllowIndividualContentCaching.rst
deleted file mode 100644 (file)
index 77715bc..0000000
+++ /dev/null
@@ -1,61 +0,0 @@
-==================================================
-Feature: #64200 - Allow individual content caching
-==================================================
-
-Description
-===========
-
-The ``stdWrap.cache.`` property is now available as first-class function to all
-content objects. This skips the rendering even for content objects that evaluate
-``stdWrap`` after rendering (e.g. ``COA``).
-
-Usage:
-
-.. code-block:: typoscript
-
-       page = PAGE
-       page.10 = COA
-       page.10 {
-               cache.key = coaout
-               cache.lifetime = 60
-               #stdWrap.cache.key = coastdWrap
-               #stdWrap.cache.lifetime = 60
-               10 = TEXT
-               10 {
-                       cache.key = mycurrenttimestamp
-                       cache.lifetime = 60
-                       data = date : U
-                       strftime = %H:%M:%S
-                       noTrimWrap = |10: | |
-               }
-               20 = TEXT
-               20 {
-                       data = date : U
-                       strftime = %H:%M:%S
-                       noTrimWrap = |20: | |
-               }
-       }
-
-The commented part is ``stdWrap.cache.`` property available since 4.7,
-that does not stop the rendering of ``COA`` including all sub-cObjects.
-
-Additionally, stdWrap support is added to key, lifetime and tags.
-
-
-Impact
-======
-
-If you've previously used the ``cache.`` property in your custom cObject,
-this will now fail, because ``cache.`` is unset to avoid double caching.
-You are encouraged to rely on the core methods for caching cObjects or
-rename your property.
-
-``stdWrap.cache`` continues to exists and can be used as before. However
-the top level ``stdWrap`` of certain cObjects (e.g. ``TEXT`` cObject)
-will not evaluate ``cache.`` as part of ``stdWrap``, but before starting
-the rendering of the cObject. In conjunction the storing will happen
-after the ``stdWrap`` processing right before the content is returned.
-
-Top level ``cache.`` will not evaluate the hook
-``$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['stdWrap_cacheStore']``
-any more.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-65550-MakeTableDisplayOrderConfigurableInListModule.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-65550-MakeTableDisplayOrderConfigurableInListModule.rst
deleted file mode 100644 (file)
index 63ad7e4..0000000
+++ /dev/null
@@ -1,19 +0,0 @@
-======================================================================
-Feature: #65550 - Make table display order configurable in List module
-======================================================================
-
-Description
-===========
-
-The new ``PageTSconfig`` configuration option ``mod.web_list.tableDisplayOrder`` has been added
-for the List module to allow flexible configuration of the order in which tables are displayed.
-The keywords ``before`` and ``after`` can be used to specify an order relative to other table names.
-
-Example:
-
-.. code-block:: typoscript
-
-       mod.web_list.tableDisplayOrder.<tableName> {
-         before = <tableA>, <tableB>, ...
-         after = <tableA>, <tableB>, ...
-       }
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-67360-CustomAttributeNameAndMultipleValuesForMetaTags.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-67360-CustomAttributeNameAndMultipleValuesForMetaTags.rst
deleted file mode 100644 (file)
index 29f4cc8..0000000
+++ /dev/null
@@ -1,53 +0,0 @@
-=========================================================================
-Feature: #67360 - Custom attribute name and multiple values for meta tags
-=========================================================================
-
-Description
-===========
-
-``page.meta`` is extented to support different attribute names like ``property`` used for OG tags. You may also supply
-multiple values for one name, which results in multiple meta tags with the same name to be rendered.
-
-See http://ogp.me/ for more information about the Open Graph protocol and its properties.
-
-.. code-block:: typoscript
-
-    page {
-        meta {
-            X-UA-Compatible = IE=edge,chrome=1
-            X-UA-Compatible.attribute = http-equiv
-
-            keywords = TYPO3
-
-            og:site_name = TYPO3
-            og:site_name.attribute = property
-
-            description = Inspiring people to share Normal
-
-            dc\.description = Inspiring people to share [DC tags]
-
-            og:description = Inspiring people to share [OpenGraph]
-            og:description.attribute = property
-
-            og:locale = en_GB
-            og:locale.attribute = property
-
-            og:locale:alternate {
-                attribute = property
-                value {
-                    1 = fr_FR
-                    2 = de_DE
-                }
-            }
-
-            refresh = 5; url=http://example.com/
-            refresh.attribute = http-equiv
-
-        }
-    }
-
-
-Impact
-======
-
-Meta tags with a different attribute name are supported now like the Open Graph meta tags.
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-67603-IntroduceTcaDescriptionColumn.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-67603-IntroduceTcaDescriptionColumn.rst
deleted file mode 100644 (file)
index 2325ee6..0000000
+++ /dev/null
@@ -1,18 +0,0 @@
-==========================================================
-Feature: #67603 - Introduce TCA > ctrl > descriptionColumn
-==========================================================
-
-Description
-===========
-
-To annotate database table column fields as internal description for editors and admins a new setting
-for TCA is introduced. Setting is called ``['TCA']['ctrl']['descriptionColumn']`` and holds column name.
-
-This description should only displayed in the backend to guide editors and admins.
-
-Usage of descriptionColumn is added under different issues.
-
-Impact
-======
-
-None, since annotation itself is added only. Does not impact.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-67658-IntroduceDataProcessorsForSplittingValues.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-67658-IntroduceDataProcessorsForSplittingValues.rst
deleted file mode 100644 (file)
index 2d737db..0000000
+++ /dev/null
@@ -1,73 +0,0 @@
-===============================================================
-Feature: #67658 - Introduce DataProcessors for splitting values
-===============================================================
-
-Description
-===========
-
-Two new DataProcessors are added to allow flexible processing for comma-separated
-values. To use e.g. with the FLUIDTEMPLATE content object.
-
-The SplitProcessor allows to split values separated with a delimiter inside a single database field
-into an array to loop over it.
-
-The CommaSeparatedValueProcessor allows to split values into a two-dimensional array used for
-CSV files or tt_content records of CType "table".
-
-Using the SplitProcessor the following scenario is possible:
-
-.. code-block:: typoscript
-
-       page.10 = FLUIDTEMPLATE
-       page.10.file = EXT:site_default/Resources/Private/Template/Default.html
-       page.10.dataProcessing.2 = TYPO3\CMS\Frontend\DataProcessing\SplitProcessor
-       page.10.dataProcessing.2 {
-               if.isTrue.field = bodytext
-               delimiter = ,
-               fieldName = bodytext
-               removeEmptyEntries = 1
-               filterIntegers = 1
-               filterUnique = 1
-               as = keywords
-       }
-
-
-In the Fluid template then iterate over the split data:
-
-.. code-block:: html
-
-       <f:for each="{keywords}" as="keyword">
-               <li>Keyword: {keyword}</li>
-       </f:for>
-
-
-Using the CommaSeparatedValueProcessor the following scenario is possible:
-
-.. code-block:: typoscript
-
-       page.10 = FLUIDTEMPLATE
-       page.10.file = EXT:site_default/Resources/Private/Template/Default.html
-       page.10.dataProcessing.4 = TYPO3\CMS\Frontend\DataProcessing\CommaSeparatedValueProcessor
-       page.10.dataProcessing.4 {
-               if.isTrue.field = bodytext
-               fieldName = bodytext
-               fieldDelimiter = |
-               fieldEnclosure =
-               maximumColumns = 2
-               as = table
-       }
-
-
-In the Fluid template then iterate over the processed data:
-
-.. code-block:: html
-
-       <table>
-               <f:for each="{table}" as="columns">
-                       <tr>
-                               <f:for each="{columns}" as="column">
-                                       <td>{column}</td>
-                               </f:for>
-                       <tr>
-               </f:for>
-       </table>
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-67662-DataProcessorForFiles.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-67662-DataProcessorForFiles.rst
deleted file mode 100644 (file)
index aa72c1d..0000000
+++ /dev/null
@@ -1,67 +0,0 @@
-=========================================
-Feature: #67662 - DataProcessor for files
-=========================================
-
-Description
-===========
-
-A new Files DataProcessor has been introduced, which can be used to prepare data to be handled by a ContentObject
-implementing the processors, e.g. the FLUIDTEMPLATE ContentObject. The FilesProcessor resolves File References, Files,
-or Files inside a folder or collection to be used for output in the Frontend. A FLUIDTEMPLATE can then simply iterate
-over processed data automatically.
-
-
-.. code-block:: typoscript
-
-       tt_content.image.20 = FLUIDTEMPLATE
-       tt_content.image.20 {
-               file = EXT:myextension/Resources/Private/Templates/ContentObjects/Image.html
-
-               dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
-               dataProcessing.10 {
-                       # the field name where relations are set
-                       # + stdWrap
-                       references.fieldName = image
-
-                       # the table name where relations are put, defaults to the currently selected record from $cObj->getTable()
-                       # + stdWrap
-                       references.table = tt_content
-
-                       # A list of sys_file UID records
-                       # + stdWrap
-                       files = 21,42
-
-                       # A list of File Collection UID records
-                       # + stdWrap
-                       collections = 13,14
-
-                       # A list of FAL Folder identifiers and files fetched recursive from all folders
-                       # + stdWrap
-                       folders = 1:introduction/images/,1:introduction/posters/
-                       folders.recursive = 1
-
-                       # Property of which the files should be sorted after they have been accumulated
-                       # can be any property of sys_file, sys_file_metadata
-                       # + stdWrap
-                       sorting = description
-
-                       # Can be "ascending", "descending" or "random", defaults to "ascending" if none given
-                       # + stdWrap
-                       sorting.direction = descending
-
-                       # The target variable to be handed to the ContentObject again, can be used
-                       # in Fluid e.g. to iterate over the objects. defaults to "files" when not defined
-                       # + stdWrap
-                       as = myfiles
-               }
-       }
-
-In the Fluid template then iterate over the files:
-
-.. code-block:: html
-
-       <ul>
-       <f:for each="{myfiles}" as="file">
-               <li><a href="{file.publicUrl}">{file.name}</a></li>
-       </f:for>
-       </ul>
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-67663-IntroduceDataProcessorForMediaGalleries.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-67663-IntroduceDataProcessorForMediaGalleries.rst
deleted file mode 100644 (file)
index 22db04d..0000000
+++ /dev/null
@@ -1,64 +0,0 @@
-=============================================================
-Feature: #67663 - Introduce DataProcessor for media galleries
-=============================================================
-
-Description
-===========
-
-The logic for working with galleries and calculating the maximum asset size is done in a separate GalleryProcessor.
-The GalleryProcessor uses the files already present in the processedData array for his calculations. The FilesProcessor can be used to fetch the files.
-
-.. code-block:: typoscript
-
-       tt_content.text_media.20 = FLUIDTEMPLATE
-       tt_content.image.20 {
-               file = EXT:myextension/Resources/Private/Templates/ContentObjects/Image.html
-
-               dataProcessing {
-
-                       # Process files
-                       10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
-
-                       # Calculate gallery info
-                       20 = TYPO3\CMS\Frontend\DataProcessing\GalleryProcessor
-                       20 {
-
-                               # filesProcessedDataKey :: Key in processedData array that holds the files (default: files) + stdWrap
-                               filesProcessedDataKey = files
-
-                               # mediaOrientation :: Media orientation, see: TCA[tt_content][column][imageorient] (default: data.imageorient) + stdWrap
-                               mediaOrientation.field = imageorient
-
-                               # numberOfColumns :: Number of columns (default: data.imagecols) + stdWrap
-                               numberOfColumns.field = imagecols
-
-                               # equalMediaHeight :: Equal media height in pixels (default: data.imageheight) + stdWrap
-                               equalMediaHeight.field = imageheight
-
-                               # equalMediaWidth :: Equal media width in pixels (default: data.imagewidth) + stdWrap
-                               equalMediaWidth.field = imagewidth
-
-                               # maxGalleryWidth :: Max gallery width in pixels (default: 600) + stdWrap
-                               maxGalleryWidth = 1000
-
-                               # maxGalleryWidthInText :: Max gallery width in pixels when orientation intext (default: 300) + stdWrap
-                               maxGalleryWidthInText = 1000
-
-                               # columnSpacing :: Column spacing width in pixels (default: 0) + stdWrap
-                               columnSpacing = 0
-
-                               # borderEnabled :: Border enabled (default: data.imageborder) + stdWrap
-                               borderEnabled.field = imageborder
-
-                               # borderWidth :: Border width in pixels (default: 0) + stdWrap
-                               borderWidth = 0
-
-                               # borderPadding :: Border padding in pixels  (default: 0) + stdWrap
-                               borderPadding = 10
-
-                               # as :: Name of key in processedData array where result is placed (default: gallery) + stdWrap
-                               as = gallery
-                       }
-               }
-
-       }
\ No newline at end of file
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-68094-DatabaseQueryDataProcessor.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-68094-DatabaseQueryDataProcessor.rst
deleted file mode 100644 (file)
index 5de464b..0000000
+++ /dev/null
@@ -1,61 +0,0 @@
-==============================================
-Feature: #68094 - Database Query DataProcessor
-==============================================
-
-Description
-===========
-
-A new Database Query DataProcessor has been introduced, which can be used to fetch data from the Database
-to be handled by a ContentObject implementing the processors, e.g. the FLUIDTEMPLATE ContentObject.
-
-The Database Query Processor works like the code from the Content Object CONTENT, except for just handing
-over the result as array. A FLUIDTEMPLATE can then simply iterate over processed data automatically.
-
-.. code-block:: typoscript
-
-       tt_content.mycontent.20 = FLUIDTEMPLATE
-       tt_content.mycontent.20 {
-               file = EXT:myextension/Resources/Private/Templates/ContentObjects/MyContent.html
-
-               dataProcessing.10 = TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor
-               dataProcessing.10 {
-                       # regular if syntax
-                       if.isTrue.field = records
-
-                       # the table name from which the data is fetched from
-                       # + stdWrap
-                       table = tt_address
-
-                       # All properties from .select can be used directly
-                       # + stdWrap
-                       colPos = 1
-                       pidInList = 13,14
-
-                       # The target variable to be handed to the ContentObject again, can be used
-                       # in Fluid e.g. to iterate over the objects. defaults to "records" when not defined
-                       # + stdWrap
-                       as = myrecords
-
-                       # The fetched records can also be processed by DataProcessors.
-                       # All configured processors are applied to every row of the result.
-                       dataProcessing {
-                               10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
-                               10 {
-                                       references.fieldName = image
-                               }
-                       }
-               }
-       }
-
-In the Fluid template then iterate over the files:
-
-.. code-block:: html
-
-       <ul>
-       <f:for each="{myrecords}" as="record">
-               <li>
-                       <f:image image="{record.files.0}" />
-                       <a href="{record.data.www}">{record.data.first_name} {record.data.last_name}</a>
-               </li>
-       </f:for>
-       </ul>
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-68191-TypoScriptSelectOptionLanguageFieldIsActiveByDefault.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-68191-TypoScriptSelectOptionLanguageFieldIsActiveByDefault.rst
deleted file mode 100644 (file)
index dfe1642..0000000
+++ /dev/null
@@ -1,58 +0,0 @@
-==============================================================================
-Feature: #68191 - TypoScript .select option languageField is active by default
-==============================================================================
-
-Description
-===========
-
-The TypoScript .select option which is used for Content Objects like "CONTENT", has the property "languageField". This option allows to set the name of the database field that has the information about the sys_language_uid value in order to have only records shown that are translated or set to "-1" (show in all langauges) when showing translated pages.
-
-Previously this functionality had to be set explicitly:
-
-.. code-block:: typoscript
-
-       config.sys_language_uid = 2
-       page.10 = CONTENT
-       page.10 {
-               table = tt_content
-               select.where = colPos=0
-               select.languageField = sys_language_uid
-               renderObj = TEXT
-               renderObj.field = header
-               renderObj.htmlSpecialChars = 1
-       }
-
-The languageField line is not necessary anymore, as the information is now fetched automatically from the TCA information structure:
-
-.. code-block:: typoscript
-
-       config.sys_language_uid = 2
-       page.10 = CONTENT
-       page.10 {
-               table = tt_content
-               select.where = colPos=0
-               renderObj = TEXT
-               renderObj.field = header
-               renderObj.htmlSpecialChars = 1
-       }
-
-If the functionality should be disabled, this can be achieved like this:
-
-.. code-block:: typoscript
-
-       config.sys_language_uid = 2
-       page.10 = CONTENT
-       page.10 {
-               table = tt_content
-               select.where = colPos=0
-               select.languageField = 0
-               renderObj = TEXT
-               renderObj.field = header
-               renderObj.htmlSpecialChars = 1
-       }
-
-
-Impact
-======
-
-All records that have language-relevant information in the TCA "ctrl"-section displayed via .select in the frontend on translated pages are now translated by default.
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-68315-IncludeAPageTSconfigFileInPagePropertiesLikeTSStaticTemplates.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-68315-IncludeAPageTSconfigFileInPagePropertiesLikeTSStaticTemplates.rst
deleted file mode 100644 (file)
index c42b2e4..0000000
+++ /dev/null
@@ -1,27 +0,0 @@
-=========================================================================================
-Feature: #68315 - Include a pageTSconfig file in page properties like TS static templates
-=========================================================================================
-
-Description
-===========
-
-In the Page properties an option is added to include a page TSconfig file (the same way as TypoScript static templates are included).
-The included files from the pages in the rootline are included after the default page TSconfig and before the normal TSconfig
-from the pages in the rootline.
-To add files to the selector in the Page properties a new function ``registerPageTSConfigFile`` is added to
-``\TYPO3\CMS\Core\Utility\ExtensionManagementUtility`` to register a pageTSconfig file.
-
-
-Impact
-======
-
-No effect on existing installations.
-
-Usage
-=====
-
-In ``Configuration/TCA/Overrides/pages.php`` of any extension, register PageTS config files, which will be shown afterwards at the newly introduced field.
-
-.. code-block:: php
-
-       \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::registerPageTSConfigFile('extension_name', 'Configuration/PageTS/myPageTSconfigFile.txt', 'My special config');
diff --git a/typo3/sysext/core/Documentation/Changelog/master/Feature-68600-IntroducedResourceStorageSanitizeFileNameSignal.rst b/typo3/sysext/core/Documentation/Changelog/master/Feature-68600-IntroducedResourceStorageSanitizeFileNameSignal.rst
deleted file mode 100644 (file)
index 6ac1f65..0000000
+++ /dev/null
@@ -1,20 +0,0 @@
-====================================================================
-Feature: #68600 - Introduced ResourceStorage SanitizeFileName signal
-====================================================================
-
-Description
-===========
-
-In order to check whether an uploaded/newly added file already exists before uploading it or to ask for
-user preferences about already existing files only when needed, the final name for the uploaded file is needed.
-
-In order to let extensions do custom sanitizing of a file name the signal ``sanitizeFileName`` is introduced in
-``TYPO3\CMS\Core\Resource\ResourceStorage``.
-The signal is emitted when ``ResourceStorage::sanitizeFileName`` or ``ResourceStorage::addFile`` are called.
-
-
-Impact
-======
-
-All installations with extensions that use the PreFileAdd signal to change/sanitize a file name.
-This logic should be moved to the new sanitizeFileName signal.
index 72dd38c..bad3606 100644 (file)
@@ -6870,6 +6870,35 @@ TEXTLINE
 Creates a single-line text input control.
 
 
+.. _reference-textline-placeholder:
+
+placeholder
+'''''''''''
+
+.. container:: table-row
+
+   Property
+         placeholder
+
+   Data type
+         string
+
+   Description
+         The value of the placeholder attribute of the object.
+
+         **Example:**
+
+         ::
+
+            10 = TEXTLINE
+            10 {
+               name = name
+               label.value = Name
+               placeholder = Please enter your name.
+            }
+
+
+
 .. _reference-textline-label:
 
 label