TYPO3 v15 dev-main snapshot ()

Documentation/Changelog/8.2/Breaking-75493-EvaluateBooleanStdWrapPropertiesCorrectly.rst

@@ -0,0 +1,62 @@
+
+.. include:: /Includes.rst.txt
+
+.. _breaking-75493:
+
+===================================================================
+Breaking: #75493 - Evaluate "boolean /stdWrap" properties correctly
+===================================================================
+
+See :issue:`75493`
+
+Description
+===========
+
+stdWrap sub-properties on boolean properties were not evaluated correctly unless the
+property itself was explicitly set.
+
+Example: :typoscript:`page.10.value.prioriCalc.wrap =` without :typoscript:`page.10.value.prioriCalc =`
+
+
+Impact
+======
+
+It is now possible to reliably use stdWrap sub-properties on boolean properties.
+
+
+Affected Installations
+======================
+
+Earlier installations can be affected if they contain TypoScript that triggers the bug.
+
+Test case:
+
+.. code-block:: typoscript
+
+	page = PAGE
+	page.10 = TEXT
+	page.10.value = 1+1
+	page.10.value.prioriCalc.wrap =
+
+Result was: 2
+Correct result: 1+1
+
+For some installations, the bug fix will make the TypoScript work as intended.
+Other installations might accidentally rely on the broken code.
+
+In the latter case, the TypoScript can be changed to:
+
+.. code-block:: typoscript
+
+	page = PAGE
+	page.10 = TEXT
+	page.10.value = 1+1
+	page.10.value.prioriCalc = 1
+
+
+Migration
+=========
+
+The usage of stdWrap sub-properties on boolean properties needs to be checked and possibly adapted to fit the fixed behavior.
+
+.. index:: TypoScript, Frontend

Documentation/Changelog/8.2/Breaking-75645-DoctrineMigrateExtbackendTree.rst

@@ -0,0 +1,39 @@
+
+.. include:: /Includes.rst.txt
+
+.. _breaking-75645:
+
+=====================================================
+Breaking: #75645 - Doctrine: migrate ext:backend/Tree
+=====================================================
+
+See :issue:`75645`
+
+Description
+===========
+
+This patch changes all database related functions to use the new Doctrine database API.
+The method :php:`getDatabaseConnection()` has been removed.
+
+
+Impact
+======
+
+Calls to the method :php:`AbstractTreeView::getDataInit()` will now return :php:`Statement` objects.
+All other :php:`AbstractTreeView::getData*` methods now expect such a :php:`Statement` object
+instead of a SQL resource.
+
+
+Affected Installations
+======================
+
+All installations using TreeViews extending the AbstractTreeView.
+
+
+Migration
+=========
+
+Migrate all calls that work with the result :php:`Statement` from TreeView to be able to
+handle :php:`Statement` objects.
+
+.. index:: Database, PHP-API, Backend

Documentation/Changelog/8.2/Breaking-75710-RTE-relatedTSconfigOptionsSkipAlignAndSkipClassRemoved.rst

@@ -0,0 +1,41 @@
+
+.. include:: /Includes.rst.txt
+
+.. _breaking-75710:
+
+===============================================================================
+Breaking: #75710 - RTE-related TSconfig options skipAlign and skipClass removed
+===============================================================================
+
+See :issue:`75710`
+
+Description
+===========
+
+The two RTE-related TSconfig options :typoscript:`RTE.default.proc.skipAlign` and :typoscript:`RTE.default.proc.skipClass`
+that don't allow align and class attributes when converting content from the RTE to the database have been removed.
+
+
+Impact
+======
+
+Setting these options will have no effect anymore.
+
+
+Affected Installations
+======================
+
+Any installation setting custom TSconfig options for :typoscript:`skipAlign`, :typoscript:`skipClass` or setting
+:typoscript:`keepPDIVattribs` without :typoscript:`class` and :typoscript:`align` as values are affected.
+
+
+Migration
+=========
+
+In order to allow class and align attributes in paragraph tags, the option :typoscript:`keepPDIVattribs`
+needs to be extended to also include "class" and "align" as values, which is done by default.
+
+If an installation has custom TSconfig settings using :typoscript:`keepPDIVattribs`, the two attributes need to be added
+accordingly to still allow class and align attributes to be kept when transforming from the RTE to the database.
+
+.. index:: TSConfig, RTE, Backend

