The Package Manager from Flow has been backported and integrated as
CMS Package Manager. This enables us to use full vendor namespaces for
extensions and brings us closer to a unified TYPO3 package format.

For more Details see: http://wiki.typo3.org/Blueprints/Packagemanager

Resolves: #47018
Releases: 6.2
Change-Id: I52abedaf470cebddb3553e37581021bf368380e6
Reviewed-on: https://review.typo3.org/19605
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Alexander Opitz
Reviewed-by: Sascha Egerer
Reviewed-by: Thomas Maroschik
Tested-by: Thomas Maroschik
Tested-by: Alexander Opitz
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny

Two unit tests failed after the patch. This is fixed by rewriting
the tests to real unit tests and better mocking.

Change-Id: If43b1867d538a330189e0fc8b8041a1192c075a2
Resolves: #52726
Releases: 6.2
Reviewed-on: https://review.typo3.org/24694
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Parts of the sys_file table are internal cache data
for the FAL Api to work. Other parts are a meta-data
storage for the FAL frontend output.
On the one hand this mixes up several concerns, on
the other hand this makes it difficult to translate
and version metadata since this would result in
duplicate FAL index entries.

As a result those two concerns are split in separate
tables. The user does not "see" the sys_file table
anymore. Metadata is edited only in sys_file_metadata.

Change-Id: Ia6e3664ad5602affcba4e02cf415aa39436d4352
Resolves: #52726
Releases: 6.2
Reviewed-on: https://review.typo3.org/24503
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny
Reviewed-by: Frans Saris
Tested-by: Frans Saris
Reviewed-by: Fabien Udriot
Tested-by: Fabien Udriot
Reviewed-by: Steffen Ritter
Tested-by: Steffen Ritter

When building the column maps inside DataMapFactory
the column configurations "type" and "internal_type"
are not considered at all. This is necessary for
several follow up patches improving the handling
of e.g. mm_match_fields.

Releases: 6.2
Resolves: #52723
Change-Id: Id7bc9a8ae9d46a01c1f5fef92f7e7ec5a1e3eb60
Reviewed-on: https://review.typo3.org/24627
Reviewed-by: Sascha Egerer
Tested-by: Sascha Egerer
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

* Fixed major bug in Enumeration->equals method by
  changing object comparison to loose comparison
* Optimized Enumeration at some places
* Do not throw generic exceptions but specific exceptions
* Add Unit tests
* Move "cast" function from VersionState to Enumeration

Resolves: #52551
Releases: 6.2
Change-Id: Ief64bc08e474c38036d34ed3791c13e39661e9b3
Reviewed-on: https://review.typo3.org/24634
Reviewed-by: Sebastian Fischer
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

The backend produces thumbnails/file icons/truetype font previews which
come from a database row. The usability for these images can be improved
by showing the file name or title on hover using the title attribute.
Currently only the thumbnail/icon is produced and more information can
only be read by clicking the icon or opening the record, like in the
content element File Links.

This patch changes the alt attribute to the alternative text and adds the
title attribute for these images. When no title has been given for a file
record, the file name will be used instead.

Change-Id: I23b761fb204dda2c200f3ea57961cc017840fcac
Fixes: #47709
Releases: 6.2
Reviewed-on: https://review.typo3.org/20456
Reviewed-by: Alexander Opitz
Tested-by: Alexander Opitz
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind

In order to enable the Package Management API, the used Flow classes
have been placed in the core. The last synced state and the made
changes to the source are noted in a README file.

Resolves: #52737
Related: #47018
Releases: 6.2
Change-Id: Ic8fda623d9ff81f52c3c104a0d5ae7c290bf7953
Reviewed-on: https://review.typo3.org/24666
Reviewed-by: Alexander Opitz
Tested-by: Alexander Opitz
Reviewed-by: Sascha Egerer
Tested-by: Sascha Egerer
Reviewed-by: Thomas Maroschik
Tested-by: Thomas Maroschik

