- Sep 13, 2024
-
-
Torben Hansen authored
Extbase controller argument mapping can result in several exceptions being thrown. Extension authors however have no public API method for handling those exceptions, resulting in possibly overwriting internal methods of `ActionController`. This change introduces the method `handleArgumentMappingExceptions` in `ActionController` and the configuration options: * `mvc.showPageNotFoundIfTargetNotFoundException` * `mvc.showPageNotFoundIfRequiredArgumentIsMissingException` Extension authors can now either configure handling of commonly thrown exceptions during argument mapping, or implement a custom exception response handling. Resolves: #104321 Releases: main Change-Id: I351e5cfee5f80995aae5c95722b21218dffb9886 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85138 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Simon Schaufelberger <simonschaufi+typo3@gmail.com> Reviewed-by:
Mathias Brodala <mbrodala@pagemachine.de> Tested-by:
Garvin Hicking <gh@faktor-e.de> Reviewed-by:
core-ci <typo3@b13.com>
-
Benjamin Franzke authored
Apply an additional form token (send via POST) for the site settings save action, additionally to the get-based route token. Releases: main Resolves: #104951 Change-Id: I33beefbf15172274a593b0889583eaa7008ef874 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86081 Tested-by:
Benjamin Franzke <ben@bnf.dev> Reviewed-by:
Andreas Kienast <a.fernandez@scripting-base.de> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
Benjamin Franzke authored
Drop the `$force` parameter, which is intended to create a fresh (ignoring existing cache) instance everytime. This parameter was probably forgotten during development. Resolves: #104946 Related: #104521 Releases: main Change-Id: I11d0e75ea69f741e8a466ae08231d72d123f81c3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86075 Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
-
- Sep 12, 2024
-
-
Benjamin Franzke authored
Implement ContainerInterface in order for fluid[1] to be able to access settings properties directly, instead of using `{settings.all.property}`, e.g. when accessing site settings directly via `{site.settings.mysite.brandColor}`. [1] https://github.com/TYPO3/Fluid/issues/1001 (raised in #104896) Releases: main Related: #104858 Related: #104896 Resolves: #104906 Change-Id: Ia6cd703dfc2faca5f6324174ee343610cc32a6b3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86013 Reviewed-by:Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
-
Benjamin Franzke authored
Site settings rely on the Settings base class __set_state() method to recreate the object from cache. Since the base class used `new self` instead of `new static`, the object received an invalid type and was therefore ignored. Use `new static` to ensure the correct constructor is invoked. Resolves: #104945 Related: #104858 Releases: main Change-Id: I09eee1043902b5e62243258a080a64f026a6783e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86074 Tested-by:
-
Oliver Bartsch authored
Prevent UndefinedSchemaException for records, which contain a no longer valid record type. Resolves: #104943 Related: #104938 Releases: main Change-Id: Ife408dd2ab7b2361583c77bb4f622548495bf9ca Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86072 Tested-by:
-
Andreas Kienast authored
Resolves: #104939 Related: #104913 Releases: main Change-Id: Ie3486041db6ffe31c10da32c5e281cbb6b2d0017 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86048 Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
-
Oliver Bartsch authored
A new generic way of defining record preview template paths is introduced. Corresponding TSconfig syntax: `record.preview.<table_name>.paths` Using this option to define template paths, the templates for the record previews as well as related layouts and partials are auto-discovered. Those templates receive the fully transformed record object. The functionality is first used for content element previews in the page module but will be used in other areas of the backend in the future. Therefore, the corresponding service has been renamed to `FluidBasedRecordPreviewRenderer`, while the event listener method for the content preview got the speaking name `renderPageContentPreview`. Resolves: #104938 Releases: main Change-Id: I15f136c50a4161366afd18f59a2188ec17750c38 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86032 Tested-by:Jochen Roth <rothjochen@gmail.com> Tested-by:
Benni Mack <benni@typo3.org>...>
-
Andreas Kienast authored
To make managing content across pages easier, a backend user may now drag content elements from the "Page" module into a page in the page tree. Once dropped, a modal window will open where the backend user may select the position where the content element shall be placed to, and also change the target page again. Resolves: #104935 Releases: main Change-Id: Id4de849d02e36478af1c6fa780c2e4d495d6b41e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86018 Tested-by:
Andreas Nedbal <andy@pixelde.su> Tested-by:
-
Mathias Brodala authored
The templates can be replaced by integrators via configuration. They probably expect to be able to use the EditRecordViewHelper. This one uses the current request for its returnUrl. The request was missing which would lead to an "Call to a member function getAttribute() on null" error. Resolves: #99287 Releases: main, 12.4 Change-Id: I6a696bf176051b7c5eb4c1b762b10ebc33e7a4b1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76939 Reviewed-by:
-
Benni Mack authored
This change prepares some code areas within the Fluid-based page module to be re-used at a later point, especially within the PagePositionMap. This is a pre-patch to make life easier. Resolves: #104934 Releases: main Change-Id: I2296db0e5d4ab4ef9b150a20e02964b0c2fc4af4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86044 Tested-by:
-
Oliver Bartsch authored
In case a sub schema, e.g. `tt_content.list` makes use of the "subtypes" feature by defining the "subtype_value_field", corresponding configuration ("subtypes_addlist" and "subtypes_excludelist") is now evaluated in the TCA schema and added as further schema (third level) to the corresponding sub schema (second level). This will therefore look like the following: Schema "tt_content" -> Sub Schema "list" -> Subtype Schema "tx_blog_pi1" Via the "subtypes" feature it's only possible to add or remove existing fields from the corresponding sub schema. Also note that the subtype schemata can only be accessed using the getSubSchema() and getSubSchemata() methods on a sub schema. This means calling `$schemaFactory->getSchema('tt_content.list.tx_blog_pi1')` does not work intentionally! Resolves: #104929 Releases: main Change-Id: I10428e1129d5d23acce91cd7756f4f255a45c29b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86043 Tested-by:Frank Nägler <frank.naegler@typo3.com> Reviewed-by:
-
Benjamin Kott authored
Corrects z-index to not hide module menu and other important actions behind the modal backdrop on mobile Resolves: #104933 Releases: main Change-Id: I3d6fe35f811a01ee674adae1a1acf7c79d6edf34 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86045 Tested-by:
Benjamin Kott <benjamin.kott@outlook.com> Reviewed-by:
-
Benjamin Kott authored
Resolves: #104930 Releases: main Change-Id: Ib481c76706e2544688ff8137ba4584aed67ddf46 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86042 Tested-by:
-
Benjamin Kott authored
We are dropping the Bootstrap CSS definitions for all list-group to have more control about the styling of the list-group elements. From now on we are shipping custom css adapted to our needs. The new list-group element styling is context aware and adapts to light and dark color schemes. Resolves: #104927 Releases: main Change-Id: I9212f0e668a00591f1351b1a56daec99eadc420b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86041 Tested-by:
-
Stefan Bürk authored
The frontend implementation of `EXT:adminpanel` has been revamped in TYPO3 v9 with #84584, #84044 and #84892 including the refactor of AJAX request using backend ajax routing. This makes the `eID` handler implementation obsolete for quite a long time now but has not been removed meanwhile. This change removes the `eID` handler mapping towards the ajax controller without further notice as they are not called anyway. [1] https://review.typo3.org/c/Packages/TYPO3.CMS/+/56826 Resolves: #104924 Related: #84892 Related: #84044 Related: #84584 Releases: main Change-Id: I49ae7721adc9937bcca0d0b774aefd07c446ad35 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86039 Tested-by:
-
Garvin Hicking authored
The Extension Scanner of the EXT:install module allows to scan custom extensions based on several static code analysis rules. Most of these rules depend on analyzing code to see if deprecated or removed methods are called, or if argument names change, annotations/attributes get removed and so on. This patch adds a `AbstractMethodImplementationMatcher` matcher which can analyze definitions of specific methods within an extended abstract class that need to be migrated. A good example for this is the change in Fluid ViewHelpers deprecating the "renderStatic" method, which could previously not be matched. Because ViewHelpers themself do not execute a `renderStatic` method, any custom ViewHelper implementing `renderStatic` would not be revealed in the Extension Scanner before. The Matcher receives a configuration like: ``` return [ 'TYPO3Fluid\Fluid\Core\ViewHelper\AbstractViewHelper::renderStatic' => [ 'restFiles' => [ 'Deprecation-104789-RenderStaticForFluidViewHelpers.rst', ], ], ]; ``` and based on this, iterates every custom code to check if any class inherits from this `TYPO3Fluid\Fluid\Core\ViewHelper\AbstractViewHelper` abstract, and then checks for a given method name (here `renderStatic`). Both static (`::`) and "local" ( `->`) methods can be configured for matching. These matches will be reported as strong matches. Resolves: #104799 Related: #104789 Releases: main Change-Id: I9021ecc021a45770e2e4c8b0295f4d1afe55adfd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85853 Tested-by:Simon Praetorius <simon@praetorius.me> Reviewed-by:
-
Frank Naegler authored
The method \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPItoST43() has been marked as deprecated and will be removed with TYPO3 v14. Resolves: #102821 Releases: main Change-Id: Iab5c665e9ec8c0aef0c21affac7bb2b5f40a5d88 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83320 Tested-by:
Torben Hansen <derhansen@gmail.com> Reviewed-by:
-
Simon Praetorius authored
A new option `external` is added to the `AssetCollector` API, which prompts `AssetRenderer` to skip any processing of the supplied asset URI. Resolves: #102255 Releases: main Change-Id: I6016f814af0b0ef92a172eb0538fe949affce6cc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86035 Reviewed-by:
-
Andreas Kienast authored
The wizard to move or copy a content element into another page is now moved into a modal window. This is a preparation patch to allow dragging content elements from the page module. Resolves: #104915 Releases: main Change-Id: I4e69bbcc2f43ea889491a1383648dbc17a233812 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86023 Tested-by:
-
Sybille Peters authored
The following fields have been added to the default configuration: * `pages.canonical_link` * `sys_redirect.target` * `sys_file_reference.link` Other non-working fields (`pages.media`, `tt_content.records`) are kept for forward-compatibility. Resolves: #83835 Related: #103478 Related: #103477 Releases: main Change-Id: Ic598a2a78bb9c103def9a692370f118ee2fa11b3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83612 Tested-by:
-
Andreas Kienast authored
To avoid flickering in the TYPO3 backend, the body and iframe elements are now styled to have a background color matching the selected color scheme. Resolves: #104917 Releases: main Change-Id: Ib5c7ee67e29912f35aa97fb4ef3718b9cee32bee Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86025 Tested-by:
-
Stefan Bürk authored
This change renames a changelog file to get rid of a bad-ass trailing space character in the filename. Resolves: #104922 Related: #104868 Releases: main Change-Id: I4e2b330e94ee74451d59979195b05e2701da51a0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86037 Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Tested-by:
Ayke Halder <mail@ayke-halder.de> Tested-by:
-
- Sep 11, 2024
-
-
Oliver Bartsch authored
The new PSR-14 RecordCreationEvent is introduced in order to allow the manipulation of any property before being used to create a Record object. The event is even capable of creating the Record object on its own. Using the event, extension authors can apply custom transformations for fields, e.g. creating custom objects for field values. The properties to operate on are either already transformed or the raw values, in case no transformation matched the field type. Resolves: #104846 Releases: main Change-Id: I83c95ae218a7148aa0a2768a7cb58c00b41681a0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85913 Tested-by:
-
Frank Naegler authored
If no configurable Site exists, show a message to the user that explains why nothing exists. Resolves: #104913 Releases: main Change-Id: I6e1c39a19d79c82a1552b3d35610b89d6f1b7ba1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86021 Reviewed-by:
-
Andreas Nedbal authored
This patch adds the ability to switch the active color scheme using multiple different methods in the Backend User Interface. The two main methods are a selection of buttons in the user dropdown at the top right of the Backend, the other one being a setting present in User Settings. Additionally, if the "auto" setting (default) is selected, the backend is automatically using the systems preferred color scheme. Considering the dark color scheme is still regarded as experimental, the switching capabilities are currently disabled using a UserTS setting 'setup.fields.colorScheme.disabled'. Resolves: #104868 Releases: main Change-Id: I6704fba0930ac579582f1d21dd11368b3509328a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85935 Reviewed-by:
-
Simon Praetorius authored
This patch enables a template processor included in Fluid 4 for all Fluid instances in the Core. The template processor strips `<f:comment>` tags from Fluid template strings before the parsing starts. This prevents Fluid errors when invalid Fluid code is used inside `<f:comment>`. Original change in Fluid: https://github.com/TYPO3/Fluid/commit/faad81a9f5d991d688e1d4c673e0d7aaf41a7e94 Resolves: #104904 Releases: main Change-Id: Ieebb60ee21ae9f8d6f168e75b9fd22a7103a5f6a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86012 Reviewed-by:
-
Benjamin Kott authored
We are dropping the Bootstrap CSS definitions for all modals to have more control about the styling of the modal elements. From now on we are shipping custom css adapted to our needs. The new modal element styling is context aware and adapts to light and dark color schemes. Resolves: #104911 Releases: main Change-Id: I98d619c407708f6d5c969cb98fc304786e4c0c44 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86015 Reviewed-by:
-
Stefan Froemken authored
Add missing "App" node to example in Changelog of notification actions. Resolves: #104903 Releases: main, 12.4, 11.5 Change-Id: Icc88a55c731c7f5b517740673c24acd21b83fa12 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86010 Reviewed-by:
-
Oliver Bartsch authored
The RecordInterface is extended to require implementations to implement the `getRawRecord()` and `getSystemProperties()` methods as well as the PSR-11 `ContainerInterface`. This allows to change RecordFactory's `createRecord()` method to return the interface instead of the `Record` object. This will come in handy e.g. for the already existing `Page` object, which can now be used without extending `Record`. By using the `ContainerInterface` we allow access to the record and its properties via the has() and get() methods, which is supported since Fluid 4.0: https://github.com/TYPO3/Fluid/issues/1001. Resolves: #104859 Releases: main Change-Id: Ib8d20dc4eea343bf1c2160dbab6d4301930792ee Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85925 Reviewed-by:
-
Jochen Roth authored
Previously, it was possible to allow editors to modify colPos and CType in FormEngine via connected CEs. This has been changed when editing translated CEs, that CType and colPos cannot be changed anymore. An upgrade wizard is added to ensure that all translated CEs really contain the same colPos and CType values as their default language pendants. Both fields are now set to l10n_mode=exclude to avoid future inconsistencies. Resolves: #60357 Releases: main Change-Id: Id04636d8c131ce8fbc7c9a87d5fc13a6b406eec2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85978 Tested-by:
André Buchmann <andy.schliesser@gmail.com> Tested-by:
-
Simon Praetorius authored
This patch raises the minimum Fluid dependency to the just released Fluid 4. The Fluid team has taken great care to plan this switch in the Core by introducing a lot of changes in advance, both with minor releases of Fluid 2 and code changes in the Core to avoid now deprecated Fluid features. There are no new deprecations with this release. All deprecations have already been announced and documented in previous raises of Fluid 2.x in the Core. One recently added test case needs to be adjusted with this change to account for the feature described in the attached feature RST file. For a full changelog and more information about the release, dedicated release notes are available on GitHub: https://github.com/TYPO3/Fluid/releases/tag/4.0.0 Executed commands: ``` composer req typo3fluid/fluid:^4.0 composer req -d typo3/sysext/adminpanel --no-update typo3fluid/fluid:^4.0 composer req -d typo3/sysext/core --no-update typo3fluid/fluid:^4.0 composer req -d typo3/sysext/fluid --no-update typo3fluid/fluid:^4.0 composer req -d typo3/sysext/redirects --no-update typo3fluid/fluid:^4.0 ``` Resolves: #104896 Releases: main Change-Id: Ia40b2a62ba43303bdc094f763e103465a0d5a03e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86008 Reviewed-by:
-
Benjamin Franzke authored
Site local settings (defined in the sites settings.yaml file) need to be taken into account in the site overview, only if they are based on definitions. Therefore the setting map (which is based on definitions) has to be evaluated instead of the flat settings map (which contains all settings, defined and legacy anonymous settings). Releases: main Resolves: #104886 Related: #104794 Change-Id: I49f8d01c3947302ff75a6aac0e3e64cdeca819c8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85998 Tested-by:
-
Oliver Bartsch authored
Resolves: #104891 Releases: main, 12.4 Change-Id: I7431cd142a1b92e7ca14dcfe1b5720f9a627be04 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86002 Reviewed-by:
-
Benjamin Kott authored
Resolves: #104893 Releases: main Change-Id: I9cbee0ca23f33d58ad99cabf3f7511fc4620b0d0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86003 Tested-by:
-
Benjamin Franzke authored
Resolves: #104892 Releases: main Change-Id: I55ad0f3da6807d2b8bd624a95613f3d612ddc788 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86004 Reviewed-by:
Lina Wolf <112@linawolf.de> Tested-by:
-
Michael Schams authored
This patch updates the English labels shown in the TYPO3 Dashboard and Dashboard widgets for System Notes. Resolves: #104888 Releases: main Change-Id: I4ecb3886d30459823529052ef084daf715715873 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86000 Reviewed-by:
-
- Sep 10, 2024
-
-
Benjamin Franzke authored
A new Site Settings editor has been introduced that allows to configure per-site settings in `config/sites/*/settings.yaml`. The new backend module `Site Management > Settings` provides an overview of sites which offer configurable settings and makes them editable based on Site Set provided Settings Definitions. The editor shows a list of settings categories and respective settings. It will persist all settings into `config/sites/*/settings.yaml`. The module will only persist settings that deviate from the site-scoped default value. That means it will only change the minimal difference to the settings set defined by the active sets for the respective site. The backend module is currently available for administrators only, but will likely be extended to be made available for editors in future. Anonymous (undefined) site settings – as supported since TYPO3 v10 – will not be made editable, but will be preserved as-is when persisting changes through the settings editor. Resolves: #104794 Releases: main Change-Id: I7eea8445b86b50efa498238daa3436f0940f4b78 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84342 Tested-by:
-
Nikita Hovratov authored
The label of palettes can be overridden in showitem. These labels are now also removed to correctly find and remove this system palettes. Resolves: #104836 Related: #104814 Releases: main Change-Id: I322ffd71fcc062ad07ff9b59f2f8dd32a381668f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85902 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
-
Benni Mack authored
Resolves: #104884 Related: #104844 Releases: main Change-Id: I6361b841eededc837702f9fbe61c236c7502abd0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/85994 Tested-by:
-
