To solve this, the corresponding argument definition of Image-
and Media-ViewHelper render methods has been changed to object.
Type validation of these arguments in question is done inside
the corresponding methods.

The Extbase ClassInfoFactory may be unable to build information for a
given class if a PHP warning occurs while running in development context.

Instead of hiding the actual exception with a generic message
"Could not analyse class: VendorName\ExtensionKey\Some\Class", it should
include the message of the corresponding exception to give useful advice
while fixing the problem.

There is a leftover stub run from the global scope to ensure
that the hook uses the proper backend charset. This code
was never executed in the current version of crawler, but
still may be viable in some situations. Therefore it is added
to the constructor method of the actual Crawler Hook.

This adds an initialisation line to AbstractTemplateView which
passes the Request's format attribute value to the TemplatePaths
which are responsible for resolving the template file. Without it,
controllers were not able to render Requests using a format other
than html.

On a more general level the change allows using a wide array of
new template syntaxes and integration features (see feature
documentation included with this commit in `core` extension).

The breaking changes are minimal; mostly caused by removal of
deprecated code from the `fluid` system extension (rather than
fundamental changes to how Fluid itself works). Custom templates
should work with little or no migration required.

The folder icons are now also shown in the ElementBrowser file tree,
but without context-menu. As the icon link handling provided by the
general FolderTree wrapIcon function does not match in ElementBrowser
mode, an own implementation of this function is introduced in
ElementBrowserFolderTreeView.

Move labels and legends to their own partials. This step is slightly
(but thankfully) breaking. The patch allows to avoid duplicate/
redundant code and helps the integrator to override the labels/ legends
with just one small override.

The patch contains one problem with logDeprecatedFunction call.
Also we decided to not move this methods because it will be incredible
hard or at least annoying for ext devs to deprecate own functionality
with this API change.

The introduction of typo3temp/var and typo3temp/assets missed
essential changes.

* Files generated by tests
* Install Tool cleared wrong directory
* Some paths were only changed partially
* Some paths were changed to the public dir, but should in fact be private
* Some paths have been completely forgotten to be changed

Besides that, the introduction of new subfolder in typo3temp, we need
to allow arbitrary number of subfolders and remove the limitation of two
in GeneralUtility::writeFileToTypo3tempDir

This patch fix the declaration of
TYPO3\CMS\Dbal\RecordList\DatabaseRecordList::makeSearchString
to be compatible with the parent method:
TYPO3\CMS\Recordlist\RecordList\AbstractDatabaseRecordList::makeSearchString

The comment for the method
\TYPO3\CMS\Core\Cache\Backend\SimpleFileBackend::setCacheDirectory()
states clearly, that it is possible to provide an absolute path as
cache directory. However, in the lower part of the function, it is
stated, that if ($cacheDirectory0 == '/') the documentRoot should be
set to '/'. That results in a returned path like '//...'.
This causes problems within
\TYPO3\CMS\Core\Utility\GeneralUtility::validPathStr(), because pathes
with '//' in it are always invalid.

The option to re-convert htmlspecialchars() between transformations
RTE and DB is always on, in order to clean HTML is always turned
on, meaning that the HTMLcleaner() method will not do htmlspecialchars() at all by default.

As these additional options is now obsolete with the current rtehtmlarea
extension (thus, always "enabled"), the options are removed.

This patchset removes the compatibility layer of EXT:form. The layer
made sure that EXT:form acts almost like in TYPO3 6.2. This mainly
applies to the layout configuration and rendering.
In the former days integrators could use .layout settings on different
levels to change the output of the form elements in the frontend. The
whole process is not intuitive and not well documented.
Nowadyas integrators should use fluid templates to customize their
forms. With this patchset this is the only way to go.

Furthermore the SELECT, TEXTAREA and TEXTBLOCK elements are adjusted.
The automatic transformation of the .data and .content attribute is
removed. That way .text is the only valid attribute for adding a human
readable text to the above mentioned elements.
Using the old attribute causes no harm.
There will be neither an output nor an error message.

The rtehtmlarea RTE shipped with the TYPO3 Core does not
work with the RTE options "useDIVasParagraphTagForRTE"
and "remapParagraphTag" which allowed the content sent to the
RTE to use <div> tags or no tags instead of the regular <p>
tags.

Using these options before resulted in having multiple <div>
tags added every time the contents of the RTE were saved
to the database.

Since the RTE does not support this functionality, nor does
it make any sense, it is removed.

The TYPO3 frontend resolves
config.locale_all (e.g. set to de_AT.UTF-8) and stores
it in $TSFE->localeCharset by using a "best guess" based
on decade-old mappings.

$TSFE->localeCharset is only used in stdWrap.strftime
to convert the result from the localeCharset to the ->renderCharset.

However, as it is obvious that a misconfiguration of the system, which happens only when
config.set_locale = de_AT@iso-8859-15
config.renderCharset = utf-8
is set, this exception needs to be configured manually
when using stdWrap.strftime.charset = iso-8859-15