This change streamlines the use of Ajax URLs
by auto-publishing all Ajax URLs to JavaScript
inline settings.

All Ajax URLs can now also be looked up in
JavaScript by providing the AjaxID like that:

var ajaxUrl = TYPO3.settings.ajaxUrls['TxMyExt::process'];

All code has been adapted to reflect this change.

Resolves: #57096
Documentation: #56347
Releases: 6.2
Change-Id: I4a441f51dcb3551874082077c52918b3fc6a9b0f
Reviewed-on: https://review.typo3.org/28602
Reviewed-by: Markus Klein
Tested-by: Markus Klein
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind

The patch removes loadConfigurationAndInitialize() from unit test
bootstrap and substitutes it with some more fine grained bootstrap
calls. In effect, the instance specific LocalConfiguration.php is
no longer loaded and removes another depencency from unit tests
to the instance.

Change-Id: Ia6591fe8d40d530558a514832c8d649c46b4ccc9
Resolves: #57035
Related: #51436
Releases: 6.2
Reviewed-on: https://review.typo3.org/28491
Reviewed-by: Helmut Hummel
Tested-by: Helmut Hummel
Reviewed-by: Markus Klein
Tested-by: Markus Klein

Some tests of GeneralUtility depend on LocalConfiguration
settings and can not easily be mocked in a sane way. They
are also not very helpfull and the functionality tested is
unlikly to break. They are removed for now.

Change-Id: Ic162e950d4df75e1b8aea63a6c547139efabdf15
Resolves: #57185
Related: #51436
Related: #57035
Releases: 6.2
Reviewed-on: https://review.typo3.org/28644
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Helmut Hummel
Tested-by: Helmut Hummel

With proper mocking in place we no longer need an
initialized database to run unit tests.

Change-Id: I3913186540bbd1b1419c37132cddaaa34ea9ca34
Related: #51436
Releases: 6.2
Reviewed-on: https://review.typo3.org/28645
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

In few tests dataproviders have duplicated array keys,
which results in some cases not being tested.
This patch removes duplicated entries and changes array
key names where needed.

Resolves: #57180
Releases: 6.2
Change-Id: I68ea38f89ed7f304b57165ca1d225ffdbe2a7a15
Reviewed-on: https://review.typo3.org/28641
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

The output of the distributions should be handled for the introduction
package and all other packages.

As there is no distinction between official (published by the Core Team)
and community-based distributions, the check is done via the username
for now, but could be easily modified in one place.

Releases: 6.2
Resolves: #57181
Change-Id: I8f2584532dda4738c66bd27e69743bcff91bc422
Reviewed-on: https://review.typo3.org/28640
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe
Reviewed-by: Wouter Wolters
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

The autoload registry entry of the form wizard
is superfluous now, so remove it.

Resolves: #57184
Releases: 6.2
Change-Id: Icc9e7a4791c5a2be95923f2e8bcad980dac611e8
Reviewed-on: https://review.typo3.org/28643
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Wouter Wolters
Tested-by: Wouter Wolters

Change-Id: I218e938c33a34c74ebd0b0720c35cd00b83d2605
Reviewed-on: https://review.typo3.org/28627
Reviewed-by: TYPO3 Release Team
Tested-by: TYPO3 Release Team

Change-Id: I3a9e09d95b86395258b32924625ed48e316b236b
Reviewed-on: https://review.typo3.org/28626
Reviewed-by: TYPO3 Release Team
Tested-by: TYPO3 Release Team

Currently Fluid treats negative integers as false which
results in <f:if condition="-9"> rendering else instead
of then.

When casting integers to boolean using php all integers
other than 0 (zero) are casted to true, just 0 results in
false. Therefore, casting of BooleanNode::convertToBoolean
must be adjusted to act like plain php.

This bugfix is a breaking change as people might have
deliberately used the wrong behaviour.

Releases: 6.2
Resolves: #54243
Resolves: #33597
Change-Id: Iebaa578cf071909610ca0e1abfc9bfaad7459231
Reviewed-on: https://review.typo3.org/26784
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader
Reviewed-by: Stefan Neufeind
Reviewed-by: Nicole Cordes
Tested-by: Nicole Cordes

The basic problem with MM (ManyToMany) relations in workspaces is
that the intermediate table (MM table) does not have any
information about actually being a reference in a particular
workspace - there is no "t3ver_wsid" field. Thus, the meaning of
a relation needs to be determined from the entities on both sides
of the relation. The following is possible:

* both sides are live -> valid in live only
* exactly one side is versioned -> valid in a workspace only
* both sides are versioned -> valid in a workspace only

The difficulties now start with versioning one side first and
after some time the other side - thus the relation with exactly
one version and one live entity needs to be turned into an entry
pointing to both versions.

