[BUGFIX] Show fieldname if fieldtitle is empty

Change-Id: Ie609e843031b6bfeb525b364cd401857b6fbf8c3
Resolves: #13480
Merge "[BUGFIX] Show fieldname if fieldtitle is empty"
[BUGFIX] Append Fehook output to TSFE->content

To avoid that the output of our preview hook
breaks the markup (and breaks IE7) we append it to the
TSFE->content instead of just outputting it.

Change-Id: I745c23a2f9d985440e2bb7365ecf2cee7cc22de1
Resolves: #13446
Merge "[BUGFIX] Append Fehook output to TSFE->content"
[BUGFIX] Avoid SQL error when module is opened on moved page

In case the backend module is opened on a page which was moved
within the current workspace there's a SQL error caused because
the processing for the relevant "Pagetree" runs empty.
Adding the current page to the processing can never break this part
because it will always be part of the result anyways.

Change-Id: I57d7740a4c436bf3fd44b8cc93d4ae1d9e9529b9
Resolves: #13635
Merge "[BUGFIX] Fix broken topbar switcher"
Merge "[~TASK] (FlashMessages) finish the renaming of flashMessages"
Merge "[~BUGFIX] correct annotations of Tx_Extbase_Persistence_Mapper_DataMapper"
[+BUGFIX] (Persistence) clone setDefaultQuerySettings for new queries

If you set the default querySettings object for an repository the same
instance is used for any query-object created with createQuery
method. So any repository method modificating its (normaly) own
querySettings object will also modificate the defaultQuerySettings
object. Thanks to Benjamin Schulte

Fixes: #12702

Change-Id: I9c00e064dee4349735a52e1ae01c6b5d28774fe1
[+BUGFIX] (Persistence) Make Typo3QuerySettings exchangeable

Let objectManager create querySettings object by
Tx_Extbase_Persistence_QuerySettingsInterface in
Tx_Extbase_Persistence_QueryFactory and remove obsolete instanceof
check in Typo3DbBackend

Fixes: #13191

Change-Id: I5ba9dbafeb8baa13d028fdb4f15c7bc9c6dcbd91
Merge "[+BUGFIX] (Persistence) Make Typo3QuerySettings exchangeable"
[BUGFIX] DataDictionary is not always properly instantiated

Many operations in TYPO3 backend lead to a fatal error: Call to a member function NameQuote() on a non-object.
This is due to an improper instantiation of a DataDictionary.

Change-Id: I43dc23be9045073a695ee244f5fd3a0c37247d4b
Resolves: #13691
[+FEATURE] Extbase: Enable Dependency Injection for Domain Models

In order to avoid the constructor to be called,
domain objects are created by using PHPs unserialize() function.
This has the side-effect, that we need to inject
dependencies "manually" for those.
This is accomplished by adding a helper function
getEmptyObject() to the Object Container.
Thanks to Pascal Jungblut for the patches!

Change-Id: I49edab54eb810abc894f3f59fe8c46cf4ddfa464
Fixes: #11311
Merge "[BUGFIX] Grid generates invalid id's for the group view"
[~CLEANUP] smaller deprecated clean-ups

As a backport Extbase is influenced by all the changes in FLOW. It's
important to keep both in sync and thus deprecate code which is not
in FLOW3 anymore or which has changed.

All deprecated annotations should now match the CGL and all removals
are terminated in the future.

* clean up deprecation annotation
* remove code which was deprecated long enough

Change-Id: Ic1b6217bc6c9100b6c48c5d30eca6068417265a8
[!!!][+BUGFIX] make backend-modules in web use new pagetree by default

In TYPO3 4.5 the new pagetree was introduced. It's possible to use
this in an Extbase backend-module with the config option
'navigationComponentId' in Tx_Extbase_Utility_Extension::registerModule.

With introducing this as default config for modules in 'web', we make
all Extbase based backend-modules make use of the new pagetree.

Even though this is a breaking change, all backend-modules are asked
to use the new pagetree since TYPO3 4.5 anyway.

* make navigationComponentId=typo3-pagetree default config

Change-Id: I3f08134a58bf41c7940ac3050f6b4843988a30b4
Merge "[!!!][+BUGFIX] make backend-modules in web use new pagetree by default"
[+TASK] Move FlexForm parsing to a dedicated Service

The protected FlexForm conversion methods in the FrontendConfigurationManager
are now moved to a Service class. This enables the re-use of this parsing methods
by other classes or 3rd party extensions

* move convertFlexFormContentToArray to Service class
* mark old methods deprecated
* implement unit test for FlexForm parsing

Thanks to Rens Admiraal.

Change-Id: I346e26f18d5ca5609eb69d6a869b61d746bdc9a0
Resolves: #13032
Merge "[BUGFIX] Avoid SQL error when module is opened on moved page"
Merge "[+TASK] Move FlexForm parsing to a dedicated Service"