Documentation/Changelog/8.2/Breaking-75747-EXTform-RemovedUseDefaultContentObjectSetting.rst

@@ -0,0 +1,36 @@
+
+.. include:: /Includes.rst.txt
+
+.. _breaking-75747:
+
+=====================================================================
+Breaking: #75747 - EXT:form - Removed useDefaultContentObject setting
+=====================================================================
+
+See :issue:`75747`
+
+Description
+===========
+
+The TypoScript option :typoscript:`useDefaultContentObject` of the FORM cObject has been removed.
+Setting this value to 0 allowed the usage of the prehistoric content type `mailform`.
+
+
+Impact
+======
+
+It is not possible to configure the rendering of the FORM cOject. The setting is not evaluated anymore.
+
+
+Affected Installations
+======================
+
+Any installation that uses the TypoScript option :typoscript:`useDefaultContentObject = 0`.
+
+
+Migration
+=========
+
+Remove the TypoScript option from any TypoScript settings. Migrate manually to use the features of EXT:form.
+
+.. index:: TypoScript, ext:form

Documentation/Changelog/8.2/Breaking-75760-ReturnTypeOfGetRecordsToCopyDatabaseResultChanged.rst

@@ -0,0 +1,44 @@
+
+.. include:: /Includes.rst.txt
+
+.. _breaking-75760:
+
+================================================================================================
+Breaking: #75760 - Return type of LocalizationRepository::getRecordsToCopyDatabaseResult changed
+================================================================================================
+
+See :issue:`75760`
+
+Description
+===========
+
+The return type of :php:`LocalizationRepository::getRecordsToCopyDatabaseResult()`
+has changed. Instead of returning either :php:`bool`, :php:`\mysqli_result`
+or :php:`object` the return value always is a :php:`\Doctrine\DBAL\Driver\Statement`.
+
+
+Impact
+======
+
+Using the mentioned method will not yield the expected result type.
+
+
+Affected Installations
+======================
+
+Any installation with a 3rd party extension that uses the named method.
+
+
+Migration
+=========
+
+Change the way the result is being used to conform to the Doctrine API:
+
+.. code-block:: php
+
+    $result = $this->localizationRepository->getRecordsToCopyDatabaseResult(...);
+    while ($row = $result->fetch()) {
+        // Do something here
+    }
+
+.. index:: Database, Frontend, Backend, PHP-API

Documentation/Changelog/8.2/Breaking-76285-PopupConfigurationIsMovedToTYPO3settings.rst

@@ -0,0 +1,47 @@
+
+.. include:: /Includes.rst.txt
+
+.. _breaking-76285:
+
+=================================================================
+Breaking: #76285 - Popup configuration is moved to TYPO3.settings
+=================================================================
+
+See :issue:`76285`
+
+Description
+===========
+
+The popup window configuration has been moved to `TYPO3.settings`.
+
+The following configuration options are not working anymore.
+
+* :js:`top.TYPO3.configuration.RTEPopupWindow.width`
+* :js:`top.TYPO3.configuration.RTEPopupWindow.height`
+* :js:`top.TYPO3.configuration.PopupWindow.width`
+* :js:`top.TYPO3.configuration.PopupWindow.height`
+
+
+Impact
+======
+
+Width and height are not set correctly anymore in JavaScript context.
+
+
+Affected Installations
+======================
+
+Extensions that use one of the mentioned configurations.
+
+
+Migration
+=========
+
+The migration can be done with the following replacements.
+
+* :js:`top.TYPO3.configuration.RTEPopupWindow.width` to :js:`TYPO3.settings.Textarea.RTEPopupWindow.width`
+* :js:`top.TYPO3.configuration.RTEPopupWindow.height` to :js:`TYPO3.settings.Textarea.RTEPopupWindow.height`
+* :js:`top.TYPO3.configuration.PopupWindow.width` to :js:`TYPO3.settings.Popup.PopupWindow.width`
+* :js:`top.TYPO3.configuration.PopupWindow.height` to :js:`TYPO3.settings.Popup.PopupWindow.height`
+
+.. index:: JavaScript, Backend