Change-Id: Iaf88fc46903400d97f6f1dc3acedb3c9b438e8dd
Releases: 6.2
Resolves: #52740
Related: #47018
Reviewed-on: https://review.typo3.org/24667
Reviewed-by: Thomas Maroschik
Tested-by: Thomas Maroschik
Reviewed-by: Alexander Opitz
Tested-by: Alexander Opitz
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Using "expects" on $mockDataMapFactory may fail with
several methods like "setOneToOneRelation" as these methods
return a ColumnMap object but the mock doesn't.

This patch adds the missing "->will($this->return())"
for these methods.

Releases: 6.2
Resolves: #52724
Change-Id: Ic91a7c51b1451c039e20b8ac310fdb25b02e1d84
Reviewed-on: https://review.typo3.org/24628
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Follow-up to "Allow to disable the "Core Updater" through an env-variable".
Now it's not even possible to call the individual Ajax requests that do the
update if it is disabled.

Resolves: #52639
Releases: 6.2
Change-Id: Icfa18d619bbb8aabf1896920f28fe5a63bd5c345
Reviewed-on: https://review.typo3.org/24661
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

By setting the environment variable "TYPO3_DISABLE_CORE_UPDATER=1" the
Core Updater functionality is disabled in the Install Tool. This can
be useful for providers which have it's own means of upgrading the
Core.

Resolves: #52639
Releases: 6.2
Change-Id: I88272ea613d95512ad780cefa5e261cf2dc6a60c
Reviewed-on: https://review.typo3.org/24629
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

Autoloader can be used in almost all cases.

Change-Id: I853e85758f6b39a6cb0798891ca0bea40ad6915c
Resolves: #52357
Releases: 6.2
Reviewed-on: https://review.typo3.org/24131
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

This patch corrects the calculation of the maximum value for a group
of checkboxes which is stored as bit flag value in the database. The
formular for the maximum value is 2nd power of the item count minus one.

Resolves: #52104
Releases: 6.2, 6.1, 6.0, 4.7, 4.5
Change-Id: I0eb430b72a072838c6ac3bc3f5e339ff2509c455
Reviewed-on: https://review.typo3.org/24650
Reviewed-by: Thorsten Kahler
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Currently the t3ver_state field can have 6
different integer values.
To clean up the code and make it better
understandable a Enum object is implemented.

Resolves: #52551
Releases: 6.2
Change-Id: I2f41d6bbf6575aec4a5c2b6d86495700d61bf5b7
Reviewed-on: https://review.typo3.org/24410
Reviewed-by: Sebastian Fischer
Tested-by: Sebastian Fischer
Reviewed-by: Thorsten Kahler
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

EXT:documentation checks for Index.html, index.html and index.htm as
main files for additional html documentations.

Change-Id: Idd2970ef9d6cc1b6f436b0c0fe0c607cf7b9d903
Resolves: #52569
Releases: 6.2
Reviewed-on: https://review.typo3.org/24441
Reviewed-by: Xavier Perseguers
Tested-by: Xavier Perseguers
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Workspaces are defined by having owners, members and default
notification recipients. These recipients, of course, need to be
a sub-set out of the owners/members crowd. Besides that, changing
the stage to "ready to publish execute" only considers owners and
falling back to "editing" stage only considers editors.

This feature request aims to allow editors/users to define whom
to notify, out of the owners/members crowd without limiting
these possibilities on the system level.

Resolves: #50224
Releases: 6.2
Change-Id: I39ded2ed02772040d498d5293d24c8bd6fb9ef46
Reviewed-on: https://review.typo3.org/22447
Reviewed-by: Wouter Wolters
Tested-by: Wouter Wolters
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

Implement a enumeration type without a
relation to 3rd party php modules.

Resolves: #52707
Releases: 6.2
Change-Id: Ie1138cf343a029132357640401f3a501fc0a3290
Reviewed-on: https://review.typo3.org/24598
Reviewed-by: Sebastian Fischer
Tested-by: Sebastian Fischer
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Currently the addQueryString option in the uriBuilder only supports
arguments which are in the query string. Therefore, the pagination
widget does not work with filtering post requests.

Solution: Add addQueryStringMethod (already supported by typolink
configuration) as property of uriBuilder and as argument of the
following fluid view helpers:
* link.action
* link.page
* uri.action
* uri.page
* widget.link
* widget.uri
* widget.pagination
Add addQueryStringMethod as configuration option of the paginate widget.

