This project is mirrored from https://git.typo3.org/typo3/typo3.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
- 10 Mar, 2021 1 commit
-
-
This patch provides the following changes in order to have better abstractions and encapsulate the dependencies of each implementation. 1. SelectTree (Category Tree) The TreeToolbar is now clearly coupled into the SelectTree and built as LitElement inside the SelectTreeElement. SelectTree now contains all relevant functionality regarding selecting multiple items, and shows settings (SelectTreeSettings) which were only used in SelectTree. This is especially relevant for the multiple item selection, and the exclusiveKey handling. 2. PageTree + FileStorageTree Obsolete public methods are removed, and visibility is changed. Filtering is now separated in favor of a non-public property. By using Types (in e.g. PageTreeDragDrop) the visibility is also adapted Obsolete wrapper methods are removed. Resolves: #93692 Releases: master Change-Id: Ifead098bb80e37d5c7ad5e1d0eabda14aa7087ce Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68303 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Richard Haeser <richard@richardhaeser.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 01 Mar, 2021 1 commit
-
-
The component is provided as replacement for the current lit-helper `icon()` which cannot provide support for icon usage inside shadow dom elements. The component renders all icons as inline SVGs. FontawesomeIconProvider is therefore adapted to provide inline rendered SVGs for font-awesome icons. Not that these inline font-awesome SVGs will also be used in areas where 'inline' icons are requested (like information toolbar) but the fallback to 'default' was used before. The component supports all properties of the Icon API via HTML attributes. Colors and custom sizes can be applied to the component via CSS color/font-size property: typo3-backend-icon[identifier=status-dialog-information] { color:#6daae0; /* An explicit font-size will be used as icon width & height */ font-size: 1.2em; } Resolves: #93473 Releases: master Change-Id: I3044c325f122eb0085ecb3f45fb9502bfb314d5d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67675 Tested-by:
Richard Haeser <richard@richardhaeser.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 22 Feb, 2021 1 commit
-
-
The changes done in #93453 introduced a CSS change that broke all regular collapsible panels as their carets don't rotate anymore. This bugfix reverts the CSS change and adopts the Flexform code to set the `collapsed` class on a more appropriate element. Resolves: #93537 Related: #93453 Releases: master Change-Id: Iff87fd49a7bf9d3b155674578be7cfd887ad1408 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67960 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 19 Feb, 2021 1 commit
-
-
A new API is introduced, providing multi-factor authentication for the Core. The API is furthermore directly used to add two MFA providers by default: * TOTP (time-based one-time passwords) * Recovery codes Even if the API is designed to allow MFA in both, backend and frontend, it is currently only implemented into the backend. Users can therefore configure their available MFA providers in a new backend module, accessible via their user settings. There are also some configuration options for administrators to e.g. define a recommended provider or to disallow available providers for specific users or user groups. Administration of the users' MFA providers is possible for administrators in the corresponding user records. New providers can be introduced by implementing the MfaProviderInterface and tagging the service with the `mfa.provider` tag. Note that the API is currently marked as internal since changes in upcoming patches are to be expected. Following dependencies are introduced: * bacon/bacon-qr-code "^2.0" * christian-riesen/base32 "^1.5" Possible features that could follow later-on: * MFA frontend integration * Webauthn core provider for FIDO2 and U2F. * Forcing users to set up MFA on login * Password-recovery with active MFA Resolves: #93526 Releases: master Change-Id: I4e902be624c80295c9c0c3286c90a6a680feeb5d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67548 Reviewed-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Benni Mack <benni@typo3.org>
-
- 15 Feb, 2021 1 commit
-
-
This patch refactors the client-side rendering of FlexForm sections. Now, there are two modules in place: - FlexFormSectionContainer This module handles the "outer" part of a section, e.g. to toggle all containers or to revalidate FormEngine if a container is removed. - FlexFormContainerContainer The FlexFormContainerContainer represents an individual container being a child of a section. In order to streamline the UI, the look & feel has been changed to be more similar to IRRE. Resolves: #93453 Releases: master Change-Id: Ica373a6dbed4b470725267eac221bf839b23ec0f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67589 Tested-by:
Richard Haeser <richard@richardhaeser.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 10 Feb, 2021 1 commit
-
-
This change splits up Drag+Drop handling in general for SVG-based trees into PageTree specific logic, and common usages. This makes Drag+Drop functionality usable in more places than just the PageTree In addition, all usages of jQuery are removed and proper types were added instead of using "any". Resolves: #93478 Releases: master Change-Id: Ibb17cdd718424760676899b7746cb0828e06fc7d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67682 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Richard Haeser <richard@richardhaeser.com>
-
- 09 Feb, 2021 1 commit
-
-
This change migrates all left-over components of * SvgTree * SelectTree (a.k.a. CategoryTree) * and PageTree to TypeScript adding types in various places to make the code less error-prone. Resolves: #87678 Resolves: #85400 Releases: master Change-Id: Ibb4024d365857c44018a7a201c1cf75baa48179a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67662 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
core-ci <typo3@b13.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 06 Feb, 2021 1 commit
-
-
Andreas Fernandez authored
This patch adds the TypeScript declaration for the sortablejs library. Since the imported module has a different naming, the PageRenderer needs both the new module name ("sortablejs") and the old name ("Sortable") as this would be a breaking change, otherwise. In the master patch, the old module name has been declared deprecated. Resolves: #93454 Releases: master, 10.4 Change-Id: Ia8cc7bb4fb57bc7d55aa3601d6ccd1bfe6e0b54d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67658 Tested-by:
core-ci <typo3@b13.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 04 Feb, 2021 2 commits
-
-
This change aims to reduce the overhead by using jQuery in favor of Vanilla JS in various Tree-related JS files in preparation for a TypeScript migration. * SvgTree.js * SelectTree.js * PageTree.js * PageTreeToolbar.ts * PageTreeElement.ts * TreeToolbar.ts Resolves: #93427 Releases: master Change-Id: I57fc8e66415ea4ab6eaf690d925fbf7670d74284 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67583 Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
Benni Mack authored
This change migrate the TreeToolbar (used in FormEngine Category Tree for example) to TypeScript, removing effectively one RequireJS call and replacing it with a native TypeScript component. Removing the rest of the jQuery will be part of a separate effort. Resolves: #93432 Releases: master Change-Id: I3df66cd1c28d096c0f32982347dbd37c58834e4d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67640 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 27 Jan, 2021 1 commit
-
-
When an IRRE field in FormEngine has maxitems set, and an item gets removed (thus, allowing an inline element to be added again), the buttons to create new elements are shown again. This fixes a regression introduced with #91595. Resolves: #93091 Resolves: #93238 Related: #91595 Releases: master, 10.4 Change-Id: If4c8152ab6e4fc1388fbfcf1af72fa2609f6df16 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67541 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Jörn Wagner <joern.wagner@explicatis.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Jörn Wagner <joern.wagner@explicatis.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 19 Jan, 2021 1 commit
-
-
The Permissions backend module and its JavaScript module now ditch jQuery in favor of native browser API and TYPO3 API. The JavaScript has been refactored a little bit; initially checking the permission checkboxes or writing back the calculcated permission value is now decoupled and executed in the Permission module only. To support for..of with NodeList collections, TypeScript now loads the internal "dom.iterable" library. Additionally, the interim solution to add `editform` to Document has been removed which made another change in LinkPopup necessary. Furthermore, a bug has been fixed, where the value of the first visible select element was used when saving any other select element with a completely different value. Resolves: #93301 Releases: master Change-Id: Iffede862a0eb36e805a5f127d7b19f32c899ce31 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67457 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 07 Jan, 2021 1 commit
-
-
Benjamin Franzke authored
SelectTreeElement makes use of $.param() without importing jquery via requireJS. Instead of adding the missing jquery import, we simply migrate to the native URLSearchParams, as it is available in all supported browsers. Furthermore we avoid decoding the datastructureidentifier json, as it is encoded to json server side. We do this, because URLSearchParams does not url encode nested objects. Resolves: #93200 Releases: master Change-Id: I0da98092da6e09d6576bbdb59112d738086be238 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67323 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
- 06 Jan, 2021 2 commits
-
-
The FormEngine field type `selectMutlipleSideBySide` is very special, as it's a combination of four input and select fields. With the refactoring done in #87324 an issue in the validation has been introduced which caused the validation of the wrong field which contains no validation rules. This patch uses the correct field to obtain the validation rules from, now. Another issue is that values of `selectCheckBox` never have been validated as the necessary validation rules were missing. The rules are now appended to the outermost div container. In the same run, minor styling and markup changes were necessary. Resolves: #93191 Related: #87324 Releases: master, 10.4 Change-Id: I7195213a768fa4814eb3ecd81953a500c77ede5d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67317 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Richard Haeser <richard@richardhaeser.com>
-
Andreas Fernandez authored
When sorting elements in an IRRE container, the sorting took grandchildren into account as well, which broke the sorting in the database. With this patch, a new data attribute is added to be able to identify direct ancestors and limit sorting to these records only. Resolves: #92804 Releases: master, 10.4 Change-Id: I09876c3a8be45b060c133d758807e4df25fee0d2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66933 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Richard Haeser <richard@richardhaeser.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 29 Dec, 2020 1 commit
-
-
Probably since ever, FormEngine validates the whole form when a field changed or an IRRE item got removed. This patch introduces the following changes: - only fields affected by the `change` event get validated - FormEngineValidation.validate() accepts an optional argument to define the container whose fields get validated. If omitted, the whole form is validated. Resolves: #93046 Releases: master, 10.4 Change-Id: I48d2f597c88815ebc0374bb02cf0aed6ac4086fe Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67094 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Richard Haeser <richard@richardhaeser.com>
-
- 21 Dec, 2020 1 commit
-
-
Bootstrap v5 – introduced in #92616 – was added with CCS from beta1 but JavaScript from alpha2. bootstrap.bundle.js was manually wrapped into a AMD closure, and because bootstrap 5.0.0-beta1 contains alot of changes regarding data tags, it couldn't be updated in the initial patch. Bootstrap is now bundled using rollup using the ES6 sources in order to allow for automatic updates through `grunt build`. popperjs – previously bundled into bootstrap distributed files – is now added as dependency. The bootstap ES6 sources, that we now use through rollup, do not bundle this external dependency (for good reasons). Dependency added with: yarn add @popperjs/core Further adaptions contained in this change to ensure beta1 compatibility: a) Carousel "item" to "carousel-item" class migration b) $.fn.modal(options) does no longer imply $.fn.modal('show') c) Fix panels, both JS and CSS (card-group can't be used here) d) All bootstrap data- tags are migrated to data-bs-. (see https://github.com/twbs/bootstrap/pull/31827) Migrated with # renderes a sed substition with the help of a nested sed from all the # data-bs attributes that where changed in the twbs/bootstrap commit git grep -l data- | xargs sed -i $( \ curl -s \ https://patch-diff.githubusercontent.com/raw/twbs/bootstrap/pull/31827.patch | \ sed 's/data-bs-[a-z-]*/\n&\n/g' | grep "data-bs-[a-z-]" | \ sort | uniq | \ sed 's/data-bs-\(.*\)\([^a-z-]\|$\)/ -e s\/data-\1\\\([^a-z-]\\\)\/data-bs-\1\\1\/g -e s\/data('"'"'\1'"'"')\/data('"'"'bs-\1'"'"')\/g/g' \ ) # Revert false positives from the above auto-replacement git checkout -- typo3/sysext/core/Documentation/Changelog/ \ typo3/sysext/backend/Classes/Form/Container/FlexFormContainerContainer.php \ Build/Sources/TypeScript/backend/Resources/Public/TypeScript/LiveSearch.ts \ Build/Sources/TypeScript/backend/Resources/Public/TypeScript/FormEngineFlexForm.ts \ Build/Sources/TypeScript/install/Resources/Public/TypeScript/Module/Settings/ExtensionConfiguration.ts \ Build/Sources/Sass/typo3/_element_panel.scss (cd Build && grunt build) Resolves: #93126 Resolves: #93123 Resolves: #93132 Related: #92616 Releases: master Change-Id: Ie194d0f87d2c60df7b9e8a6de4893cfaaea55356 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67215 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Martin Kutschker <mkutschker-typo3@yahoo.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Martin Kutschker <mkutschker-typo3@yahoo.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 20 Dec, 2020 1 commit
-
-
This changes removes the frontend framework Bootstrap 3, and adds Bootstrap 5 beta 1 (we expect Bootstrap 5 final by the time we release TYPO3 v11 LTS). Bootstrap v3 is not supported by the Bootstrap team any longer, so an update is critical for TYPO3 Core. Bootstrap v5 adds a few accessibility improvements as well as flexbox for rendering containers and grids throughout TYPO3 Backend. All JS components are not bound to jQuery anymore, and have been reworked. A lot of HTML/CSS changes happened, which we slowly migrate (and not in a huge change) to TYPO3's templates, in order to keep this change managable. A legacy CSS/SCSS file is added to keep some backwards-compatibility classes to ease the migration for extension developers who have built their own backend modules. Key features of Bootstrap 5: * "rem" instead of "px" is used by default * CSS variables are introduced * Improved bootstrap focus outline styling (buttons / inputs / links) * Simplified grid functionality * use new button color mixin to increase contrast: Primary, Success and Warning Button color is now dark instead of white EXT:styleguide was used as a basis for upgrading to keep compatibility as much as possible, but more changes will be coming in the next few minor releases. Resolves: #92616 Releases: master Change-Id: Iec989f39649b5460b055ec879199faf38e424f2b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66247 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 03 Dec, 2020 1 commit
-
-
With the introduction of a new datetime picker, the listener for the event `formengine.dp.change` was not attached properly which broke the validation of updated datetime field. The listener is now attached to the datetimer field properly. To avoid introducing jQuery again, the method `FormEngineValidation.markFieldAsChanged` became aware of non-jQuery objects. Resolves: #92913 Related: #91606 Releases: master Change-Id: I3727f362a7d685fdea9bcdf0f1d3b37eca12d424 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66966 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 20 Nov, 2020 1 commit
-
-
Also add aria-expanded and aria-controls arguments for screen readers Resolves: #92682 Releases: master, 10.4 Change-Id: I48d0edcbea4d185d11216048d7847ad3574d704d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66271 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Michael Telgkamp <michael.telgkamp@mindscreen.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Michael Telgkamp <michael.telgkamp@mindscreen.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 03 Nov, 2020 1 commit
-
-
Slug fields currently only support slug recreation if the given generator fields are directly visible in the backend. However, this makes it impossible to recreate slugs even if some postModifiers are defined who can take care of successful slug generation. This commit allows slug recreation if at least one postModifier is defined, even if the defined generator fields are not usable for slug generation. Therefore also EditDocumentController was adjusted to not automatically add slug fields to columnsOnly in case postModifiers are defined for this record. Resolves: #89187 Releases: master, 10.4 Change-Id: Ifd50ec106b5b302cea23d37e470eafae840c8993 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61716 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 31 Oct, 2020 1 commit
-
-
With splitting the FormEngine in smaller parts, a regression has been introduced in the behavior of selectMultipleSideBySide. This select type supports "exclusive values" which are mutually exclusively selectable. However, due to a typo in the fetched (non-existent) data attribute, the whole behavior was broken. This patch fixes the typo. Resolves: #92737 Related: #87324 Releases: master, 10.4 Change-Id: Ice5de95c49d81df94ee1a8257ecab3abfe7d21d7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66361 Reviewed-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
- 19 Oct, 2020 1 commit
-
-
Christian Kuhn authored
The 'Make textareas resizable' setting is quite ancient. The patch drops this option from the user settings and enables 'growing' text areas by default. To prevent text areas from growing indefinitely, the user setting 'max height' with a default of 500px is kept. Change-Id: I0497c6823b96b077c05d25a2e63ae58c079400b7 Resolves: #92582 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66162 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 16 Oct, 2020 1 commit
-
-
Andreas Fernandez authored
This patch replaces the bootstrap-datetimepicker with flatpickr which is pretty lightweight. Since this datetimepicker also has some sanity validation on board, much custom datetime parsing in FormEngine can and has been removed, including magic date manipulation by using addition or subtraction. The year format for momentjs has been changed from `YYYY` to `Y` as well to support years < 1000. Currently the datepicker is not able to select a date < 100. By manual selection, the picker jumps back to 1999 and not to 99 as expected. Resolves: #91606 Releases: master Change-Id: Id723c5200c797019f6de0ed5a4c15b2137a32995 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64833 Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <noreply@typo3.com> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 10 Oct, 2020 1 commit
-
-
This patch removes jQuery from a major part of FormEngine components, including elements, field wizards, enhancers and IRRE. Additionally, the argument `optionEl` of the method `FormEngine.setSelectOptionFromExternalSource()` accepts objects of type `HTMLOptionElement` which renders jQuery objects obsolete, which has been deprecated. Resolves: #91911 Releases: master Change-Id: I5b7d2f4c7b9b5993a5bbe8cec016aa74cabbbecd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65009 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Stefan Froemken <froemken@gmail.com> Tested-by:
Richard Haeser <richard@richardhaeser.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Stefan Froemken <froemken@gmail.com> Reviewed-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- 18 Sep, 2020 1 commit
-
-
The toggleContainerControls method of InlineControlContainer.ts now only toggles its immediate controls. Furthermore, the new record link control for creating inline records has gotten the required class to toggle its visibility, when reaching maxitems limit. Resolves: #91808 Releases: master, 10.4 Change-Id: Ic8988943c349c874b6d9b7427a42c224dca1ded1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65058 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 25 Aug, 2020 2 commits
-
-
Each node in an IRRE container now has a new `data-placeholder-record` attribute to be able to identify such node w/out accessing CSS classes used for styling purpose. Nodes where `data-placeholder-record` has a truthy value are localizable and are ignored now when the sorting is changed which solves an issue where such records would have been moved into a different language. In the same run the localization is fixed as it was tried to iterate an object, which doesn't work. Alternatively, the object values are fetched and iterated now. Resolves: #91942 Resolves: #91938 Releases: master, 10.4 Change-Id: Ic6622eb5d6950893f79d4ae9697d7eaa096d2ef9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65214 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
This patch ensures the correct context (previous child id) is set on appending a new inline child after an existing one. Resolves: #91912 Related: #91863 Releases: master, 10.4 Change-Id: Ie6159049d23059a5fce38637499217af5a0b25a9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65450 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- 08 Aug, 2020 1 commit
-
-
This changes the configuration of the TypeScript compiler to resolve modules in "node" style, which allows using TypeScript declaration files (*.d.ts) shipped with npm packages. Additionally the option "esModuleInterop" is enabled which allows us to use CommonJS modules in AMD modules without fiddling with incompatible exports. As a negative side-effect, all JavaScript have to get recompiled to reflect these changes. Resolves: #91954 Releases: master, 10.4 Change-Id: If6386f5062bfbe439615bb947e94cd728dfd5b2b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65225 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- 27 Jul, 2020 1 commit
-
-
This patch adds the current selected value in the parents selectbox if no uid is set in its data attributes. This ensures that the value is removed from the option list on adding the inline element. Resolves: #91863 Releases: master, 10.4 Change-Id: I9adb35208dbf4f80db12b766ff273aaa27927a6d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65084 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Nicole Cordes <typo3@cordes.co> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
- 29 Jun, 2020 1 commit
-
-
nprogress is used to indicate activity when a collapsed IRRE node is about to get loaded. In case of FlexForms the id attribute may contain a dot which is not an issue if handled correctly. However, nprogress doesn't treat this value as an id, but rather as a full CSS selector which causes issues and breaks loading the IRRE node. To work around this issue, the id of the container used to render the progress bar is now MD5 hashed. Resolves: #91585 Releases: master, 10.4 Change-Id: I893d0cf24ea0f384d9ffff4d84f83b0fa35341b7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64783 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
- 20 Jun, 2020 2 commits
-
-
Andreas Fernandez authored
The JavaScript functions TBE_EDITOR.fieldChanged_fName` and its legacy alias `TBE_EDITOR_fieldChanged_fName` used to extract the table name, field name and uid from the incoming field name have been removed. As a drive-by bugfix, the undefined variables `TBE_EDITOR_setHiddenContent` and `TBE_EDITOR.setHiddenContent` have been removed as well. Resolves: #91578 Releases: master Change-Id: I528fde709367d5d474b846f347a3770d15b1a227 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64678 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
Andreas Fernandez authored
Some modules have been rewritten to not use jQuery in the past. However, there was still a dependency due to missing `ready` handling. Since recent changes TYPO3 is capable of such handling and enables to remove jQuery completely from some modules. Resolves: #91598 Releases: master Change-Id: I23fa63f9090eee8abc49cd1993df27bec12d92e2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64832 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 09 May, 2020 1 commit
-
-
It's safe to use getElementById() instead of querySelector() in case an element is fetched by its ID. Numbers for nerds: getElementById() is nearly 1.5x faster than querySelector(). To be fair, both functions are really fast with executing multiple million operations per second, thus nobody will notice a performance impact. See https://www.measurethat.net/Benchmarks/ShowResult/106740 Resolves: #91254 Related: #91183 Releases: master Change-Id: I2ed590d20c9af66ce818f012ac73ec45c5c9fa55 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64384 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
- 03 May, 2020 1 commit
-
-
Andreas Fernandez authored
IRRE relied on the HTML comment `<!--notloaded-->` to detect whether a record is already loaded or not. As this might collide with HTML minification, the comment has been replaced with a class placed in the panel. Resolves: #91258 Releases: master Change-Id: Ibe890317bdcb9707a71de1168de0d404fb3c67a4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64385 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Xavier Perseguers <xavier@typo3.org> Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Xavier Perseguers <xavier@typo3.org> Reviewed-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 01 May, 2020 1 commit
-
-
Andreas Fernandez authored
The InlineControlContainer tried to fetch elements via `querySelector()` previously. This fails once the selector contains a character that has a specific meaning for the whole selector, e.g. a dot. Having a selector `#foo-bar-settings.test` instructs the query selector to fetch an element matching the ID `foo-bar-settings` and the class `test`. As we handle IDs only, we can safely use `getElementById()` which doesn't have the previously mentioned implications. Resolves: #91183 Releases: master Change-Id: I63d23428ee548140f42e2c551d155ac829a2b596 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64343 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Raphael Zschorsch <rafu1987@gmail.com> Tested-by:
Armin Vieweg <armin@v.ieweg.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Raphael Zschorsch <rafu1987@gmail.com> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 18 Apr, 2020 1 commit
-
-
Christian Eßl authored
Resolves: #91103 Releases: master Change-Id: If342b9bf69574b54d598e342c3bb2773dba582cb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64224 Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Jonas Eberle <flightvision@googlemail.com> Reviewed-by:
Christian Eßl <indy.essl@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Jonas Eberle <flightvision@googlemail.com> Tested-by:
Christian Eßl <indy.essl@gmail.com>
-
- 23 Mar, 2020 1 commit
-
-
If assets get imported via mass selection in the Element Browser, the order of the items is now kept. Since this requires interframe communication, the Inline Control Container now sends a postMessage to the Element Browser. When the import process starts, the first asset of the selection gets imported. After the import, the postMessage is intercepted and the next asset get imported, until the queue is empty. As this could be a rather lenghty process, a progress bar is rendered at the top of the file table. To get a more fitting naming, all previously used action names used in postMessages have been renamed from `typo3:foreignRelation:inserted` to `typo3:foreignRelation:insert`. As a drive-by fix, the server is not spammed with n request anymore due to queueing. Resolves: #86362 Resolves: #59341 Releases: master Change-Id: Ib9e3ee8d943582874a0a73632968f8660b169b42 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63838 Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
- 20 Mar, 2020 1 commit
-
-
The event listener for collapsing and expanding IRRE nodes is now less greedy and ignores the div containing all control buttons which makes the buttons without click event (e.g. "Edit metadata") functional again. Resolves: #90796 Releases: master Change-Id: Ie19547bc5fbf21124f4a658ffc3a28b157242d51 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63817 Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 10 Mar, 2020 1 commit
-
-
Andreas Fernandez authored
This patch changes the behavior of the FormEngine internal ValueSlider by creating a new instance per occurrence of the slider to solve event stacking issues. Due to the new structure of the module, it's moved into FormEngine/FieldWizard. Resolves: #90673 Releases: master, 9.5 Change-Id: I80f2f2faeb37fb793b19cede7b629d8c415072d3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63597 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-