Resolves: #57169
Releases: 6.2
Change-Id: Idb043d520c30f15e85d54a016e52690f5f05cedc
Reviewed-on: https://review.typo3.org/28624
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader

* general -> always use live id as pointer value
* create records -> automatically fill placeholder pointers
* copy records -> currently leads to problems with sorting
* move records -> follow and create child move placeholders
* delete records -> forward delete data in copy(!) process
* ReferenceIndex needs to hold the most specific relations
  since the CommandMap handler is based on this information
* ReleationHandler is extended for IRRE references to fetch
  the live default parent pointer automatically (this new
  behaviour can be disabled by public methods for each
  RelationHandler instance)
* The method version_swap_procBasedOnFieldType of the version
  DataHandlerHook is completely removed since IRRE records are
  now referenced using the live default parent pointer value
* UserTSconfig property options.workspaces.swapMode is set
  to "pages" per default - thus, if a page gets published all
  accordant records on that page are published as well

Resolves: #56376
Releases: 6.2
Change-Id: I75248d10b000de73ca623770f07e8c2e89d4cdd8
Reviewed-on: https://review.typo3.org/27774
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader

The version preview in the frontend rendering process basically
selects only the live versions and then overlays those records
with possible versions. Since the MM handling is changed to
directly point to the most specific version in that regard (this
is an exception to the "always live, overlay then" approach), the
versions also need to be selected directly. ContentObjectRenderer
uses the method PageRepository::enableFields() which adds an
additional SQL WHERE part, like " AND tablename.pid<>-1" to
exclude possible versions.

Besides that, elements (like sys_catagory) that are stored on the
root-level cannot be queried at all which leads to custom code in
the end just to perform these queries.

This change allows selections on the root-level and disables the
"pid<>-1" constraint if the opposite has been defined in the
pidInList property.

Example:
select.pidInList = root,-1

Resolves: #57168
Documentation: #57171
Releases: 6.2
Change-Id: I6fb91f89f70614d59c83d808f07e890833248880
Reviewed-on: https://review.typo3.org/28623
Reviewed-by: Ernesto Baschny
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader

Resolves: #56941
Releases: 6.2
Change-Id: I5dfabf2c5df8c495fbdce30cb170260d2656e6b4
Reviewed-on: https://review.typo3.org/28425
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind
Reviewed-by: Nicole Cordes
Tested-by: Nicole Cordes

It's not possible to create a backend selectbox
that is mandatory with only 1 item selectable.

Releases: 6.2, 6.1
Resolves: #24925
Resolves: #24871
Change-Id: Idaef6475f61c70cd8c3f6074ccd0b0195d90c581
Reviewed-on: https://review.typo3.org/27169
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind

There are 2 icons in the New Element wizard which should not belong there
and get the user into a blank page if the user got no access to create
page records.

- in the toolbar: icon to create a new page
- in the wizard: icon to create new page

Change-Id: I5ab638f17eebfc740ab64dd57ce655681552f901
Resolves: #56992
Releases: 6.2
Reviewed-on: https://review.typo3.org/28464
Reviewed-by: Georg Ringer
Tested-by: Georg Ringer
Reviewed-by: Wouter Wolters
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind
Reviewed-by: Nicole Cordes
Tested-by: Nicole Cordes

This patch introduces new methods to the FrontendContentAdapterServer
that allow the manipulation of the file field migration configuration.
It is now possible to add additional (content) types for which the
migration should be active and to add custom migration configurations.

Releases: 6.2
Resolves: #46067
Documentation: #56365
Change-Id: Ibc23be8a414192c8795d9bb4f09316cf608e240b
Reviewed-on: https://review.typo3.org/23360
Reviewed-by: Markus Klein
Tested-by: Markus Klein
Tested-by: Tom Peters
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind

Change-Id: Ia750e9997bb69b00652a6cc30dd3442574c0b97b
Resolves: #56007
Releases: 6.2
Reviewed-on: https://review.typo3.org/27642
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind

Extbase does some simple calls to determine the
page ID of the current request, and does not cache it.

This costs some mySQL calls, which are unneeded
once the current page ID is found. The page ID is
now stored in the ConfigurationManager to retrieve
with a simple runtime cache.

Resolves: #55566
Resolves: #57125
Releases: 6.2
Change-Id: Id5fe4a25591c77ce8a81cefa018a04e803ba7e8a
Reviewed-on: https://review.typo3.org/27243
Reviewed-by: Nicole Cordes
Tested-by: Nicole Cordes
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind

With a static table name the extension key is not updated which sets a
wrong table title for the extension before. This patch resolves table
title from configuration with a fallback to table name part and sets
group name and extension key. This helps to prevent any conflict between
different extensions.