Fixes: #35281
Fixes: #11441
Releases: 6.2
Change-Id: I8f2963fa7467dffcf3b9535d2a41820de8f9930a
Reviewed-on: https://review.typo3.org/22432
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring
Reviewed-by: Stefano Cecere
Reviewed-by: Stefan Neufeind
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

This is a followup for the patch
I6ceeb8db4dd4e470e7c72dcfbc2121093411da75.

The latest change sets missed to adapt
the unit-tests accordingly.

Furthermore due to this change it came to light,
that the active loading option of storages in the file object
may create a recursion issue, if the file is not indexed.
This architectural problem has been removed by making
the constructor argument mandatory and extend the
ResourceFactory to always inject the correct storage.

Releases: 6.2
Resolves: #51528
Change-Id: Ic1561b83f49783e3af1b8f3403e1b8eab84a1380
Reviewed-on: https://review.typo3.org/24623
Reviewed-by: Frans Saris
Tested-by: Frans Saris
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Add the new field to the list of fields to be save during task
creation.

Resolves: #52696
Releases: 6.2
Change-Id: I4c281535a22318a6a742b25c6196a511bc620e24
Reviewed-on: https://review.typo3.org/24630
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe

Resolves: #52721
Releases: 6.2
Change-Id: Ife6338dd9f12ae21fce746f3707710ab7fa36464
Reviewed-on: https://review.typo3.org/24624
Reviewed-by: Markus Klein
Tested-by: Markus Klein

The newline below a scheduler-task-name is only needed
if a progress-bar and/or additional-information follow.

Change-Id: I8d92fc0d3b8d88fdbdfdc79d8ee501b74d821bcc
Resolves: #52715
Releases: 6.2, 6.1, 6.0
Reviewed-on: https://review.typo3.org/24612
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe

Adds a description-textfield for tasks. This will be displayed
in the scheduler-list. The description can either be shown as
hover (default) or below the job-name, configurable through
the extension-settings for "scheduler".

Change-Id: If0191da43677fc261cb73257e3ede848a5375d69
Resolves: #52696
Releases: 6.2
Reviewed-on: https://review.typo3.org/24610
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

With this change it will be possible to define multiple values
for the 'template', 'partial' and 'layout' root path configuration.
Each of the respective options will now have a corresponding setter
that enables configuration of multiple paths to look up when loading a
Fluid template file:
	$view->setTemplateRootPaths(array('first/path', 'second/path', …));
The old setters will be kept and they overrule the fallback paths. So:
	$view->setTemplateRootPath('some/path');
would disable the fallback paths of the previous example. The same is true
for 'setPartialRootPath()' and 'setLayoutRootPath()'.
The rootPath-getters have been deprecated in favor of
'getTemplateRootPaths()', 'getPartialRootPaths()' and
'getLayoutRootPaths()'.

This is a backport of the Flow feature applied in
Change-Id: I530e9a1fadbbd210c980c62cf2022c38fa81bb56 issue #39870

Resolves: #39868
Releases: 6.2
Change-Id: Id5a768ae834c53cd20fd59e762c2acf2ea9e6356
Reviewed-on: https://review.typo3.org/23950
Reviewed-by: Frans Saris
Tested-by: Frans Saris
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

The FileRepository, ResourceStorage and ResourceFactory all somehow
take care of creating files, managing files and their data.  Getting a
file from ResourceStorage->getFile never involves the index-Records and
even if index records exists the driver always needs to query all file
information out of the filesystem to create FileObject.

As we always expect the index-record to be up to date we can rely on
that and must not query the file-system for every bit of information.
In addition creating objects without looking for the record first
renders the FAL API useless. This patch introduces a
FileIndexRepository which only deals with these kind of records and
deprecates the methods within the FileRepository.

In addition it moves around the "file-object creation logic" so this is
dealt with at a central place: The Resource Factory. Finally the
ResourceFactory always uses to get an IndexRecord from the newly
introduced Repository. If the FileInfo is not present, it queries the
Storage for the fileInfo (from the Driver).

