- Jul 07, 2023
-
-
Andreas Fernandez authored
flatpickr doesn't provide an easy possibility to set the today's date. To solve this issue, the plugin `shortcut-buttons-flatpickr` is added with a configuration for the today's date. Resolves: #100635 Releases: main, 12.4 Change-Id: I882f05ab4486d1b3073008cadb1d0275dd77c8ce Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79867 Reviewed-by:
Benjamin Franzke <ben@bnf.dev> Tested-by:
core-ci <typo3@b13.com>
-
Benjamin Kott authored
Resolves: #101276 Releases: main, 12.4 Change-Id: Ie9941076dc54fc3c123241cf51a50a19a9145ec6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79866 Tested-by:
-
Benjamin Kott authored
This patch streamlines the import module with the import command. While the CLI commands can import data from extensions, the interface has no option to perform this action. We are now listing available datasets from distributions in the import module. Resolves: #101256 Releases: main, 12.4 Change-Id: I6fac0d22bbb42a6ff8b682b6c3415a3d7e4982d6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79863 Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
-
Benni Mack authored
This change adds the status quo for further MM-related work. This relates to some tests that had tests on "allowLanguageSynchronization" but not "l10n_mode=exclude" set. In addition, some MM-related tests were not added to all workspace-* tests anymore, which are now added: * copyContentToLanguageOfRelation * copyCategoryToLanguageOfRelation * localizeContentOfRelationWithLanguageExclude * localizeContentOfRelationAndAddCategoryWithLanguageSynchronization Resolves: #101285 Related: #80640 Releases: main, 12.4 Change-Id: Ib675b9bc263d519372a8028370db581e25a49edf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79864 Tested-by:
-
Susanne Moog authored
When `open_basedir` is set (often the case on shared hosting), TYPO3 fails to find executables as it does a check for file existence first, which fails due to the restriction. Instead of checking file existence in all cases, a fallback has been added on *nix systems that will try execution of a given command and use the return code to decide whether the path is valid. This itself uses the command `which` which is not available on Windows. As nowadays `open_basedir` is mostly used on shared hosting environments based on *nix, this will not be fixed for Windows. Resolves: #70869 Resolves: #85174 Releases: main, 12.4 Change-Id: Ic01e822ae16b9ef1fa80be745a9de51e527ba059 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79865 Tested-by:
-
Benjamin Kott authored
With #10551 a pretty cool new feature was introduced which will show you information about the status of non versionable records in list module of TYPO3 backend. These messages are now only be displayed, if extension workspaces is activated. Resolves: #101282 Releases: main, 12.4 Change-Id: I428535a2e301fa38b639fed99d70c8052dfaa6fd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79849 Tested-by:
Benjamin Kott <benjamin.kott@outlook.com> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
-
Stefano Kowalke authored
Releases: main, 12.4 Resolves: #101284 Change-Id: Idd633c9d764296c9ec2dfb482a75d59a9da3e2d4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79860 Reviewed-by:
-
Jochen Roth authored
A click on open/recently used documents the returnUrl was not set which led to a blank content frame when the close button on the record was clicked. This issue is fixed by adding the EditDocumentController's returnUrl to the OpenDocs payload and re-using it in the toolbar items. However, this will not work with already existing entries and a consistent behavior cannot be assured due to potentially (dis)allowed modules for each backend user. Resolves: #94214 Releases: main, 12.4 Change-Id: I29680172735a5c28c46268cd14b7e26dd0997cd9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79862 Tested-by:
-
Benjamin Kott authored
In sys_file_reference tables a standard basic palette is used for filetypes image, audio and video. Therefore no alternative field is shown in own tca field types file. Use specific file type palettes, to avoid rewriting in overrideChildTca in type=file fields. Resolves: #101277 Releases: main, 12.4 Change-Id: Ie47396e0876499be787f3d9ba9da94988d9f4e39 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79859 Tested-by:
-
Benjamin Kott authored
We are removing the pagination arrows from the translation files since they needed to be marked with "aria-hidden" to avoid acessibility issues. This would extend the usage of markup that should not be placed in translation files in the first place. To allow integrators to change the apperance we are now adding css classes that can be used to apply special styling for the next and previous links. Resolves: #101283 Releases: main, 12.4 Change-Id: I090da2922dd644e161440e4e5a1e47ef0963d839 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79858 Reviewed-by:
-
Oliver Hader authored
Indexed Search pagination still uses `onclick="..."` inline event handlers. For being compatible with content security policy, the corresponding handlers are added as inline JavaScript, embedded with a CSP nonce value. Resolves: #101271 Releases: main, 12.4 Change-Id: Ic1202faf8be2d1d9e84b599f62e8c9a53aeef2fa Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79857 Tested-by:
-
Susanne Moog authored
The rootline may contain extendToSubpages settings for hidden or timed records which prevented previewing a page because the preview checks only considered the current page. The rootline is now taken into account. Resolves: #17599 Releases: main, 12.4 Change-Id: I0271caf8decd46fd9dedf31158d62a86e1e0028c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79856 Reviewed-by:
-
Riny van Tiggelen authored
In case mod.web_layout.allowInconsistentLanguageHandling is set, no warnings about inconsistent language usage should be displayed. This is now properly checked in ContentFetcher, which would otherwise add a warning message to the queue. Resolves: #99171 Releases: main, 12.4 Change-Id: If0f6cce36e5d35e0ec5ca3df865cc5736bb44005 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79853 Tested-by:
-
Jochen Roth authored
Currently, when the selected db has already tables an exception is thrown This has been changed by showing a nicely formatted error message like done for any other error in this command. Resolves: #101172 Releases: main, 12.4 Change-Id: I09fe21a5cce71ff860f965244bee86474ee5c398 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79854 Tested-by:
-
- Jul 06, 2023
-
-
Oliver Hader authored
Package symfony/polyfill-intl-normalizer can be removed again, since ext-intl is already a composer requirement. Executed commands: composer rem symfony/polyfill-intl-normalizer composer rem symfony/polyfill-intl-normalizer \ -d typo3/sysext/core --no-update Resolves: #101275 Releases: main, 12.4 Change-Id: Id60b90ad3300175d2287a23e062f94975ad5fe86 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79844 Tested-by:Stefan Bürk <stefan@buerk.tech> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
Stephan Großberndt authored
Backend no longer crashes with an TableNotFoundException if a table has been removed and an according item is in the list of recent documents. The patch catches the exception. Releases: main, 12.4, 11.5 Resolves: #101139 Change-Id: I489d8cf1ee2bb10800fe2966ae4fc1cb0bcd57c5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79852 Reviewed-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
-
Sybille Peters authored
It is possible to rename a file with ResourseStorage::renameFile(). This is also used under the hood, if a file is renamed in the file list. RenameFile also performs a sanitation of the filename, in case the filename was not yet sanitized (e.g. convert chars like space, quote, ö, ê, ß or §). But if the target filename is the same as the current filename, the sanitation was not performed. This is now fixed so that the behaviour is more consistent and sanitizing files with renameFile() is possible. Resolves: #100683 Releases: main, 12.4 Change-Id: Ia35747f1381f4aac64af50c461e172c9f951cf83 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79787 Tested-by:
-
Sybille Peters authored
The redirects documentation contains a link to the issues on the page "Known problems", using a category filter. This used to be "Link Handling, Site Handling & Routing", but redirects now have their own category "Redirects Handling", so we use this. Resolves: #101260 Releases: main, 12.4, 11.5 Change-Id: Ife6c4bbd7b2db1476054d5ce2558f84f32ab4800 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79829 Tested-by:
-
Johannes Nielsen authored
So far the setup command did not consider default values in non-interactive mode. This led to unexpected errors when not passing in parameters, which should have default values, as either CLI parameters or ENV variables. Resolves: #100945 Releases: main, 12.4 Change-Id: If811c5c1ef9b7d8a5c776af407fac7d2ced4e654 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79831 Tested-by:
-
Oliver Hader authored
The filename of uploaded files might not be encoded as normalized unicode. For instance, this happens when using umlauts in filenames on HFS+ filesystem (macOS). For instance the client sends an `ö`, which is sent in NFD as `0x6fcc88`, but should be normalized as `0xc3b6`. https://en.wikipedia.org/wiki/Unicode_equivalence#Normalization Executed commands: composer req symfony/polyfill-intl-normalizer:^1.27 composer req symfony/polyfill-intl-normalizer:^1.27 \ -d typo3/sysext/core --no-update Resolves: #101253 Releases: main, 12.4, 11.5 Change-Id: I8605481ffdc3b5d96f529850bf09a1fd75d09cd2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79837 Tested-by:
-
Annett Jähnichen authored
If the pluginTitle wasn't set, a warning message was rendered in the page module as if the plugin wasn't configured. We now use the PluginName as default to create a visual difference between a plugin that is not configured. Resolves: #99775 Releases: main, 12.4 Change-Id: Ic069edce5a74989ee32b2d40b1e645dc5449690d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79828 Tested-by:
Annett Jähnichen <mcmietz@web.de> Reviewed-by:
-
Benjamin Kott authored
The backend layout representation in the backend implements a table based layout. While the columns spanning was interpreted correctly, the definition of how wide a column is in the defined grid was missing, causing the cells to take up an unexpected amount of space. Resolves: #101041 Resolves: #100961 Related: #97306 Related: #94629 Releases: main, 12.4 Change-Id: I8ab426e0c6e136135bf1bcf6bcc0368f76d4f4b0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79827 Tested-by:
-
Andreas Fernandez authored
In non-SVG trees, there are currently two icons representing the node's expansion state rendered that get toggled via CSS rules based on hard-coded aria attributes and icon identifiers, which is a bad practice. To solve this, a new web component `typo3-backend-tree-node-toggle` is added whose only responsibility is to render the correct icon based on its `aria-expanded` attribute Resolves: #100549 Releases: main, 12.4 Change-Id: I1a955731fc21da01a914b1ef721d7eb2d1e18ed5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79826 Tested-by:
-
Torben Hansen authored
The current backend password reset log message misses a `}` and logs the `user_id` if a password has been reset successfully. Logging the `user_id` is however not inline with other user related log messages, where always the `username` is logged. This patch streamlines the log message with other user related log messages by including the `username` instead of the `user_id`. Resolves: #99354 Releases: main, 12.4 Signed-off-by:
Torben Hansen <derhansen@gmail.com> Change-Id: If18d3b4cd1a76008f56f5433e8ff5d591898d2ad Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79824 Reviewed-by:
-
Oliver Bartsch authored
In case a user did not pass necessary multi-factor authentication, this is handled as a login failure. Therefore, a webhook is now triggered for this scenario, like done for login failures of the first factor (usually username / password), providing basic information about the user and the used MFA provider. Resolves: #101263 Related: #100129 Releases: main, 12.4 Change-Id: I56b79a74d291beb94d78bb42305dcfba86ecaa26 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79825 Tested-by:
-
Benjamin Franzke authored
Resolves: #101265 Releases: main, 12.4 Change-Id: Ia4b6e5f9cb9c17394e3d72e18d9664ccbaf53f85 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79823 Tested-by:
-
Oliver Hader authored
Issue #39261 changed the behavior for processing nested tags. The iteration is adjusted and commented, to make clear what is actually happening there... (`$tagConfig` did not have a meaning). Resolves: #92194 Releases: main, 12.4 Change-Id: I94ddc683bbd1241330cde0d44cb7339afa75da56 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79806 Tested-by:
-
Oliver Bartsch authored
In case a user has MFA enabled, the same handling is now done as for users, not having MFA enabled. This is e.g. dispatching the AfterUserLoggedInEvent. Resolves: #99864 Resolves: #100128 Releases: main, 12.4 Change-Id: I1df7a23e2b1a1ae09ac3b0217364478155af6bca Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79807 Tested-by:
-
Oliver Bartsch authored
Since #94345 it's possible to omit the "event" identifier when configuring an event listener, since the service can be resolved using reflection. This however did until now not work when using union types. This patch therefore adjusts the corresponding compiler pass, making it possible to use the same method for listing on multiple events. Resolves: #101264 Related: #94345 Releases: main, 12.4 Change-Id: I5668269104515811d3c916c832942ef532bdfa27 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79821 Tested-by:
-
Stefan Froemken authored
In case of activated STRICT_TRANS_TABLES, better known as strict_mode, the index_words record incl. metaphone can not be stored as a string is provided, but an int is expected. As various metaphone related methods in TYPO3 return a string we change the DB type of column metaphone to varchar. We set the length to 60 as it is the same we use in analyzeHeaderinfo(). Resolves: #99547 Releases: main, 12.4, 11.5 Change-Id: Ice4223f2169595b781ed8c3a7dd5dda3f50e8a1e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79817 Tested-by:
-
Annett Jähnichen authored
Currently, when selecting a level in the "View" menu, the complete page tree is loaded starting from the root page, because the link did not have an id of the currently selected page. The id is now passed as an argument. Resolves: #99885 Releases: main, 12.4 Change-Id: I45fe4abfdd68b5bce15ca9d7b540a2965de7fab4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79820 Tested-by:
-
Oliver Bartsch authored
By dispatching a new PSR-14 Event on a failed multi-factor authentication attempt, it's now possible to consider such failed attempts in the "send email on failed login" functionality. The improved log message does now also use the correct "action" and "error" types, which allows further functionality, such as the corresponding dashboard widget, to make use of those information. Resolves: #100129 Releases: main, 12.4 Change-Id: I52047bc45dba124f050aa31640444ce4af12c4df Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79816 Reviewed-by:
-
Andreas Fernandez authored
The FormEngine validation now accepts "00:00 01-01-1970" as an entered date, which evaluates to int 0. If string 0 is passed, the field is supposed to be empty. Previously, a too simple negation check was in place. In the long run, the whole date validation handling needs a major rewrite to not rely on timestamps anymore. Resolves: #101258 Releases: main, 12.4 Change-Id: I90a976088e01c23443369eff76f4c6401463715e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79819 Tested-by:
-
Susanne Moog authored
When previewing a translated page that is enabled which has a parent (default lang) page that is hidden, users got a 403 error, because the preview flag was not set (as the page itself was not hidden). Change the check to always check both the default language and the overlay for setting the preview flag. Resolves: #20873 Resolves: #92775 Releases: main, 12.4 Change-Id: I438e772ee34cdb018cf4701878c18684a2fa3e03 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79813 Reviewed-by:
-
Lukas Niestroj authored
Rephrase the error messages presented to the user after a failed attempt to create or update a version record in offline workspace without permissions. Further, disable all modification actions in the recordlist. Disabled buttons: edit, move, delete, copy, cut, new record, history. Resolves: #10551 Releases: main, 12.4 Change-Id: Ieada8032ca12b1b90b53ee700ed9a6ba55d55bd2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79815 Tested-by:
-
Stefan Bürk authored
This change add additional functional tests to ensure old import tag syntax works in PageTsConfig UserTsConfig, from row templates and global array registration. Resolves: #99868 Releases: main, 12.4 Change-Id: I8921242fb5af3b2b4acf2c60ed74ee31e2589783 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79814 Tested-by:
-
Imko Schumacher authored
The TCA processing temporary converts native datetime inputs to timestamps for some checks. The start of the unix epoch (1970-01-01 00:00) corresponds to the 0 timestamp. Conditionally checks interpreted that as false, resulting the value to be the default value. This fix also prevents empty date values from being set to MySQL-specific values (0000-00-00 00:00:00). Resolves: #92900 Releases: main, 12.4 Change-Id: I979d59f4abe3dd73117a9e135a74ae3036192d9b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79812 Tested-by:
-
Andreas Nedbal authored
This patch adds support for loading the base CKEditor 5 locales and importing them in the backend if requested. Because CKEditor doesn't ship a full set of locales, we needed to add an additional build step that assembles the locales of all plugins we have installed. Resolves: #100873 Releases: main, 12.4 Change-Id: I971bf3e55d006a4a378123e8723c1bb8d23b09d1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79777 Tested-by:
Andreas Nedbal <andy@pixelde.su> Tested-by:
-
Susanne Moog authored
The "show dialog" option is an option below the notification settings of each workspace and therefor only impacts the notification settings. A dialog will still appear, allowing the user to add a comment. The documentation now reflects this. Releases: main, 12.4, 11.5 Resolves: #101255 Resolves: #84629 Change-Id: I16b4d80cb454f77afe9fb0e8783920b41e3991ce Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79783 Reviewed-by:
-
Torben Hansen authored
With #99920 the HTTP referrer evaluation has been extended to not overwrite the evaluated HTTP referrer on failed logins. The fix however broke the HTTP referrer evaluation, when the login plugin is placed on a page which is configured as 403 error page. In this case, the page is called via sub-request and a possible available HTTP referrer from the initiating request is used as redirect url. This patch extends the HTTP referrer evaluation, so the URL of the initiating request is used as HTTP referrer variable, if the plugin is called via sub-request. This ensures, that the user is redirected to the URL which the 403 error handler intercepted. In order to do so, the `PageContentErrorHandler` is extended to pass the original request as request attribute `originalRequest` to the sub-request. Additionally, the evaluation of the referrer URL has been moved to `RedirectHandler` and all scenarios have been covered with tests. It has to be noted, that in TYPO3 11.5 the fix will only work, if the "Subrequest page errors" feature toggle is enabled. Resolves: #100715 Releases: main, 12.4, 11.5 Signed-off-by:
-