Resolves: #23478
Releases: 6.2
Change-Id: I5f33b0a9ab616256f0b328a6d7c793677213531b
Reviewed-on: https://review.typo3.org/28510
Reviewed-by: Vladimir Podkovanov
Reviewed-by: Wouter Wolters
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind

To support a smooth upgrade from a 6.0 or 6.1 system, we have to reduce
the length if the identifier field for the key "identifier".

Resolves: #57002
Releases: 6.2
Change-Id: Ic5928ceae1f288cfb3005ad271e493f356679c82
Reviewed-on: https://review.typo3.org/28622
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind

When deleting the deprecation log file a not styled flash
message is shown afterwards. This is fixed by setting
renderMode to div.

Resolves: #57162
Releases: 6.2
Change-Id: I4ccc3620b008cd765b8fb1d124957e66aee448b5
Reviewed-on: https://review.typo3.org/28620
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny

Resolves: #57166
Releases: 6.2
Change-Id: I72aa55cff3322bbe46d271758fd04f3aba860ae7
Reviewed-on: https://review.typo3.org/28619
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

To reduce queries to accordant relations saved in the reference
index, add the current workspace that is used. This information
will be used later during publishing nested record sets (e.g.
for Inline Relational Record Editing).

Resolves: #56977
Releases: 6.2
Change-Id: I92851e243581a525bb99fafc9ed656fd613eeb82
Reviewed-on: https://review.typo3.org/28472
Reviewed-by: Wouter Wolters
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader

When you open the workspace toolbar, the bullets
of the list are shown. It should not.

Resolves: #57114
Related: #55819
Releases: 6.2
Change-Id: Ia58ddd1cd8005d6e2410c04e28a2a7b2111665c4
Reviewed-on: https://review.typo3.org/28591
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny
Reviewed-by: Wouter Wolters
Tested-by: Wouter Wolters

As annotated in the files, a refactoring is made to
remove duplicated code.

Resolves: #57072
Releases: 6.2
Change-Id: Idef2c3c194aa1659603c8b6bcc0a515ccff13a23
Reviewed-on: https://review.typo3.org/28524
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Helmut Hummel
Tested-by: Helmut Hummel

$TCA[<table>]['ctrl']['shadowColumnsForMovePlaceholders'] behaves
similar to shadowColumnsForNewPlaceholders but is only used for
move placeholders.

If shadowColumnsForMovePlaceholders is not defined in particular
for a table, but shadowColumnsForNewPlaceholders is defined,
then that value is used as a fallback - since that property
existed for a longer time already.

Resolves: #56994
Documentation: #56749
Releases: 6.2
Change-Id: Icdbd35234efae8162cfb2dc15a2838acd22370b1
Reviewed-on: https://review.typo3.org/28473
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader

Releases: 6.2
Change-Id: I3278984b1a7aa4ee704b9568f01d3ff3edf94da9
Reviewed-on: https://review.typo3.org/28617
Reviewed-by: Wouter Wolters
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny

To protect the backend from click jacking attacks
a HTTP header needs to be sent, which prevents
embedding backend pages in an iframe on domains
different than the one used to access the backend.

All recommended browsers respect this header
and prevents the backend page to be shown in an
iframe, so we do not need to implement further
JavaScript frame busting solutions.

Resolves: #54201
Documentation: #57144
Releases: 6.2
Change-Id: Ic83cae4917bb62ff8fe8b55a947ace7dba86d223
Reviewed-on: https://review.typo3.org/28601
Reviewed-by: Christian Kuhn
Reviewed-by: Markus Klein
Tested-by: Markus Klein
Reviewed-by: Wouter Wolters
Tested-by: Wouter Wolters
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny

It was previously possible to access the install tool
by using a specially crafted URL, which caused
the install tool enable file check to fail.

As there was no easy solution to solve this issue,
we now introduce the need to create a file on first
install.

So in the installation directory the following must
be present:

d typo3
f index.php
f FIRST_INSTALL

After the installation the file will be removed.

Resolves: #55387
Releases: 6.2
Change-Id: I583581f18b939ba032950451bab17ac20131683b
Reviewed-on: https://review.typo3.org/28612
Reviewed-by: Markus Klein
Tested-by: Markus Klein
Reviewed-by: Helmut Hummel
Tested-by: Helmut Hummel

The FrontendContentAdapter transforms tt_content and pages records
within cObject to the format which they have been stored in in pre
6.x installations, so probably existing legacy TypoScript config
can deal with the same data.

This patchset introduces an AllConfiguration flag allowing to disable
that service. For new installations the service is disabled by default,
upgrading installations have the service enabled.

