- 13 Jan, 2022 1 commit
-
-
This introduces a new PSR-14 event, enabling extension authors to modify the header and footer content of the page module in a flexible way, since also reordering and overwriting is possible now. This replaces the previously available hooks - $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['cms/layout/db_layout.php']['drawHeaderHook'] - $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['cms/layout/db_layout.php']['drawFooterHook'] which are now removed. Resolves: #96526 Releases: main Change-Id: I5fb3f3098394b70ecc4e5cc11c804f7125ad2a4a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73003 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
- 12 Jan, 2022 1 commit
-
-
Christian Kuhn authored
This patch introduces a new EXT:fluid view class "BackendTemplateView" to be used as main view for backend-related non-Extbase views. This class is the base of a new non-Extbase and non-request dependent backend view. The class is for now marked @internal and experimental since we'll probably add a factory to configure backend template overrides for any backend view later-on. A few ViewHelpers are changed to work without accessing the request if enough VH arguments are provided. This is the first patch in a series of patches that will switch from StandaloneView usages in backend controllers to this new BackendTemplateView. Basic strategy: * $view->getRequest()->setControllerExtensionName('SysNote') is removed. This is Extbase-specific and not needed nor wanted for common non-Extbase controllers. * Instantiate the View (for now with makeInstance, will be replaced with a factory later-on) * Set the needed paths via ->setTemplateRootPaths() etc. For these, we *always* use the main extension's entry templating paths, for instance 'EXT:sys_note/Resources/Private/Templates' or 'EXT:sys_note/Resources/Private/Partials'. We do *not* use sub directories here to clear up path logic. * ->assign() / ->assignMultiple() whatever is needed. * ->render('SubDirectory/TemplateName') the actual action / template, no '.html' suffix. As a demo, EXT:sys_note is adapted accordingly which hands over arguments to the above mentioned VH's in a way so these don't access the request object anymore. The sys_note code gets a couple of additional changes so the hooks can prepare request dependent arguments and set them as template variables (here: returnUrl). This patch triggers a hidden gem: Since ViewHelpers no longer receive an Extbase request, they also don't trigger Extbase magic anymore. The casual victim here is f:translate, which has already been prepared to not trigger Extbase's frontend TypoScript parsing if there is no Extbase request. This often improves backend view performance by 25% or more, depending on the amount of frontend TypoScript to parse. Further patches will adapt other core backend routes and will relate to this patch for reference. Change-Id: I4fec3ad690452a00e731c9f6928273048397dd89 Resolves: #96513 Related: #96473 Releases: main Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72966 Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 11 Jan, 2022 2 commits
-
-
Oliver Bartsch authored
With #95387 the menu generation of the page module was moved to the end of the request handling method. However, the `makeActionMenu()` method does currently not only create the menu but does also make some sanity check, whether the currently selected `function` is actually available. If not, the `function` is reset to the default ("columns mode"). This e.g. happens when in languages mode and then switching to another domain / another site, which is single language only. This then led to the user being unable to work in "columns mode", since no action menu is generated for such sites. This is now fixed by executing the mentioned method before the content gets generated. Resolves: #96084 Related: #95387 Releases: main, 11.5 Change-Id: Iadb67ece1724b6d34a4724d7782bdd295cece642 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72971 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
NewRecordController (+ icon in doc header of list module) renders "Create a new page" on top. This is not a link and looks misplaced. It is a 'section header' for optional content that can be enabled via pageTS. mod.wizards.newRecord.pages.show.pageSelectPosition = 1 mod.wizards.newRecord.pages.show.pageInside = 1 mod.wizards.newRecord.pages.show.pageAfter = 1 When at least one of these are enabled, the header makes sense, but should be avoided otherwise. Resolves: #96505 Releases: main, 11.5 Change-Id: I6468cda44e719f268f6b59d7e61f240737da6f33 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72962 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 08 Jan, 2022 1 commit
-
-
The type can already be inferred from the source code. The cleanup was run automatically with a PHPStorm plugin. Resolves: #96482 Releases: main Change-Id: I669145adc66dc898f3016de1958cf0105c988243 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72907 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 04 Jan, 2022 1 commit
-
-
Benjamin Franzke authored
With the changes in #95854, database mounts are no longer sorted by the order they are defined in the group/user settings, but undefined by the order the database returns. DB mounts aren't sorted against each other, that means sorting values are not meaningful anyway, and results in uncontrolable orderings. Explicitly preserve the order using usort(). Also revert groupAndSortPages() to the state prior to #95854, as the forcePid parameter would now be unused. Releases: main, 11.5, 10.4 Resolves: #96359 Related: #95854 Change-Id: I64b8d90c68246cc0ac01abcbf3678aa1055189e3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72813 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
- 03 Jan, 2022 1 commit
-
-
Resolves: #96443 Releases: main, 11.5 Change-Id: I9f1c951628cf8872473ff20bbd59ffb769ffe279 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72819 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 30 Dec, 2021 1 commit
-
-
With the changes in #95854, implicit rootPid dbmounts caused duplicated pages in pagetree, because explicit page mounts have been considered multiple times for the pid=0 tree: * First time because of their relationship to pid = 0 * Second time because of their explicit mount (which was sorted into the pid = 0 tree) This happened because #95854 optimized to only use one call to the PageTree repository, which then had the side effect of merging "multiple" pages into one tree, instead of showing "two" separate trees. The patch ensures that multiple page trees are used when the rootPid (0) is included as a webmount. Releases: main, 11.5, 10.4 Resolves: #96367 Related: #95854 Change-Id: I7f421995f2d4aa88bb266fec684565102a4dc080 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72812 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 23 Dec, 2021 1 commit
-
-
This fixes several issues for the case that an editor only has access to translated pages and not to the default language (L=0). Resolves: #95795 Releases: main, 11.5, 10.4 Change-Id: Ied31c7aa5229d3b8686741dd97005f9b5f16ef16 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72616 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 20 Dec, 2021 1 commit
-
-
Christian Kuhn authored
BackendController renders "Main.html" as central backend skeleton, plus "Topbar.html" and "MainModule.html". The patch moved the templates into one folder. Resolves: #96404 Releases: main Change-Id: I485d9ff03e457d78c8454e36ac893fbbc1ffe77c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72746 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech>
-
- 15 Dec, 2021 1 commit
-
-
Christian Kuhn authored
$command being either 'new' or 'edit' is tested in a previous if() a couple of lines above already. Resolves: #96357 Releases: main Change-Id: I8088d50df6c854127ebecb8038a648fdad9af172 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72662 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 14 Dec, 2021 1 commit
-
-
Oliver Bartsch authored
The SelectTree and the CategoryTree use a placeholder form element with all the information like current value and then calls the FormSelectTreeAjaxController to actually build the tree. When using default / override values for such field, the information was previously only available on building the placeholder. Therefore the value was correctly filled and stored, but not displayed in corresponding tree. This is now fixed by passing those values to the Ajax endpoint, which then adds them to the form compiler input. This allows the data providers to properly select the values in the tree. Resolves: #91607 Releases: main, 11.5 Change-Id: I8743bc3c28977b8d8758096b573a0be332d825e8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72645 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 13 Dec, 2021 3 commits
-
-
$this->firstEl is checked for !== null several times in EditDocumentController, but it most certainly isn't, because reset() returns false instead of null, if the array is empty. This patch resolves this problem by setting $this->firstEl to null, if reset($this->elementsData) returned false. Resolves: #96342 Releases: main, 11.5 Change-Id: I45b7aff02d7b601e16fd05862542a9e3955de908 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72638 Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
physikbuddha <r.kaerner@oranto.de> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
physikbuddha <r.kaerner@oranto.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org>
-
Oliver Bartsch authored
Since #96154, the shortcut button is invalid in case no `$displayName` is provided. For such case, the ButtonBar throws an unhandled exception. The EditDocumentController previously failed to ensure that the corresponding value is always properly set, which therefore led to mentioned exception in some cases. To fix this, it's now ensured that `getShortcutTitle()` does always return a valid title. In case something is wrong, e.g. no valid query arguments are provided, a default title is used. Previously, the `$recordId` in `getShortcutTitle()` was always directly casted to an int. However, since it is also possible to edit multiple records, the $recordId` might be a comma separated list of uids. This case is now also properly handled. Note: The `getShortcutTitle()` is since #94182 also used for the module title. This might be a misuse and will therefore be further evaluated in another patch. Resolves: #96337 Related: #96154 Releases: main Change-Id: I2ec6a5d2ab8d5263315e8fa7194bc887b084ae79 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72632 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
Oliver Bartsch authored
Actions to site configurations, in the site configuration module, are now properly logged with the new logging type "site". Resolves: #91744 Releases: main, 11.5 Change-Id: I43156f0ac4eaa538e1f10442d4e54d141073e6da Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72624 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 10 Dec, 2021 1 commit
-
-
This fix a warning when you click on a Rollback (preview) button in history for pages or content elements. Resolves: #96325 Releases: main, 11.5 Change-Id: Iec42cd04289a4c567840651686808b9ef43e1656 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72615 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 09 Dec, 2021 1 commit
-
-
The feature `runtimeDbQuotingOfTcaConfiguration` is now always enabled. This as a consequence also removes db connections before TCA is loaded, which is required since #96291. Resolves: #96300 Related: #96291 Related: #94697 Releases: main Change-Id: Ib91701adf451a3475da41eb5520ec7932115a253 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72566 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
- 08 Dec, 2021 1 commit
-
-
Due to the introduction of URL rewrites for backend links in #93048, the `route` parameter got superfluous and is therefore no longer added to backend urls. Resolves: #96281 Related: #93048 Releases: main Change-Id: Ibbbea03873fa955be5fd0113ca37bf9821aabfcc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72552 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 07 Dec, 2021 1 commit
-
-
Oliver Bartsch authored
The database table sys_language has become obsolete with the introduction of site handling and site languages. Therefore, the sys_language database table and the corresponding TCA is now removed. Fixtures and tests are adjusted to no longer rely on this table. Additionally, also a couple of code comments through the Core are adjusted. Executed commands: composer u typo3/cms-styleguide Resolves: #96277 Related: #94165 Releases: main Change-Id: I4ab0f3c7bb6de110cc1ce9826b2718f60d8a18a0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72534 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 03 Dec, 2021 2 commits
-
-
Oliver Bartsch authored
To support editors, the page module checks whether configured shortcut targets exist and if they are accessible in the frontend (e.g. not hidden). Otherwise, a info box is displayed on the page, defining the shortcut. However, in case a target page has group restrictions defined (`pages.fe_group`), it was previously declared as non accessible, since no frontend group context exists in backend. This is now fixed by disabling the group access, while searching for target pages. Resolves: #96184 Releases: main, 11.5 Change-Id: I173dfc4b6c5877a3a3ab458e890530fc167712aa Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72471 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Achim Fritz <af@achimfritz.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Achim Fritz <af@achimfritz.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
Oliver Bartsch authored
To improve the accessibility of the login screen, the logo got an "alt" attribute added in #92628. In case a installation uses a custom login logo, also a custom "alt" text could be provided. Previously the "alt" attribute was omitted, in case a custom login logo was used, but no custom "alt" text was defined. The presence of the "alt" attribute is now enforced by falling back to the default "alt" text, in case a custom logo is used, but no custom "alt" text is configured. Resolves: #96212 Related: #92628 Releases: main Change-Id: Id5074d72c9622f0ba3399015381e1cdf1813d0eb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72474 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 02 Dec, 2021 4 commits
-
-
Custom `FormEngine` nodes using internal property `fieldChangeFunc` must assign instances implementing `OnFieldChangeInterface` - using scalar values (inline JavaScript as string) is not supported anymore. `OnFieldChangeInterface` existed in TYPO3 v11 already, which allows custom implementations to be compatible with TYPO3 v11 and TYPO3 v12. Resolves: #96158 Releases: main Change-Id: Iad2ed520f40f9965b93fedd47f60164267e38ec6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72402 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Since TYPO3 is fully capable of using absolute URLs in Frontend (Site handling) and Backend (URL Routing), the FAL API related option "relativeToCurrentScript" is now removed. Resolves: #96201 Related: #94193 Releases: main Change-Id: Ieaca44f705544a886b5f6eeabe6f955d80013706 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72461 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Resolves: #96185 Releases: main, 11.5 Change-Id: I4138c226c93ba0fb0f578a35f736a6e0b7598e6a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72447 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
The hook "$GLOBALS['TBE_MODULES_EXT']['xMOD_db_new_content_el']['addElClasses']" is now removed. The newer alternative $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['cms']['db_new_content_el']['wizardItemsHook'] should be used instead. Resolves: #96189 Related: #95343 Releases: main Change-Id: I04d839b9c09d5737d00deeab7184f92486a599df Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72449 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 01 Dec, 2021 1 commit
-
-
The Shortcut API, handling the "shortcuts" in the backend was reworked in v11. This included adaptations to the new backend routing next to code cleanup. Therefore, this patch now removes old API methods, a ViewHelper and a couple of legacy fallbacks. Resolves: #96154 Related: #92132 Related: #93060 Related: #93093 Releases: main Change-Id: Ie1f75497c40656966e3eda129d8e7582b32f591b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72394 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 27 Nov, 2021 1 commit
-
-
Toolbar items are now automatically tagged and registered, based on the implemented `ToolbarItemInterface`, using the autoconfiguration feature from the DI container. The registration via `$GLOBALS['TYPO3_CONF_VARS']['BE']['toolbarItems']` has been removed. Resolves: #96041 Related: #62928 Releases: master Change-Id: Ic3d84752f30444d5a6be67ecbfe39e525c68e9ac Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72241 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 26 Nov, 2021 1 commit
-
-
Currently the inline edit button is shown even though a user does not have necessary edit permissions. This has been fixed by adding the necessary checks. As a side effect, the corresponding t3js class is no longer added to the header for modules, not representing an editable record title. Resolves: #96030 Releases: master, 11.5 Change-Id: I630e97263a950cf00229ce0613e2c4d35a11425e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72233 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 19 Nov, 2021 1 commit
-
-
Benjamin Franzke authored
This applies to rendering of database mounts (from groups or from workspaces): They are now shown as children of the virtual root page (uid=0) as it used to be in TYPO3 v8. This is to allow workspace users to get an overview of all changes of all mounts by navigating to the virtual page uid=0. Releases: master, 11.5, 10.4 Resolves: #95854 Related: #95972 Related: #91145 Change-Id: I7f6370f327711396193cf56b63f15876350c2559 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72028 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
- 18 Nov, 2021 2 commits
-
-
Closing a popup window does not use inline JavaScript code anymore. Resolves: #96019 Releases: master, 11.5 Change-Id: Iea2354e30d51ddcd24d9288fe5fa87b924259c13 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72222 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Torben Hansen <derhansen@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Torben Hansen <derhansen@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
When resolving inline JavaScript invocations in issue #95954 it looked like AJAX-aware elements in FormEngine would share a common abstract implementation in the client-side handling. Actually AJAX response handling is independent for each of those elements... This change now applies changes, that previously have been made to `TYPO3/CMS/Backend/FormEngine/InlineRelation/AjaxDispatcher`, to `TYPO3/CMS/Backend/FormEngine/Container/FlexFormSectionContainer`. Resolves: #96027 Releases: master, 11.5 Change-Id: Icf507a32399f72182597e9c8d650fb2d9a35e480 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72231 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Jörg Bösche <typo3@joergboesche.de> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
- 17 Nov, 2021 1 commit
-
-
Due to a bug, inline form fields were initialized twice, causing internal application state issues in FormEngine and Modal handling. Resolves: #96009 Releases: master Change-Id: I07f75ae90826eec77515ec84e69f4154828295a1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72214 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Chris Müller <typo3@krue.ml> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
- 15 Nov, 2021 3 commits
-
-
Reduces amount of `requireJsModules` and `scriptCall` invocations in AJAX response handling and migrates to new `scriptItems` which is forwarded to JavaScriptHandler.js. Resolves: #95954 Releases: master Change-Id: I258da49fef46ccc36c602e0fd7c9a14ddb3cec1d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72154 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benjamin Franzke authored
empty() returns true if a record contains 0 as value. Therefore isset() needs to be used instead. The corresponding fix that was introduced with #91145 to workaround this flaw is removed again. Resolves: #95972 Related: #91145 Releases: master, 10.4 Change-Id: Idfea91b84d8391d680900966f57b406c28a616ce Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72170 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
There were several problems with tooltips in the page tree: - htmlspecialchars was applied twice to the tooltip string. Once in BackendUtility::titleAttribForPages, once in TreeController. - When applying double or single quotes to a page title, the tooltips in the page tree would show these as html entities. Double and single quotes are now allowed, while any potential html tags in the title will be stripped from the tooltip. Any of those characters (", ', <, >) left in the tooltip are later escaped to unicode in the json view. Resolves: #91424 Releases: master Change-Id: I53b2ad6bbd4e4131535eb573422a8cbd5d002858 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64511 Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
- 10 Nov, 2021 2 commits
-
-
FlexForm Section can be added before content element is saved. This is done by ensuring that processedTca have a value for list_type. Earlier the pi_flexform was ignored as the default values on create before save was empty. Resolves: #81684 Releases: master, 10.4 Change-Id: I62e03cbbd93e8785f58c24dad1e573e8b5e0202b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68152 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
To decrease the amount of inline JavaScript that has been generated by some PHP process assignments and invocations are declared in a more strict way. This would allow to make use of strict content security policy denying invocation of unsafe-inline scripts. Resolves: #91786 Releases: master Change-Id: I89384d661ebd35a5fda10f9587a7f41db4f587aa Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64123 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Torben Hansen <derhansen@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Torben Hansen <derhansen@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
- 04 Nov, 2021 1 commit
-
-
This patch adds an error if the site configuration file cannot be written or deleted. Exceptions thrown while failing to write the site configuration are now caught and shown as error messages instead of breaking the backend in DebugContext or silently ignoring the error in LiveContext. Resolves: #91490 Releases: master Change-Id: I27802eb1a3798d305635df0eeebda8720f7bea47 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64582 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- 03 Nov, 2021 2 commits
-
-
Instead overriding class member variables externally, existing initialize() method has been extended to support options. This is a preparation to reduce the amount of inline JavaScript later. Resolves: #95845 Releases: master Change-Id: I7d76761e6b57a6e97163ca2ad721a2b1c8775e3c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72022 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Jochen <rothjochen@gmail.com> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org>
-
Changes read-access to modules from `ModuleLoader::$modules` to `ModuleLoader::getModules()`. Resolves: #95851 Releases: master Change-Id: I011f014f6d1c70051e269b696b00a6a7c5c77a6e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72026 Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de>
-