Documentation/Changelog/8.2/Breaking-76469-DoctrineMigrateExtImpExp.rst

@@ -0,0 +1,38 @@
+
+.. include:: /Includes.rst.txt
+
+.. _breaking-76469:
+
+===============================================
+Breaking: #76469 - Doctrine: migrate ext:ImpExp
+===============================================
+
+See :issue:`76469`
+
+Description
+===========
+
+The return type of :php:`ImportExportController::exec_listQueryPid()`
+has changed. Instead of returning either :php:`bool`, :php:`\mysqli_result`
+or :php:`object` the return value always is a :php:`\Doctrine\DBAL\Driver\Statement`.
+
+
+Impact
+======
+
+Using the mentioned method will not yield the expected result type.
+
+
+Affected Installations
+======================
+
+All installations with a 3rd party extension using :php:`ImportExportController::exec_listQueryPid()`.
+
+
+Migration
+=========
+
+Migrate all calls that work with the result of :php:`ImportExportController::exec_listQueryPid()`
+to be able to handle :php:`\Doctrine\DBAL\Driver\Statement` objects.
+
+.. index:: Database, PHP-API

Documentation/Changelog/8.2/Breaking-76527-CleanupContextMenuClasses.rst

@@ -0,0 +1,35 @@
+
+.. include:: /Includes.rst.txt
+
+.. _breaking-76527:
+
+==============================================
+Breaking: #76527 - Cleanup ContextMenu classes
+==============================================
+
+See :issue:`76527`
+
+Description
+===========
+
+The classes of the ContextMenu (used in page tree) have been refactored.
+The following classes have been removed:
+
+* :php:`\TYPO3\CMS\Backend\ContextMenu\AbstractContextMenu`
+* :php:`\TYPO3\CMS\Backend\ContextMenu\AbstractContextMenuDataProvider`
+* :php:`\TYPO3\CMS\Backend\ContextMenu\Extdirect\AbstractExtdirectContextMenu`
+* :php:`\TYPO3\CMS\Backend\ContextMenu\Renderer\AbstractContextMenuRenderer`
+
+
+Impact
+======
+
+Extensions which use one of the classes above will stop working.
+
+
+Affected Installations
+======================
+
+All installations with a 3rd party extension using one of the classes above.
+
+.. index:: PHP-API, Backend

Documentation/Changelog/8.2/Breaking-76802-DropXcacheCacheBackend.rst