Releases: 6.2
Resolves: #51528
Change-Id: I6ceeb8db4dd4e470e7c72dcfbc2121093411da75
Reviewed-on: https://review.typo3.org/23839
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny
Reviewed-by: Frans Saris
Tested-by: Frans Saris
Reviewed-by: Markus Klein
Tested-by: Markus Klein
Reviewed-by: Steffen Ritter
Tested-by: Steffen Ritter

Currently the method just splits the given class name
by backslashes to detect the proper vendor name. If using
a leading backslash the algorithm of this function causes
a wrong result. Therefore all leading backslashes must be
removed first.

Releases: 6.2, 6.1, 6.0
Fixes: #52708
Change-Id: Icdc46facf66260bf528994964fb713d3dd24b3c6
Reviewed-on: https://review.typo3.org/24596
Reviewed-by: Xavier Perseguers
Tested-by: Xavier Perseguers
Reviewed-by: Stefan Froemken
Tested-by: Stefan Froemken
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

When changing to another workspaces the currently selected page is not
always available.
This change selects the next available page from the rootline for page
tree and submodules of web module when the current page does not exist
in the workspace.

Change-Id: I0502fea3c21515421586403a41f5c696ffc0d762
Fixes: #37611
Releases: 6.2, 6.1, 6.0, 4.7, 4.5
Reviewed-on: https://review.typo3.org/21110
Reviewed-by: Sascha Egerer
Tested-by: Sascha Egerer
Reviewed-by: Timo Webler
Tested-by: Timo Webler
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

DataHandler::clear_cache() is called with a table and an uid that
has been modified to trigger the clear cache commands. To find
siblings, children, parents, etc. the pid value is directly used
to find the affected pages. However, in a workspace context, the
pid is always "-1" which leads to a selection of all page
records of all workspaces. This amount is used to flush all
defined caches by a given tag name and might result in execution
time outs.

To avoid these superfluous cache flushes, page ids lower than 0
are ignored now in this section.

Fixes: #51051
Releases: 6.0, 6.1, 6.2
Change-Id: I03987bbd8c5d3526fb4dfda75b0dd0316fe1d836
Reviewed-on: https://review.typo3.org/23078
Reviewed-by: Sascha Egerer
Tested-by: Sascha Egerer
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring
Reviewed-by: Oliver Hader
Tested-by: Oliver Hader

When a deletion of a page is published, all moved records
have to be copied to their new location before they get deleted.

Resolves: #52636
Releases: 6.2, 6.1, 6.0
Change-Id: Ide471b4f25c0350a1df57af3d92283310a76cac9
Reviewed-on: https://review.typo3.org/24513
Reviewed-by: Sascha Egerer
Tested-by: Sascha Egerer
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

The field content that is used for the workspace placeholder records
is not processed through the field configuration.

This produces annoying error messages to the user.

Resolves: #17551
Releases: 6.2, 6.1, 6.0

Change-Id: I79823cc2bd0d26a03b0850045c08999ebdbc1a9b
Reviewed-on: https://review.typo3.org/22940
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

Call workspace overlay to resolve the right uid for
move-placeholder.

Change-Id: I6af65fcda1b1fffe72dfbc314976e42f30120d71
Fixes: #36573
Releases: 6.2, 6.1, 6.0, 4.7, 4.5
Reviewed-on: https://review.typo3.org/10759
Reviewed-by: Sascha Egerer
Tested-by: Sascha Egerer
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

The migrate workspaces update wizard task tries to upgrade non
existing tables. Check if table exists before executing the query.

Change-Id: I57855c079a8485537888345b61c9b3f0a17ca492
Resolves: #34246
Releases: 6.2
Reviewed-on: https://review.typo3.org/23796
Reviewed-by: Sascha Egerer
Tested-by: Sascha Egerer
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

In workspace preview the query condition for pages records has to be
enhanced to restrict to live WS and current WS.

Change-Id: Ib271b9bb435b50f2777621707728a74ba5de4187
Fixes: #37209
Releases: 6.2, 6.1, 6.0
Reviewed-on: https://review.typo3.org/11252
Reviewed-by: Sascha Egerer
Tested-by: Sascha Egerer
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

The cache-frontend is VariableFrontendCache that already uses
serialize() or (if available) igbinary_serialie() itself.
No need to additionally serialize data.

Change-Id: I8c3cfd2a279f8a38bc5c4d860329f2333f1304a5
Resolves: #52648
Releases: 6.2
Reviewed-on: https://review.typo3.org/24512
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe
Reviewed-by: Stefan Neufeind
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

The origin is in DatabaseRecordList::makeControl() that
tries to create a preview link with the page id "243#33163"
- more strict checks will deny this request because it's not
the expected integer value. Thus, BackendUtility::viewOnClick()
is called with a string instead of an integer.
This happens in the regular list module in the TYPO3 backend.
It's not critical if hooks and further processors use intval() on the
argument, but is bad if methods expect the defined integer value.

Change-Id: Ib66c1ee219b67e51d534f11fbf1eaa330476ca93
Fixes: #50912
Releases: 4.5, 6.0, 6.1, 6.2
Reviewed-on: https://review.typo3.org/22951
Reviewed-by: Sascha Egerer
Tested-by: Sascha Egerer
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

If any RedirectLoopException is raised there should be a mention that
for any restart the redirectCount parameter has to be removed or the
install tool has to be restarted from backend.

Resolves: #52703
Releases: 6.2
Change-Id: I766a036db261376e978d1ff51bb2c69ee34fff82
Reviewed-on: https://review.typo3.org/24565
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

If you edit a record in a workspace and then you try to
delete the record, the record it not deleted but the
version (workspace-change record) is.

Resolves: #52530
Releases: 6.2, 6.1, 6.0
Change-Id: I6a77f9a398276af98c41d841053641f3e07b2e33
Reviewed-on: https://review.typo3.org/24366
Reviewed-by: Thorsten Kahler
Tested-by: Thorsten Kahler
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

If a storage needs information about a file, it always has
to retrieve all information about the file from the driver.
This can be very expensive - especially if only the modification
timestamp would be relevant, but sha1 content hash as well
as creation time, access time, size, mimetype ... are detected.
This patch extends the interface with a possibility to only
retrieve a subset of these information. As drivers are only
accessible through an ResourceStorage and the new parameters
are optional this patch does not change behaviour or break
backwards compatiblity.

Releases: 6.2
Resolves: #51515
Change-Id: I45dec41e3f6cfa2d6c8902b795dc224c729296f8
Reviewed-on: https://review.typo3.org/23464
Tested-by: Oliver Hader
Reviewed-by: Oliver Hader

Currently there is no way for controlling the visibility
of a module in the BE. The patch introduces User TSconfig
which can be used to hide modules from the main menu.

options.hideModules = file, help

options.hideModules.web := addToList(func,info)

options.hideModules.system = BelogLog

The change only influences the visibility of modules in the menu
and does not control the access (permission) which still must be
done in the ACL of a BE User / Group as usually.

Change-Id: I6c2ec2c389a154440932afa16f9ca3a2cb4b8116
Releases: 6.2
Resolves: #52482
Documentation: #52692
Reviewed-on: https://review.typo3.org/24274
Reviewed-by: Steffen Müller
Tested-by: Steffen Müller
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Anja Leichsenring
Tested-by: Anja Leichsenring

The following condition is available in TypoScript and TSconfig
for testing the ApplicationContext:

[applicationContext = value1, value2, ...]

One of the given values matching the applicationContext.
Wildcards + and * are allowed, as well as regular expressions
delimited with /PREG_PATTERN/

Examples:

[applicationContext = Development/Debugging, Development/Profiling]
  # matching exactly "Development/Debugging" or "Development/Profiling"
[global]

[applicationContext = Production*]
  # matching any applicationContext with a rootContext of "Production",
  # for example "Production/Live" or "Production/Staging"
[global]

[applicationContext = /^Production\/Staging\/Server\d+$/]
  # matching "Production/Staging/Server1", "Production/Staging/Server2"
  # and so on
[global]

Resolves: #50132
Documentation: #52701
Releases: 6.2
Change-Id: I4f0f69ca4208d36d8eb8966ec9ef034f6b703b34
Reviewed-on: https://review.typo3.org/22412
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn
Reviewed-by: Markus Klein
Tested-by: Markus Klein