- Apr 28, 2024
-
-
Andreas Kienast authored
With the update of Bootstrap to v5.3, the implementation of progress bars has changed for accessibility reasons [1]. This commit updates all usages of progress bars to the new markup. [1] https://getbootstrap.com/docs/5.3/migration/#progress-bars Resolves: #103718 Releases: main, 12.4 Change-Id: I208e3561b4943e382caa09e23e75d350bd702a6a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84014 Tested-by:
Benjamin Franzke <ben@bnf.dev> Tested-by:
Andreas Kienast <a.fernandez@scripting-base.de> Reviewed-by:
Andreas Nedbal <andy@pixelde.su> Reviewed-by:
core-ci <typo3@b13.com> Reviewed-by:
-
- Apr 27, 2024
-
-
Jasmina Ließmann authored
As in the backend module "Configuration", search results can be displayed as badges next to the search input field. When the search input field is displayed with a label instead of placeholder text, the badge was displayed out of place. This patch aligns the badge to the search input field. In addition, the search field now takes up full width for small breakpoints. Resolves: #103716 Releases: main Change-Id: I322b4ab4c62823fa6dcf9d00fc30bc8671c57f09 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84013 Reviewed-by:
Garvin Hicking <gh@faktor-e.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
- Apr 26, 2024
-
-
Benjamin Kott authored
Both extensions core and linkvalidator do not ship css files. PostCSS cannot find any files to process here. Resolves: #103731 Releases: main, 12.4 Change-Id: Ibdfcecb4dd813b04e89bab5d2fcfe3a55b0bf4b4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84033 Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
-
Benjamin Kott authored
We're enhancing our backend by introducing a refined system for shadows. The default and strong shadows remain for simple components, while tooltips, flyouts, dialogs, and windows have dedicated ones. This streamlines shadow definitions across elements, ensuring consistency. Shadows support both light and dark modes for visibility across all settings. Resolves: #103726 Releases: main Change-Id: Id02122a9f48833df03e28613642499b63c339b45 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84019 Tested-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
-
Benjamin Franzke authored
Provide a new (default) EXT:styleguide frontend generator that uses site set infrastructure provided by #103437, #103439 and #103522. The old sys_template-root based renderer is preserved and tested independently Resolves: #103034 Related: #103437 Related: #103439 Related: #103522 Releases: main Change-Id: I53c986d7a47c8c2687b2a240410f9d4130fbae4b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83696 Tested-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
-
- Apr 25, 2024
-
-
Willi Wehmeier authored
The modal form to rename a file needs a proper label for the filename input field. Resolves: #103724 Releases: main, 12.4 Change-Id: I29018d288ced1de6001d38b841ef37a1231f7394 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84021 Reviewed-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
-
Benjamin Kott authored
We're currently in a mixed mode where some components support dark mode, while others don't. To facilitate the migration of components currently incompatible with dark mode, we're setting the default to light mode for now. This allows us to gradually migrate components and enable the dark mode switch once both a component and its context are ready for it. Resolves: #103723 Releases: main Change-Id: I39e31d9b7170ac5592f58afe9f9dced0fd14c4c4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84020 Tested-by:
-
- Apr 24, 2024
-
-
Andreas Kienast authored
The grunt module `grunt-newer` was introduced with #90200 to help improving build times on consecutive single builds by running tasks on changed files only. This is nowadays not required anymore in JS build context, as it's possible in TypeScript to compile changed files only, which is already incorporated for quite a while. Therefore, the usage of `newer` is now removed in this context. However, to avoid running `terser` multiple times on the same, previously compiled files, the directory `Build/JavaScript` now gets removed before each TypeScript compilation. The postcss calculation is fast enough to not require grunt-newer at all, therefore grunt-newer is dropped here as well. Executed commands: npm remove grunt-newer Resolves: #103712 Releases: main, 12.4 Change-Id: I1c6b88945a45cb9a394a2beaa2ec8198865880b0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84006 Tested-by:
-
- Apr 23, 2024
-
-
Andreas Nedbal authored
In the current frontend tooling, we invoke Rollup twice: * via grunt-rollup to build library modules * via the command line to build everything related to CKEditor This commit gets rid of the first way and moves the library compilation to a JS-backed configuration as well, so we can get rid of a grunt package and also unify the tooling a bit. We also make use of @rollup/plugin-terser instead of the deprecated rollup-plugin-terser module that was used in ckeditor build before. To match the new behaviour, the "exec:ckeditor" task also was renamed to "exec:rollup". Executed commands: npm remove grunt-rollup npm remove rollup-plugin-terser npm install @rollup/plugin-terser --save-dev npm run build Resolves: #103686 Releases: main, 12.4 Change-Id: I8057dcceae2d039c637c6db68cf51b3ef1f12406 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83942 Tested-by: -
Jasmina Ließmann authored
To improve the UX and accessibility of the "Workspaces" backend module the following changes are made: * Grouping and rearranging action buttons * Showing system language title in addition to the flag icon * Addition of a new "Action" column to represent the type of change and resolve the previous workspace state legend and colored record titles * Output notification messages with the icon if integrity issues exists * Removal of the live record column (This only contained the name of the live record and no other function. Additionally, records created in workspace were also displayed incorrectly in the live column even though they did not yet exist in live environment.) Resolves: #103670 Releases: main Change-Id: Ic7cd00fc46b638adaca9bd4cf4c6a97f2a53d787 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83924 Reviewed-by:
Jasmina Ließmann <minapokhalo+typo3@gmail.com> Reviewed-by:
-
Ayke Halder authored
There is a checkbox in page module to show hidden content elements. If this checkbox is not selected the hidden content elements must be hidden. Additionally hidden elements must not be accessible/focusable by keyboard. Resolves: #103626 Releases: main, 12.4 Change-Id: Id8f4b98938ae27e3bd3d3e7903c3f50588d554b8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83781 Tested-by:
Willi Wehmeier <wwwehmeier@gmail.com> Tested-by:
-
Benjamin Kott authored
With new web standards arising and getting shipped to the web platform, we are migrating the currently limited light and dark mode components to the web native color-scheme. See: https://developer.mozilla.org/en-US/docs/Web/CSS/color-scheme Instead of relying on preferred color scheme queries, we're adopting the light-dark color function, streamlining our CSS and ensuring compatibility with all major browsers, except Safari (for now). While Safari is slightly behind, we anticipate full support for light-dark mode by May 2024, with the feature already available in Safari 17.5 Beta. See: https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/light-dark See: https://developer.apple.com/documentation/safari-release-notes/safari-17_5-release-notes Note: Safari users will experience missing backgrounds and colors due to our decision not address this behavior. We're forward-facing and planning for the LTS release. If you intend to use Safari during development, please ensure you're using at least Safari 17.5 Beta. We're monitoring the situation closely and will implement a fallback if Safari hasn't released a compatible version before 13.2. Resolves: #103705 Releases: main Change-Id: I9f53e992f4d55efd86420a72a84da9d90b16e490 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83995 Tested-by:
Frank Nägler <frank.naegler@typo3.com> Tested-by:
-
Benni Mack authored
Change-Id: I06f3088f1b06adc56000391ea0af8bc199586cb8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83993 Tested-by:
-
Benni Mack authored
Change-Id: I0de3c394a9e37ca840c3d0aa6f6df745bca8ac3b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83992 Tested-by:
-
Andreas Kienast authored
Executed commands: npm install --save chart.js@^4.4.2 npm run build Resolves: #103652 Releases: main, 12.4 Change-Id: Iddbfb5be5f998c7b9d693dac94fee88a1f242edf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83851 Tested-by:Simon Schaufelberger <simonschaufi+typo3@gmail.com> Tested-by:
-
Andreas Kienast authored
Executed commands: npm install --save alwan@^2.0.4 npm run build Resolves: #103651 Releases: main, 12.4 Change-Id: I56b52fdff9031eec2cabfaeb968469a20fa72bb0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83850 Reviewed-by: -
Andreas Kienast authored
Executed commands: npm install --save-dev \ @typescript-eslint/eslint-plugin@^7.7.0 \ @typescript-eslint/parser@^7.7.0 \ @typescript-eslint/typescript-estree@^7.7.0 \ eslint-plugin-wc@^2.1.0 \ sass@^1.75.0 \ sharp@^0.33.3 \ terser@^5.30.3 \ typescript@^5.4.5 npm run build Resolves: #103653 Releases: main, 12.4 Change-Id: I96bb9e96d12182adc33b5fafb52d53a4fecf6806 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83872 Tested-by: -
Andreas Kienast authored
The "No results found" alert is rendered in a flex-row container, which caused a rendering bug where the alert box was stretched to a height of 100%, but its width is limited to its content. Use flex children modifiers to ensure correct positioning. Resolves: #103662 Releases: main, 12.4 Change-Id: I5b17950ca381fda841cd3a901d9f5e1a70e5562d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83919 Reviewed-by:
-
- Apr 22, 2024
-
-
Andreas Kienast authored
In order to streamline the backend UI and to re-use introduced web components, the "Add widget" wizard in the dashboard module now utilizes the `@typo3/backend/new-record-wizard` module that is already known from the Content Element creation wizard. As a small quality-of-life change, the modal title now includes the name of the dashboard as well. Resolves: #103697 Releases: main Change-Id: I58f069e5d3f57484cba8e020f51ab82cf923d25a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83937 Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
-
Andreas Kienast authored
Executed commands: npm install --save \ lit@^3.1.3 \ lit-element@^4.0.5 \ lit-html@^3.1.3 npm run build Resolves: #103654 Releases: main, 12.4 Change-Id: Id250be2076f29d095cffed34bffe3f882feb223d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83874 Reviewed-by:Fabien Udriot <fudriot@omic.ch> Tested-by:
-
Andreas Kienast authored
The component `@typo3/backend/new-content-element-wizard` is primarily used to render a wizard-like UI for selecting a content element for creation. To make the component usable in other places as well, it get's renamed to `@typo3/backend/new-record-wizard`. Resolves: #103683 Releases: main Change-Id: I9ad19d95fd0c8aa1efb60c335726dac57eb7c54c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83936 Reviewed-by:
-
- Apr 18, 2024
-
-
Andreas Kienast authored
Executed commands: npm install --save-dev flag-icons@^7.2.1 npm run build Resolves: #103656 Releases: main, 12.4 Change-Id: Ibebf001a8867104d616777adf47b7c0edaccbf9d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83876 Tested-by:
-
- Apr 17, 2024
-
-
Jasmina Ließmann authored
The element information modal displays both field information for the current record and its references. The more fields there are in a table and the more content the specific record contains, the more the reference sections disappear from view. The three sections are now displayed as accordions to enable the user to decide for themselves which sections are relevant to them. In addition, the display of non-existent records in the reference sections has been adjusted and information about the paths/storage locations has been removed, as these can already be viewed in the record's editing mask. Resolves: #102469 Releases: main Change-Id: Ia4ba85921d7be2ab30477e8248d4fb8734f6eaaf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/81873 Tested-by:
-
- Apr 16, 2024
-
-
Willi Wehmeier authored
Add proper focus styles to the nav links in the Link Browser modal window. Resolves: #103631 Releases: main, 12.4 Change-Id: I0abb597124e335c3955c73438ac3cd2f0dad93bf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83786 Tested-by:
-
- Apr 15, 2024
-
-
Andreas Kienast authored
The "Upgrade Wiards" view automatically checks whether mandatory database changes are pending. In that case, a list of tables, fields and indices are rendered. Before the removal of jQuery, a line break was rendered between the list items. However, the migration was not complete, as the line breaks are now rendered as `<br>`. The commit fixes this by creating real `<br>` elements. Resolves: #103613 Releases: main Change-Id: I6896ceeaed30606f55ac4376002552f92224c878 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83784 Tested-by:
-
- Apr 12, 2024
-
-
Andreas Kienast authored
This commit replaces the abandoned package `@ronilaukkarinen/stylefmt` with the already installed `stylelint` tool. Please note that this is an intermediate step to give the build toolchain some love it deserves. Executed commands: npm remove @ronilaukkarinen/stylefmt npm install --save-dev \ autoprefixer@^10.4.19 \ postcss-scss@^4.0.9 \ stylelint@^14.16.1 \ stylelint-scss@^5.3.1 Resolves: #103612 Releases: main, 12.4 Change-Id: I1f283d50a1a6504c4c000e674c75a40923f6c7e7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83748 Reviewed-by:
-
- Apr 11, 2024
-
-
Andreas Kienast authored
This commit updates ckeditor to 41.3. See changelog at [1]. Executed commands: npm install --save \ @ckeditor/ckeditor5-alignment@^41.3.0 \ @ckeditor/ckeditor5-autoformat@^41.3.0 \ @ckeditor/ckeditor5-basic-styles@^41.3.0 \ @ckeditor/ckeditor5-block-quote@^41.3.0 \ @ckeditor/ckeditor5-clipboard@^41.3.0 \ @ckeditor/ckeditor5-code-block@^41.3.0 \ @ckeditor/ckeditor5-core@^41.3.0 \ @ckeditor/ckeditor5-editor-classic@^41.3.0 \ @ckeditor/ckeditor5-engine@^41.3.0 \ @ckeditor/ckeditor5-essentials@^41.3.0 \ @ckeditor/ckeditor5-find-and-replace@^41.3.0 \ @ckeditor/ckeditor5-font@^41.3.0 \ @ckeditor/ckeditor5-heading@^41.3.0 \ @ckeditor/ckeditor5-horizontal-line@^41.3.0 \ @ckeditor/ckeditor5-html-support@^41.3.0 \ @ckeditor/ckeditor5-indent@^41.3.0 \ @ckeditor/ckeditor5-link@^41.3.0 \ @ckeditor/ckeditor5-list@^41.3.0 \ @ckeditor/ckeditor5-paragraph@^41.3.0 \ @ckeditor/ckeditor5-paste-from-office@^41.3.0 \ @ckeditor/ckeditor5-remove-format@^41.3.0 \ @ckeditor/ckeditor5-show-blocks@^41.3.0 \ @ckeditor/ckeditor5-source-editing@^41.3.0 \ @ckeditor/ckeditor5-special-characters@^41.3.0 \ @ckeditor/ckeditor5-style@^41.3.0 \ @ckeditor/ckeditor5-table@^41.3.0 \ @ckeditor/ckeditor5-theme-lark@^41.3.0 \ @ckeditor/ckeditor5-ui@^41.3.0 \ @ckeditor/ckeditor5-undo@^41.3.0 \ @ckeditor/ckeditor5-utils@^41.3.0 \ @ckeditor/ckeditor5-word-count@^41.3.0 npm run build [1] https://github.com/ckeditor/ckeditor5/releases/tag/v41.3.0 Resolves: #103589 Releases: main, 12.4 Change-Id: Id24aac98727af0d0b9284e68dd8c4a4e138a6c15 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83730 Tested-by:Ayke Halder <mail@ayke-halder.de> Reviewed-by:
-
- Apr 10, 2024
-
-
Jasmina Ließmann authored
To better identify the different record types, the record icon is now displayed next to the record title and some unnecessary double quotes are removed. The actions are now displayed as badges. Also, in the h1 the table name and UID have been removed. Resolves: #103433 Related: #103291 Releases: main Change-Id: I5b09258ca688f0d4ecdd1737b00b8b5a156e6ace Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83528 Reviewed-by:
-
- Apr 08, 2024
-
-
Andreas Kienast authored
Similar to editing regular content elements, it is now possible to save scheduler tasks being edited via keyboard shortcuts as well. Resolves: #103563 Releases: main Change-Id: Ia159293670f3f3dc762f3c23da35e0e71d5541fd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83702 Reviewed-by:
-
Stefan Bürk authored
`Build/Scripts/runTests.sh` is the monorepo main dispatcher of script and tools to ensure same working state across developer host system and installation by using well defined containers. This mitigates issues with missing dependencies or wrong version of tools on develper machines. Until now local installation of `node` and `npm` in the matching version was mandatory to work with the node ecosystem like manage dependencies, executing node based tools or the build chain for CSS and TypeScript/JavaScript. This change adds now a `npm` dispatcher to `runTests.sh` similar to the `composer` command dispatcher introduced with #103045 to allow executing npm commands and defined scripts in `package.json` in a well-defined environment and removes the hard-requirement of installing it locally for new contributors. Added `runTests.sh` suite: * ./Build/Scripts/runTests.sh -s npm -- <npm-command-arguments> which allows now to using npm commands always with the correct npm and node version defined for the mono-repository state. Some examples: ./Build/Scripts/runTests.sh -s npm -- audit ./Build/Scripts/runTests.sh -s npm -- ci ./Build/Scripts/runTests.sh -s npm -- run build ./Build/Scripts/runTests.sh -s npm -- run watch:build ./Build/Scripts/runTests.sh -s npm -- install \ --save bootstrap@^5.3.2 Resolves: #103552 Related: #103045 Releases: main, 12.4, 11.5 Change-Id: Ie9de71f24dfd4805a98be7dc1b1604e5d0146eec Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83690 Tested-by:Thomas Hohn <tho@gyldendal.dk> Tested-by:
-
- Apr 07, 2024
-
-
Andreas Kienast authored
When t3editor got streamlined in the past, configuration for flex was defined that conflicts with CodeMirror's internal style definition, leading to UI glitches like "cut out" content, see screenshot attached to the ticket.. This commit removes the conflicting CSS. Resolves: #101442 Releases: main, 12.4 Change-Id: Ie5b9f8d498cdaef0b3455e05e247cb5fd64b0617 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83681 Tested-by:
Torben Hansen <derhansen@gmail.com> Reviewed-by:
-
Markus Klein authored
As documented by PHP, `\DateTime` or `\DateTimeImmutable` objects created with a timestamp only ('@12345678') as the first constructor argument will use UTC as TimeZone. Creating an object instance without any constructor arguments will use the `date_default_timezone_get()` timezone for the object - and setting the timestamp using `setTimestamp()` will not change the object's timezone. That means, that formatting the value will be done using the object Timezone and **NOT** the default PHP Timezone (`date_default_timezone_get()`). Consequently, this may lead to wrong interpretation of the displayed formatted value in the context of another timezone - if no timezone information (+0000/-0100) is included. This change streamlines this for a couple of places were it is expected to format date, datetime or time values for the current context timezone by ensuring objects get the current timezone set instead of `UTC`. Note: Changing the date default timezone on the fly after an object has been created will show a similar effect like using constructor values, even if the object has been created by using the `setTimestamp()` method. [1] https://3v4l.org/sGEe2 Resolves: #98045 Resolves: #99627 Releases: main, 12.4, 11.5 Change-Id: I095a0b0b376361e25396647d02727ac08f35cae0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/81915 Tested-by:Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Andreas Wolf <andreas.wolf@typo3.org> Tested-by:
-
- Apr 05, 2024
-
-
Stefan Bürk authored
New core-testing-* images has been build and published in the TYPO3 testing-infrastructure repository and pulled to the core ci gitlab runner instances. [1][2] This change modifies `Build/Scripts/runTests.sh` to set new image version to ensure the usage for all changes based on this change. For information what changed in the image see the patches in the testing-infrastrucure repository linked below. * core-testing-nodejs18 => 1.4 * core-testing-nodejs18-chrome => 1.4 [1] https://nodejs.org/en/blog/vulnerability/april-2024-security-releases/ [2] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/712e35c72cd7788d1d6311714b5a0dfe46e743a7 Resolves: #103518 Releases: main, 12.4 Change-Id: Ibaafbd465a21d631f6726064255241aa4b42e726 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83636 Reviewed-by:
-
Andreas Kienast authored
The JavaScript module `@typo3/backend/document-save-actions` was introduced in TYPO3 v7 to add some interactivity in FormEngine context. At first it was only used to disable the submit button and render a spinner icon instead. Over the course of some years, the module got more functionality. After some refactorings within FormEngine, the module became rather a burden. This became visible with the introduction of the Hotkeys API, as the `@typo3/backend/document-save-actions` module reacts on explicit `click` events on the save icon, that is not triggered when FormEngine invokes a save action via keyboard shortcuts. Adjusting `document-save-actions`'s behavior is necessary here, but would become a breaking change, which is unacceptable after the 13.0 release. For this reason, said module has been marked as deprecated and its usages are replaced by its successor `@typo3/backend/form/submit-interceptor`. Resolves: #103528 Releases: main Change-Id: Ic4ee972eb79da2331213de624adf077a7e5b567c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83643 Tested-by:
-
- Apr 04, 2024
-
-
Andreas Kienast authored
In the image editor, the "Cropped area" was configured with a `ceil`ed width and height. Since all other dimensions are `floor`ed, this might cause an overlap. Due to the configured cropping mode, defining that the cropping area must never exceed the image dimensions, the cropper library places the cropper to a position that's mathematically correct but not desired. To solve this issue, the `width` and `height` properties fed to the cropper are now `floor`ed as well, basically aligning with the rest of the coordinates. Resolves: #101520 Releases: main, 12.4, 11.5 Change-Id: I981bd185eaf0db60662a5a6b7b423d84112c2150 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83644 Reviewed-by:
Kevin Appelt <kevin.appelt@icloud.com> Tested-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
-
Oliver Bartsch authored
To regenerate a slug, the fields defined in the TCA "generatorOptions" configuration have to be present in the form. There are cases where those fields are added as hidden fields (e.g. using the "overrideValues" feature). Those fields are now also properly respected for the regeneration. Resolves: #103500 Releases: main, 12.4 Change-Id: I0ca7de4b7d7d09e62ece511aeb16615af3d3a1fa Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83622 Tested-by:
-
Andreas Kienast authored
A new hotkey is introduced in the FormEngine scope that lets editors invoke "Save and Close" via `Ctrl/Cmd+Shift+S`. Resolves: #103529 Releases: main Change-Id: I530a1df54707eb69033c8a03ccf58517facf162a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83642 Tested-by:
-
- Apr 03, 2024
-
-
Andreas Kienast authored
This commit changes how the "Toggle all" and option and action button states are determined. Previously, the state was determined via JavaScript, leading to an unexpected rendering change when the module has loaded. To avoid this, the state is now calculated in the controller as the necessary metrics are already known. In the same run, `optionByType.checked` is now a simple bool flag instead of holding arbitrary HTML attributes. Resolves: #103454 Releases: main Change-Id: I2da39063dbb9161873274dadddcc3b0384e36321 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83560 Tested-by:
-
- Mar 25, 2024
-
-
Oliver Bartsch authored
At various places, it's possible to edit the metadata of a file in the default language. However, users might not have access to the default language. To prevent moving to FormEngine and facing access permission errors, those places now use proper language access checks and do not display corresponding action if the user does not have access. Resolves: #103432 Releases: main, 12.4 Change-Id: I22c3755a17888cfc623ce05b25fd655b323cc553 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83573 Reviewed-by:
Jochen Roth <rothjochen@gmail.com> Reviewed-by:
-
- Mar 22, 2024
-
-
Stefan Bürk authored
New core-testing-* images have been build and published in the TYPO3 testing-infrastructure repository and pulled to the core ci gitlab runner instances. [1] This change modifies `Build/Scripts/runTests.sh` to set new image version to ensure the usage for all changes based on this change. For information what changed in the image see the patches in the testing-infrastrucure repository linked below. * core-testing-php82 => 1.12 * core-testing-php83 => 1.13 [1] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/ebdaefdb54a4fe970abf0cb1d32567bbd6339de5 Resolves: #103469 Releases: main, 12.4, 11.5 Change-Id: I35ffd10e7979d4fd59aab5a7fa5d52330e71e0e1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83569 Reviewed-by:
-