@@ -0,0 +1,44 @@
+
+.. include:: /Includes.rst.txt
+
+.. _breaking-76802:
+
+============================================
+Breaking: #76802 - Drop xcache cache backend
+============================================
+
+See :issue:`76802`
+
+Description
+===========
+
+The `xcache` core cache backend has been dropped because PHP7 does no longer support xcache.
+
+
+Impact
+======
+
+Instances will throw an exception or a fatal error using a cache with this backend configured.
+
+
+Affected Installations
+======================
+
+Instances that still use a configuration in :file:`LocalConfiguration.php` or :file:`AdditionalConfiguration.php` like:
+
+.. code-block:: php
+
+    'SYS' => [
+        'caching' => [
+            'cacheConfigurations' => [
+                'aCache' => [
+                    'backend' => 'TYPO3\\CMS\\Core\\Cache\\Backend\\XcacheBackend',
+
+
+Migration
+=========
+
+Affected instances must switch to a different cache backend, `APCU` `PHP` module with `ApcuBackend`
+provides the same local server in memory characteristics like `xcache` and should be considered as alternative.
+
+.. index:: LocalConfiguration

Documentation/Changelog/8.2/Deprecation-15415-DeprecateRemoveBadHTML.rst

@@ -0,0 +1,41 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-15415:
+
+=============================================
+Deprecation: #15415 - Deprecate removeBadHTML
+=============================================
+
+See :issue:`15415`
+
+Description
+===========
+
+Due to the wrong approach of removeBadHTML it is not 100% complete and does not keep its promise.
+
+-  :php:`ContentObjectRenderer::stdWrap_removeBadHTML()`
+-  :php:`ContentObjectRenderer::removeBadHTML()`
+-  :typoscript:`stdWrap.removeBadHTML`
+
+
+Impact
+======
+
+Using the mentioned method or stdWrap property will trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+Instances that use the method or stdWrap property.
+
+
+Migration
+=========
+
+Implement a proper encoding by yourself. Use :php:`htmlspecialchars()` or :typoscript:`stdWrap.htmlSpecialChars`
+in the context of HTML, :php:`GeneralUtility::quoteJSvalue()` or :typoscript:`stdWrap.encodeForJavaScriptValue`
+in the context of JavaScript.
+
+.. index:: Frontend, TypoScript, PHP-API

Documentation/Changelog/8.2/Deprecation-71917-DeprecateTheArgumentHscForGetLLGetLLLAndSL.rst

@@ -0,0 +1,43 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-71917:
+
+=====================================================================================
+Deprecation: #71917 - Deprecate the argument 'hsc' for getLL, getLLL, sL and pi_getLL
+=====================================================================================
+
+See :issue:`71917`
+
+Description
+===========
+
+The parameter :php:`$hsc` within the following methods of :php:`TYPO3\CMS\Lang\LanguageService` has been marked as deprecated:
+
+* :php:`getLL()`
+* :php:`getLLL()`
+* :php:`sL()`
+
+The parameter :php:`$hsc` within the following method of :php:`TYPO3\CMS\Frontend\Plugin\AbstractPlugin` has been marked as deprecated:
+
+* :php:`pi_getLL()`
+
+
+Impact
+======
+
+Directly or indirectly using any of the methods :php:`getLL()`, :php:`getLLL()`, :php:`sL()` or :php:`pi_getLL()` with the parameter :php:`$hsc` will trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+Any installation with a third-party extension calling one of the methods in its PHP code.
+
+
+Migration
+=========
+
+If the return value of these methods is output in HTML context use :php:`htmlspecialchars` directly to properly escape the content.
+
+.. index:: Frontend, Backend, PHP-API

Documentation/Changelog/8.2/Deprecation-72859-DeprecateMethodsOfDocumentTemplate.rst

@@ -0,0 +1,56 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-72859:
+
+===========================================================
+Deprecation: #72859 - Deprecate methods of DocumentTemplate
+===========================================================
+
+See :issue:`72859`
+
+Description
+===========
+
+The following methods within `DocumentTemplate` have been marked as deprecated:
+
+* viewPageIcon()
+* getHeader()
+* getResourceHeader()
+* header()
+* icons()
+* t3Button()
+* wrapScriptTags()
+* loadJavascriptLib()
+* getContextMenuCode()
+
+The following property within `DocumentTemplate` has been marked as deprecated:
+
+* sectionFlag (is internal)
+
+
+Impact
+======
+
+Calling any of the methods above will trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+Any installation with a 3rd party extension calling one of the methods in its PHP code.
+
+
+Migration
+=========
+
+Instead of :php:`wrapScriptTags()` use :php:`GeneralUtility::wrapJS`.
+
+Instead of :php:`getContextMenuCode()` use:
+
+.. code-block:: php
+
+    $this->getPageRenderer()->loadJquery();
+    $this->getPageRenderer()->loadRequireJsModule('TYPO3/CMS/Backend/ClickMenu');
+
+.. index:: Backend, PHP-API

Documentation/Changelog/8.2/Deprecation-75209-CodecleanupForMenuViewHelperTrait.rst

@@ -0,0 +1,36 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-75209:
+
+==========================================================
+Deprecation: #75209 - Code cleanup for MenuViewHelperTrait
+==========================================================
+
+See :issue:`75209`
+
+Description
+===========
+
+The `MenuViewHelperTrait` has been marked as deprecated.
+All methods of the Trait have been implemented in a new `AbstractMenuViewHelper` class.
+
+
+Impact
+======
+
+Using the methods of the `MenuViewHelperTrait` will trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+Instances with custom extensions that use the `MenuViewHelperTrait`.
+
+
+Migration
+=========
+
+Extend the new `AbstractMenuViewHelper` which contains all methods instead of using the trait.
+
+.. index:: Frontend, PHP-API, ext:fluid_styled_content

Documentation/Changelog/8.2/Deprecation-75760-DeprecateMethodsOfLocalizationRepository.rst

@@ -0,0 +1,48 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-75760:
+
+=================================================================
+Deprecation: #75760 - Deprecate methods of LocalizationRepository
+=================================================================
+
+See :issue:`75760`
+
+Description
+===========
+
+The following methods have been marked as deprecated:
+
+- :php:`LocalizationRepository::getExcludeQueryPart()`
+- :php:`LocalizationRepository::getAllowedLanguagesForBackendUser()`
+
+
+Impact
+======
+
+Using the mentioned methods will trigger a deprecation log entry
+
+
+Affected Installations
+======================
+
+Any installation with a 3rd party extension that uses one of the named methods.
+
+
+Migration
+=========
+
+Instead of :php:`LocalizationRepository::getExcludeQueryPart()` configure the query restrictions yourself:
+
+.. code-block:: php
+
+    $queryBuilder->getRestrictions()
+        ->removeAll()
+        ->add(GeneralUtility::makeInstance(DeletedRestriction::class))
+        ->add(GeneralUtility::makeInstance(BackendWorkspaceRestriction::class));
+
+Instead of :php:`LocalizationRepository::getAllowedLanguagesForBackendUser()` add
+the required conditions to your query yourself.
+
+.. index:: PHP-API, Backend, Database

Documentation/Changelog/8.2/Deprecation-75904-CategoryModelHasIconPropertyButNoDatabaseField.rst

@@ -0,0 +1,36 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-75904:
+
+============================================================================
+Deprecation: #75904 - Category Model has icon property but no database field
+============================================================================
+
+See :issue:`75904`
+
+Description
+===========
+
+Methods :php:`\TYPO3\CMS\Extbase\Domain\Model\Category::getIcon` and
+:php:`\TYPO3\CMS\Extbase\Domain\Model\Category::setIcon` have been marked as deprecated.
+
+
+Impact
+======
+
+Using the methods will trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+Instances with custom extensions that use these methods.
+
+
+Migration
+=========
+
+Implement the methods by yourself.
+
+.. index:: PHP-API, Frontend, Backend, ext:extbase

Documentation/Changelog/8.2/Deprecation-76101-RemoveSoloFieldContainer.rst

@@ -0,0 +1,36 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-76101:
+
+===============================================
+Deprecation: #76101 - remove SoloFieldContainer
+===============================================
+
+See :issue:`76101`
+
+Description
+===========
+
+The `render()` method of the `SoloFieldContainer` class has been marked as deprecated.
+It is not used in core anymore.
+
+
+Impact
+======
+
+Using the method will trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+Instances with custom extensions that use `render()` from `SoloFieldContainer`.
+
+
+Migration
+=========
+
+Use the render method from the ListOfFieldsContainer class.
+
+.. index:: PHP-API, Backend

Documentation/Changelog/8.2/Deprecation-76104-Deprecated-Single-Slash-Comments-In-TypoScript.rst

@@ -0,0 +1,48 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-76104:
+
+====================================================================
+Deprecation: #76104 - Deprecated single slash comments in TypoScript
+====================================================================
+
+See :issue:`76104`
+
+Description
+===========
+
+Double slash one-line comments are standard in many languages.
+Make them standard for TypoScript, too.
+
+Define::
+
+   One-line comments must start with two forward slashes as
+   the first non-blank characters and should be followed by
+   a whitespace.
+
+
+Deprecated::
+
+   / Line comment headed by single slash
+
+
+Impact
+======
+
+The TypoScript developer receives a deprecation warning
+with line number.
+
+
+Affected Installations
+======================
+
+Installations using a single slash to indicate a comment.
+
+
+Migration
+=========
+
+Use double slashes (//) or hash (#) for comments in Typoscript.
+
+.. index:: TypoScript, Frontend

Documentation/Changelog/8.2/Deprecation-76164-DeprecateRemoveXSS.rst

@@ -0,0 +1,41 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-76164:
+
+=========================================
+Deprecation: #76164 - Deprecate RemoveXSS
+=========================================
+
+See :issue:`76164`
+
+Description
+===========
+
+Due to the wrong approach of RemoveXSS it is not 100% secure and does not keep its
+promise. The following methods have been marked as deprecated:
+
+- :php:`\TYPO3\CMS\Core\Utility\GeneralUtility::removeXSS()`
+- :php:`\RemoveXSS::process()`
+- :php:`\TYPO3\CMS\Form\Domain\Filter\RemoveXssFilter`
+
+
+Impact
+======
+
+Using the mentioned methods will trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+Instances that use any of these methods.
+
+
+Migration
+=========
+
+Implement a proper encoding by yourself. Use :php:`htmlspecialchars()` in the
+context of HTML or :php:`GeneralUtility::quoteJSvalue()` in the context of JavaScript.
+
+.. index:: PHP-API

Documentation/Changelog/8.2/Deprecation-76345-PathPrefixesInCallUserFunctionAndGetUserObj.rst

@@ -0,0 +1,43 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-76345:
+
+======================================================================
+Deprecation: #76345 - Path prefixes in callUserFunction and getUserObj
+======================================================================
+
+See :issue:`76345`
+
+Description
+===========
+
+The two methods :php:`GeneralUtility::callUserFunc()` and :php:`GeneralUtility::getUserObj()` allow the first parameter to
+contain a file reference to the function/class to be called if prefixed with a colon.
+
+An example would be :php:`EXT:myext/Classes/MyClass.php:Benni\Myext\MyClass` for including the class.
+
+Having the reference to the actual file is not needed since the composer autoloading mechanism takes care
+of loading everything properly already since TYPO3 6.2.9.
+
+
+Impact
+======
+
+Calling one of the methods above with a file reference prepended to the class name / function name will
+trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+Any installation with a hook that is registered with the file prefix functionality.
+
+
+Migration
+=========
+
+Remove the file prefix when registering a hook and make use of the common autoloading functionality of
+composer or via the fallback autoloader by TYPO3 to achieve the same functionality automatically.
+
+.. index:: Frontend, Backend, PHP-API

Documentation/Changelog/8.2/Deprecation-76370-DeprecateCacheFactory.rst

@@ -0,0 +1,36 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-76370:
+
+============================================
+Deprecation: #76370 - Deprecate CacheFactory
+============================================
+
+See :issue:`76370`
+
+Description
+===========
+
+Class :php:`CacheFactory` has been deprecated.
+
+
+Impact
+======
+
+The class is no longer used or instantiated by the core.
+Instantiating the class will trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+TYPO3 instances and extensions typically make no use of this internal class.
+
+
+Migration
+=========
+
+Nothing notable, do not use this class anymore.
+
+.. index:: PHP-API

Documentation/Changelog/8.2/Deprecation-76383-DeprecateFontTag.rst

@@ -0,0 +1,39 @@
+
+.. include:: /Includes.rst.txt
+
+.. _deprecation-76383:
+
+=======================================
+Deprecation: #76383 - Deprecate fontTag
+=======================================
+
+See :issue:`76383`
+
+Description
+===========
+
+Font tags are not used any more in HTML since years.
+
+-  :php:`ContentObjectRenderer::stdWrap_fontTag()`
+-  :typoscript:`stdWrap.fontTag``
+
+
+Impact
+======
+
+Using the mentioned method or stdWrap property will trigger a deprecation log entry.
+
+
+Affected Installations
+======================
+
+Instances that use the method or stdWrap property.
+
+
+Migration
+=========
+
+Update HTML to not output font tags. Use CSS instead. In case you really want to use the font tag,
+it can be created by :typoscript:`stdWrap.wrap`.
+
+.. index:: Frontend, PHP-API, TypoScript

Documentation/Changelog/8.2/Feature-18586-ConfigurableWidthHeightForEditpanelInFeedit.rst

@@ -0,0 +1,23 @@
+
+.. include:: /Includes.rst.txt
+
+.. _feature-18586:
+
+=====================================================================
+Feature: #18586 - Configurable width & height for editpanel in feedit
+=====================================================================
+
+See :issue:`18586`
+
+Description
+===========
+
+It is possible to change the popup's width and height which is used in the edit panel
+of EXT:feedit by using User TsConfig:
+
+.. code-block:: typoscript
+
+	options.feedit.popupHeight = 700
+	options.feedit.popupWidth = 900
+
+.. index:: TSConfig, ext:feedit

Documentation/Changelog/8.2/Feature-20446-ClearCacheEntryInContextMenu.rst

@@ -0,0 +1,18 @@
+
+.. include:: /Includes.rst.txt
+
+.. _feature-20446:
+
+===================================================
+Feature: #20446 - Clear cache entry in context menu
+===================================================
+
+See :issue:`20446`
+
+Description
+===========
+
+A new entry has been added in the context menu of the page tree to be able to clear
+the cache of the selected page. The entry is located inside "Page Actions".
+
+.. index:: Backend

Documentation/Changelog/8.2/Feature-76008-PropertyVisibilityToDebuggerUtilityvar_dump.rst

@@ -0,0 +1,18 @@
+
+.. include:: /Includes.rst.txt
+
+.. _feature-76008:
+
+==================================================================
+Feature: #76008 - Property visibility to DebuggerUtility::var_dump
+==================================================================
+
+See :issue:`76008`
+
+Description
+===========
+
+The property visibility information has been added to `DebuggerUtility::var_dump()`
+for each object property in the dump.
+
+.. index:: PHP-API, ext:extbase

Documentation/Changelog/8.2/Feature-76072-OggFlacAndOpusSupport.rst

@@ -0,0 +1,21 @@
+
+.. include:: /Includes.rst.txt
+
+.. _feature-76072:
+
+============================================
+Feature: #76072 - Ogg, flac and opus support
+============================================
+
+See :issue:`76072`
+
+Description
+===========
+
+Support for the following open formats has been added to the media field:
+
+* ogg
+* flac
+* opus
+
+.. index:: Frontend, Backend

Documentation/Changelog/8.2/Feature-76458-LetDebuggerUtilityRenderClosures.rst

@@ -0,0 +1,23 @@
+
+.. include:: /Includes.rst.txt
+
+.. _feature-76458:
+
+=====================================================
+Feature: #76458 - Let DebuggerUtility render closures
+=====================================================
+
+See :issue:`76458`
+
+Description
+===========
+
+The `DebuggerUtility` of Extbase is now able to render closures.
+
+
+Impact
+======
+
+If a closure is part of the debugging object, the source code of the closure is rendered.
+
+.. index:: PHP-API, ext:extbase

Documentation/Changelog/8.2/Feature-76531-AddIconForRecordViewHelper.rst

@@ -0,0 +1,20 @@
+
+.. include:: /Includes.rst.txt
+
+.. _feature-76531:
+
+=============================================
+Feature: #76531 - Add IconForRecordViewHelper
+=============================================
+
+See :issue:`76531`
+
+Description
+===========
+
+A new ViewHelper to render icons for records has been added.
+Now it is possible to render icons for records in fluid.
+
+`<core:iconForRecord table="tt_content" row="{recordRow}" />`
+
+.. index:: Fluid

Documentation/Changelog/8.2/Feature-76590-IntroduceUnitTestsForJavaScript.rst

@@ -0,0 +1,76 @@
+
+.. include:: /Includes.rst.txt
+
+.. _feature-76590:
+
+====================================================
+Feature: #76590 - Introduce UnitTests for JavaScript
+====================================================
+
+See :issue:`76590`
+
+Description
+===========
+
+The core uses karma as test runner and jasmine as testing framework for JavaScript UnitTests.
+The tests will be run on travis with PhantomJS.
+Locally other browsers like Chrome, Firefox, Safari or IE can be used as well.
+
+To run the UnitTests on a local system the following steps are necessary:
+
+1. Install dependencies
+
+.. code-block:: bash
+
+   cd Build
+   npm install
+   cd ..
+
+2. Run the tests from your terminal
+
+.. code-block:: bash
+
+   # Execute the tests only once
+   ./Build/node_modules/karma/bin/karma start typo3/sysext/core/Build/Configuration/JSUnit/karma.conf.js --single-run
+
+   # Execute the tests for every change (file watcher mode)
+   ./Build/node_modules/karma/bin/karma start typo3/sysext/core/Build/Configuration/JSUnit/karma.conf.js
+
+   # Execute the tests for different browser
+   ./Build/node_modules/karma/bin/karma start typo3/sysext/core/Build/Configuration/JSUnit/karma.conf.js --single-run --browsers Chrome,Safari,Firefox
+
+
+Test-Files
+==========
+
+Any test file must be located in extension folder `typo3/sysext/<EXTKEY>/Tests/JavaScript/`
+The filename must end with Test.js, e.g. `GridEditorTest.js`
+Each test file must be implemented as AMD module, must use strict mode and has to use :js:`describe` with module name as outer wrap for each test.
+The following code block shows a good example:
+
+.. code-block:: javascript
+
+   define(['jquery', 'TYPO3/CMS/Backend/AnyModule'], function($, AnyModule) {
+      'use strict';
+      // first and outer wrap describe the test class name
+      describe('TYPO3/CMS/Backend/AnyModuleTest:', function() {
+         // second wrap describe the method to test
+         describe('tests for fooAction', function() {
+            // the first parameter of each 'it' method describe the test-case.
+            it('works for parameter a and b', function() {});
+         });
+         describe('tests for barAction', function() {
+            it('works for parameter a and b', function() {});
+         });
+      }
+   }
+
+Please take a look at the existing test files and read the jasmine documentation for further information.
+
+DataProvider for tests
+----------------------
+
+For testing a set of values, the core implement a kind of DataProvider. To use the DataProvider you have to use the function :js:`using`.
+Please take a look at `FormEngineValidationTest.js` for an example.
+
+.. index:: JavaScript

Documentation/Changelog/8.2/Important-75747-EXTform-RemovedSupportForCompatibility6.rst

@@ -0,0 +1,19 @@
+
+.. include:: /Includes.rst.txt
+
+.. _important-75747:
+
+=================================================================
+Important: #75747 - EXT:form - Removed support for compatibility6
+=================================================================
+
+See :issue:`75747`
+
+Description
+===========
+
+EXT:compatibility6 contains the prehistoric CType `mailform`. Since compatibility6 is
+not available for TYPO3 v8 the compatibility between EXT:form and the prehistoric
+CType `mailform` has been removed.
+
+.. index:: Frontend, ext:form, TypoScript

Documentation/Changelog/8.2/Index.rst

@@ -0,0 +1,52 @@
+:template: changelogOverview.html
+.. include:: /Includes.rst.txt
+..  _changelog-8-2:
+
+8.2 Changes
+===========
+
+**Table of contents**
+
+.. contents::
+   :local:
+   :depth: 1
+
+Breaking Changes
+^^^^^^^^^^^^^^^^
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Breaking-*
+
+Features
+^^^^^^^^
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Feature-*
+
+Deprecation
+^^^^^^^^^^^
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Deprecation-*
+
+Important
+^^^^^^^^^
+
+.. toctree::
+   :maxdepth: 1
+   :titlesonly:
+   :glob:
+
+   Important-*