Resolves: #54979
Releases: 6.2
Change-Id: I254f5c170c3e6a9f5ee214c0fe0e7a58e080cf34
Reviewed-on: https://review.typo3.org/26807
Reviewed-by: Markus Klein
Tested-by: Markus Klein
Reviewed-by: Alexander Stehlik
Tested-by: Alexander Stehlik
Reviewed-by: Stefan Neufeind
Reviewed-by: Steffen Ritter
Tested-by: Steffen Ritter

Resolves: #57126
Related: #55810
Releases: 6.2
Change-Id: Iea0e324b6942ec90a8da387a28ff0e7d926d63f8
Reviewed-on: https://review.typo3.org/28585
Reviewed-by: Marcin Sągol
Tested-by: Marcin Sągol
Reviewed-by: Pascal Dürsteler
Tested-by: Pascal Dürsteler
Tested-by: Christian Kuhn
Reviewed-by: Markus Klein
Tested-by: Markus Klein

Fix a failing unit test after change c23414d5

Change-Id: I427663a1a528b24a0e63d2fc9ed2a6371902a4f4
Resolves: #57159
Related: #57152
Releases: 6.2
Reviewed-on: https://review.typo3.org/28611
Reviewed-by: Markus Klein
Tested-by: Markus Klein
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe

* Cleanup code style
* Fix code issues like forgotten return values

Resolves: #53539
Releases: 6.2
Change-Id: Iec21bbb118d15e46bb464389d6a7bf3661b007a5
Reviewed-on: https://review.typo3.org/25295
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Pascal Dürsteler
Tested-by: Pascal Dürsteler
Reviewed-by: Markus Klein
Tested-by: Markus Klein

When file caches are flushed, the cache directory
is also deleted.

Now when a second request comes in and creates
the caches it happens that the cache directory of
a given cache is still there for this cache when
calling setCache in the SimpleFileBackend,
but is deleted by the first request afterwards.

Now the cache directory for the second request
does not exist and setting cache entries will fail.

Mitigate this by immediately recreating
the cache directory.

Resolves: #57136
Releases: 6.2
Change-Id: I3c4c5c63c6c754447549285d9718798272f9e585
Reviewed-on: https://review.typo3.org/28594
Reviewed-by: Ernesto Baschny
Reviewed-by: Thomas Maroschik
Reviewed-by: Pascal Dürsteler
Reviewed-by: Markus Klein
Tested-by: Markus Klein
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

For a first installer the directory structure is empty and the
first step will try to create it. We do not need to show these
as errors to the user, only if the root directory cannot be
written.

To achieve this we raise "Warnings" instead (which are
not shown in first step). To keep the Folder Structure menu
item on the left menu in the Install Tool showing a red badge
for non existing directories, we change this to also include
Warnings.

Resolves: #57152
Releases: 6.2
Change-Id: Idd628ecdf946f9befdb7fefd7a9bb7bccc175c2b
Reviewed-on: https://review.typo3.org/28605
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Wouter Wolters
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe

Additional attributes must be concatenated with a leading blank
space in order to get valid HTML content.

Fixes: #57127
Releases: 6.2
Change-Id: Iac0cf3033af37efd8e1a8efeb777083503166c5c
Reviewed-on: https://review.typo3.org/28587
Reviewed-by: Andreas Fernandez
Tested-by: Andreas Fernandez
Reviewed-by: Eric Chavaillaz
Tested-by: Eric Chavaillaz
Reviewed-by: Xavier Perseguers
Tested-by: Xavier Perseguers

On empty pages no page content is rendered at all. This patch brings the
clipboard back, if it contains elements so you can check those on the
empty pages. Besides the drawFooterHook is shown again on empty pages.
this isn't set in the core itself and extension authors should be able
to choose if the content should be visible on empty pages.

Resolves: #57062
Releases: 6.2
Change-Id: Ie7bd6fda730e801b285d7876a1eff39c3ba1eff0
Reviewed-on: https://review.typo3.org/28603
Reviewed-by: Stefan Froemken
Tested-by: Stefan Froemken
Reviewed-by: Frans Saris
Tested-by: Frans Saris

The stdWrap property escapeJsValue actually encodes the
content and should thus be called
encodeForJavaScriptValue. Also the value must be
enclosed in quotes to prevent it from being used outside
the target context of string values in JavaScript.

Releases: 6.2
Resolves: #57107
Documentation: #57108
Change-Id: Id5f850d36a87d71ca80eb58e3359ddacdd5b655e
Reviewed-on: https://review.typo3.org/28571
Reviewed-by: Helmut Hummel
Tested-by: Helmut Hummel
Reviewed-by: Xavier Perseguers
Tested-by: Xavier Perseguers

This reverts commit 07714455

This new interface is not being used throughout the Core,
as this was just the first step of three to complete this
functionality. So we revert and postpone this change for
the next release.

Change-Id: I5dd0e074a0026ff49b1d096ff4fd8926370aba3f
Reviewed-on: https://review.typo3.org/28598
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny