Important: #110684 - File storage select fields no longer reference sys_file_storage
See forge#110684
Description
The TCA columns
sys_ and
tx_ are
type => 'select'
fields that
resolved their items through
foreign_. Both now receive their items from
the new items processor function
\TYPO3\,
which lists the storages the current backend user has access to via
Backend. As before, non-admin users
only see the storages they have a file mount in, and admin users see all
storages.
The database columns are declared explicitly in ext_tables.sql as
unsigned integers and keep their previous definition. As both fields no longer
define a relation, the schema API reports them as
\TYPO3\ instead of
\TYPO3\, and the Record API
returns the storage uid instead of a resolved storage record.
This has the following side effects:
- The reference index no longer records a relation from
sys_andfile tx_records to their storage record. Existing relations are removed by updating the reference index, for example withscheduler_ task vendor/. Afterwards, the reference count and the delete warning of abin/ typo3 referenceindex: update sys_record no longer include files and scheduler tasks.file_ storage - Labels of both fields, for example in the record history, are resolved through the items processor function. For storages the current backend user has no access to, and without a backend user, the storage uid is shown instead of the storage name.
cleanup:now removes the processed file records of local storages and of the fallback storage only. Records of remote storages were previously included by accident, and installations with several local storages no longer see duplicate deletion attempts.localprocessedfiles -- all
The read-only file mounts resolved from the user TSconfig option
options. use the new
internal method
Storage instead of a
direct database query. If no storage exists apart from deleted ones, the default
local storage is created, as for any other storage lookup, instead of an
exception being thrown.
Extensions with own select fields that use
foreign_ keep working, including the storage
based item restriction for non-admin users. Extensions that override the TCA of
the two core fields, for example by adding a
foreign_ clause,
have to adapt, as those options no longer have an effect on an items processor
function.