- Aug 10, 2020
-
-
Daniel Siepmann authored
In case sqlite is used, the uid is not of type integer. Therefore it is explicitly casted before passing to strictly typed method call. Resolves: #91950 Releases: master, 10.4 Change-Id: I4d9f8e4e526f861fd06f08c90c21d8b25832cc26 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65222 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Daniel Haupt <mail@danielhaupt.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
-
Benni Mack authored
This change moves the language evaluation of a page record much earlier in the frontend process. Before: * Resolve the page (determineId) based on permissions, visibility etc. * get TypoScript from Cache * Find a translation of the page and determine the content language Now: * Resolve the page based on permissions, visibility etc * Find the translation of the page * Get TypoScript from Cache This is a breaking change, as the hooks within settingLanguage() are now called at a different time of the processing logic for a frontend request, however it solves an issue that you can now use localized values for TypoScript conditions. Resolves: #23736 Releases: master Change-Id: Ia2db0233ce6680ae1cbcddb81574a41fa6333abf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65044 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
Oliver Hader authored
The route configuration shown below using `ExtbaseEnhancer` is currently not evaluated anymore due to missing route variables in `routePath`. For this particular case in `ExtbaseEnhancer` the controller-action pair is implicitly defining variables. MyPlugin: type: Extbase extension: ... plugin: ... routes: - routePath: '/action' _controller: 'MyController::action' Resolves: #91880 Releases: master, 10.4, 9.5 Change-Id: Ib42f87c3c9f83acc7f2ceec4a93169d15777ed08 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65134 Tested-by:Markus Klein <markus.klein@typo3.org> Tested-by:
Marco Bresch <marco.bresch@starfinanz.de> Tested-by:
Georg Tiefenbrunn <georg.tiefenbrunn@gmail.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
Christian Kuhn authored
A missing restriction in PageRenderer->getSubpagesForPages() leads to the workspace preview of a page changed in a workspace to render both live and workspace versions as menu items in multi level menus. Adapt the query to fetch the correct combination of live and overlay records. Resolves: #91943 Related: #89555 Releases: master, 10.4 Change-Id: I924803fc2997a9a5c990bc4cf8a628113aae0b22 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65212 Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
-
- Aug 09, 2020
-
-
Andreas Fernandez authored
jQuery 3.5 has been released a while ago, it's safe to update to the current version. However, as 3.5.0 introduced some deprecations, it should be updated in master only. Executed commands: yarn add jquery@^3.5.1 grunt build Resolves: #91953 Releases: master Change-Id: Ife43bc2679549757dede58b0b1fa92df9bce6d7f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65224 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
- Aug 08, 2020
-
-
Andreas Fernandez authored
The event listener registration for AjaxDataHandler events is faulty which causes event stacking when a workspace gets deleted. The registration now happens at a central place to solve this issue. Resolves: #91955 Related: #91948 Releases: master Change-Id: Ifafd8171ce3da20883e39c43d8300f92366866b6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65227 Tested-by:
-
Andreas Fernandez authored
This patch fixed a long existing issue regarding workspaces. If a workspace is either created, updated or deleted, the topbar menu gets reloaded to update the workspace menu now. Resolves: #91948 Releases: master, 10.4 Change-Id: I316994c209d3bebc0e72e8e7ad956c5cf30502c9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65221 Reviewed-by:
Claus Due <claus@phpmind.net> Reviewed-by:
-
Andreas Fernandez authored
Events sent via AjaxDataHandler are now broadcasted by using the Broadcast Service. This change allows e.g. the topbar to listen to these events and trigger a reload. Broadcasting has the nice side effect that the event is sent to all browser windows which allows multiple simultaneously opened backends (that share the same domain) to react on that event. To ease the integration of event listeners, the event payload sent via classic `dispatchEvent()` is adjusted to share the same structure with broadcasted messages. Resolves: #91947 Releases: master, 10.4 Change-Id: I04321f9ab3db309972890e037a1d3790d9b06f79 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65220 Tested-by:
-
Andreas Fernandez authored
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:
-
- Aug 07, 2020
-
-
Benni Mack authored
This reverts commit fb61db41 as it contained various regressions, which should be fixed in the next iteration. Change-Id: I03b6ff9e63a1425fae3745f70bbd9b8a2a94c081 Releases: master, 10.4, 9.5 Resolves: #91949 Reverts: #88943 Reverts: #88098 Reverts: #88259 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65200 Tested-by:
Frank Nägler <frank.naegler@typo3.org> Tested-by:
-
Benni Mack authored
Classes without any special Extbase treatment (e.g. no injection) are migrated to GeneralUtility. This saves a bit performance, because ObjectManager in turn would call GeneralUtility as well for these classes. Areas in Extbase are not touched, as they will be migrated separately. Resolves: #91937 Releases: master, 10.4 Change-Id: I899af0d377f9d710621e2775f8a7f51887d130d4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65189 Reviewed-by:
-
Oliver Hader authored
New `SecurityUtility. getRandomHexValue(20)` returns 20 hexadecimal characters provided by the Web Crypto API. see https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API Resolves: #91809 Releases: master, 10.4 Change-Id: Iaee1c7641b34e1316fccd069808c519d1c3ba2ab Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65046 Tested-by:
-
Christian Kuhn authored
The clipboard has a 'move' and a 'copy' mode. This can be changed in the list module where the clipboard is rendered. Using 'cut' in context menu, the state is forced to 'move', using 'copy' in context menu, the state is forced to 'copy'. If there is an element in the clipboard, 'paste' icons in list and page module appear. Their title tag is always 'paste' or 'paste after' or similar. Only the modal in page module distinguishes between copy and paste and changes its wording 'Do you really want to move' vs. 'Do you really want to copy', while the modal title is always 'paste'. This is odd from an UX point of view: Users learned they either 'cut + paste' or 'copy + paste': The decision to cut or paste is the first step when selecting the element, it's then either cut-out and moved to clipboard, or a copy in the clipboard is added. The second step is then just 'paste here'. The patch changes the modal wording to always use 'paste' as second step, just like the icons already do. Resolves: #83566 Releases: master, 10.4 Change-Id: Ia7b4296bbcee1d21b2be0d0ddb9e1019c93e9b4a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65190 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
-
- Aug 06, 2020
-
-
Benni Mack authored
Previously, when using the "Split Preview" for comparing a workspace version, and a live workspace, in iframes, the workspace version received the GET Parameter "&ADMCMD_prev=1", and the live workspace the "ADMCMD_noBeUser=1" (= no backend user is logged in) for THESE requests. Navigating through the live workspace, the ADMCMD_* GET parameters are lost in both variants. This change replaces the ADMCMD_noBeUser=1 with ADMCMD_prev=LIVE making the options consistent naming-wise. In addition, when ADMCMD_prev=LIVE is set, the current BE_USER is kept but the workspace is set to "0" temporary (for this request), allowing for e.g. the admin panel to continue to work. When ADMCMD_prev=LIVE or ADMCMD_prev=IGNORE is set, the parameter is added to config.linkVars, allowing to keep using the ADMCMD_prev when browsing through the workspace and live versions in the iframes. Resolves: #34199 Releases: master, 10.4 Change-Id: Ifa732d56af1af1d6f01f00b6b4c035b6fdbc02ce Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65213 Tested-by:
-
Andreas Fernandez authored
This patch changes the behavior how workspaces are switched via the topbar menu. The switch now happens by explicitly requesting the workspace module with a new set `workspace` parameter. Previously, it was tried to reload the content iframe which may has a `workspace` parameter already set, resulting in simply reloading the previously requested iframe. Resolves: #91946 Releases: master, 10.4 Change-Id: I3e3dac98c5a12c3329ed5fc948c10bd36ef2d8d8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65218 Tested-by:
-
Benni Mack authored
In order to ensure that the root page ID is always pointing to the live version, the SQL query is adapted to never include versioned records by ensuring to only include live workspace records in the SQL query for pages. Resolves: #72567 Releases: master, 10.4 Change-Id: I47f16d9ea2a65c70d732283b6b807b0fdc19e371 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65191 Tested-by:
-
Benni Mack authored
This change uses a "random" frontend user ID (currently 1337) to a very unlikely number PHP_INT_MAX to ensure that no usual frontend user is used to preview. This line can be removed completely once https://review.typo3.org/c/Packages/TYPO3.CMS/+/64441 is fixed as well. But 1337 is a no-go (that's why it needs to into 9.5) Resolves: #91837 Related: #90773 Releases: master, 10.4, 9.5 Change-Id: I70eebcf1220b216b3a9929a7b31eb83e999f282a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65215 Tested-by:
-
Christian Kuhn authored
Fixes an obvious PHP notice level error thrown in casual requests multiple times. Resolves: #91945 Releases: master, 10.4 Change-Id: I7d21c0e67ac680443cc0892bfa15ddd45c724b22 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65217 Reviewed-by:
Daniel Siepmann <coding@daniel-siepmann.de> Reviewed-by:
-
Christian Kuhn authored
A last partial usage has been dropped during 6.2 times but the file has never been removed. Do that now to avoid further developer confusion. Resolves: #91944 Related: #49689 Releases: master, 10.4 Change-Id: I784eaa7cbcf32776db1c0b21ef4ca45cd5c08f2b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65216 Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
-
Helmut Hummel authored
Only try to fetch translated uids for translated records, and provide is_siteroot field for slug helper, so that it can be checked if slug is generated for a site root. Resolves: #90736 Resolves: #89485 Releases: master, 10.4, 9.5 Change-Id: I707e5a1df2d06a81eea2dd491302b003d086e42a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65116 Tested-by:
Stefan Froemken <froemken@gmail.com> Tested-by:
-
Christian Kuhn authored
Another 'broken since ever' fix: Sorting a record in workspaces by moving it 'after itself', the record vanishes from the interface. While this action is kinda useless, it can for instance accidently happen by an editor. As with other move operations in workspaces, a move placeholder and the versioned data record is created. In case of inserting after itself, the move placeholder state is not correctly updated - both pid and sorting values end up with 0. The records then no longer belong to the correct pid and are not 'seen' by workspaces. The patch fixes this case by making sure the pid and sorting determination of the move placeholder does not accidently operate on itself as reference record. A series of functional DataHandler tests nail the correct state for pages and tt_content in non-workspace and workspace scenarios. Resolves: #53619 Releases: master, 10.4 Change-Id: I39b5e9f72bd05645dcd429bed3833d2a792efaec Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65188 Tested-by:
-
Christian Kuhn authored
The row selection of records in JavaScript is not reset after execution of a publish action in the workspace module. If an editor tries to publish or disard another set of records without reloading the module, the already handled records from the first action are send again in the request payload, leading to server side exceptions. Resolves: #89927 Releases: master, 10.4 Change-Id: I8800c1df34fd749d84e63ea3e42c7b83513e1a38 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65185 Tested-by:
-
- Aug 05, 2020
-
-
Markus Klein authored
Use the proper check to avoid adding JS libs more than once. Resolves: #91653 Releases: master Change-Id: I3b750e6b2341681b45a722ae8ecfacb1d17243da Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64897 Reviewed-by:
-
- Aug 04, 2020
-
-
Jigal van Hemert authored
The variable $crazyRecursionLimiter actually limits the number of subpages that are rendered for each page and not the depth of recursive calls to getTree(). This limit only affects the browsable pagetree in for example the link browser and not the pagetree in the navigation pane. Resolves: #91853 Releases: master, 10.4, 9.5 Change-Id: Ib2ff5471226217bc880ddee3b278771393a09354 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65083 Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
-
Benni Mack authored
PropertyMapper (which is a singleton) previously created a new $messages instance every time "convert" was called. This works for most cases, however when using "getMessages()" only the last message was returned. It would be very useful to keep the messages in place until "resetMessages()" is called, which is used within each action of the Extbase controller validation to avoid some edge-case issues when using multiple actions on one request. Resolves: #70872 Releases: master Change-Id: I2fddc4261567cad2ebb12f91296ff3ec8d681ad8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65114 Tested-by:
-
Benni Mack authored
When fetching a frontenduser from the database, the constuctor is not called, but initializeObject is called. For this reason, the initialization of the FrontendUser happens on initializeObject() as well. Resolves: #83386 Releases: master, 10.4 Change-Id: I72e39b6485a4a072b7b94f96f947151222d68089 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65177 Tested-by:
-
Stephan Großberndt authored
This patch adds the directory `typo3conf/sites/` and for composer based installs `config/sites/` to the directory status check in the install tool. Resolves: #91488 Releases: master, 10.4 Change-Id: I059c92d7ec2d740ba3f7d3c5d81181cadc146681 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64577 Tested-by:
-
Benni Mack authored
When deleting a page with records an editor does not have access to, the error message "Attempt to delete records from disallowed tables" is shown which does not give a hint to the editor what tables are an issue. This change improves the error message to show the tables that are prohibited. Resolves: #55307 Releases: master, 10.4 Change-Id: Ibe451e7042b9832815e2d4a26104e06adc94656d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65175 Tested-by:
-
Kevin Ditscheid authored
Prevents a non-numeric value warning in ErrorHandler.php by casting the value given to the parameter of the constructor to an int. Resolves: #91930 Releases: master, 10.4, 9.5 Change-Id: I000596ee0bdf8599a2eadea5216286971a94c806 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65182 Reviewed-by:
-
Kevin Ditscheid authored
This commit prevents a warning regarding a non-numeric value in the phpErrorCode argument of the PhpErrorCodeViewHelper. TYPO3 Fluid is actually not converting the value to int, and there could be anything incoming as parameter. Resolves: #91929 Releases: master, 10.4, 9.5 Change-Id: I3514004829f97849b9fb6f16b07f9ffb53679f87 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65181 Reviewed-by:
-
Martin Bless authored
Update Settings.cfg to current standards. Releases: master Resolves: #91765 Change-Id: I868f4823ff4d5dbb837e209e71836cbf1b77af4f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65004 Tested-by:
-
Benni Mack authored
The sys_template.sitetitle field has been deprecated in v10 and is superseded by title handling of site configuration. The patch removes handling and db field. Resolves: #91927 Related: #91473 Releases: master Change-Id: I14f034193a31b7fdb0c37aeca9a485060843cefc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64618 Tested-by:
-
Markus Klein authored
The core version check is run synchronously while logging into the Backend. If the get.typo3.org service is down, logins take extremely long. Since there is no API to run this check asynchronously, the patch drops this information from the toolbar, it is only available in the reports module. Resolves: #91507 Related: #84549 Releases: master, 10.4, 9.5 Change-Id: I78fd381df1aff6a40cc9bd57ac5a4babed2ec999 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64904 Tested-by:
-
Jan Delius authored
This patch correctly applies the already configured and documented sender address for the recovery email. Resolves: #91923 Releases: master, 10.4 Change-Id: I48f6959bbca7ae9d9572a48b8948de2de8d0550c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65176 Tested-by:
Jan Delius <me@jandelius.eu> Tested-by:
falcop <falco.preusche@live.de> Tested-by:
Rico Drexler <rico.drexler@gmx.de> Reviewed-by:
-
Christian Kuhn authored
composer require --dev typo3/testing-framework ^6.3.3 Mostly brings a bugfix of the functional test splitter, relevant for bamboo but relevant and v10, and a deprecation removal preparation for master. Change-Id: I0de875483ba0997f91071242b4d4aa5f9c1398e6 Resolves: #91926 Releases: master, 10.4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65179 Tested-by:
-
- Aug 03, 2020
-
-
Benni Mack authored
The information in the sys_file_storage record created automatically should not be persisted as "auto-created" as 90% of the people do not modify this, and it is only confusing to see this information in the filelist without having a good and explained way to change this. Instead "fileadmin" (taken from $GLOBALS['TYPO3_CONF_VARS']['BE']['fileadminDir']) is used when creating the default storage. This was originally added by myself when introducing FAL in 6.0, and never touched, however feedback from newcomers shows that this should be adapted. Resolves: #91921 Releases: master Change-Id: I675ef7818aa6a83191574131f54c1c2b6f490e41 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65151 Tested-by:
-
Benni Mack authored
The information in the dropdown of the page module "Make new translation of this page" is not very common across native-english speakers, instead the label should be called "Create a new translation of this page". Resolves: #91922 Releases: master, 10.4 Change-Id: Ifa27090741d73ba363e112a8d5f5cdaa23638bcf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65172 Tested-by:
-
Benni Mack authored
The patch drops handling and existence of two further workspaces related db fields: * t3ver_tstamp has been occassionally set to 'now' when records in a workspaces were edited. However, the field was never displayed in the backend and is of little use since it only holds only a 'last' value. A change history on workspace records is available through the 'info' button in the workspace module. This is powered by sys_history and shows modifications with date/time. * t3ver_count is also never rendered in the backend. It has been used in the (non-default) 'swap' workspace actions where live records become the new workspace records. The field was then incremented by one. The loose wording around that is, it's an 'archived' record. However, if swapping a second time, the workspace record does not count two as one would expect, but still one. Only after another swap, the workspace record would have the value two in this field. Together with the fact this field has never been shown/used, the weird behavior, and that swapping is an uncommon case that needs to be explicitely enabled and used, the field is dropped now. Resolves: #89137 Releases: master Change-Id: I7cdfe6e867c14462395d7398123b14464835c1bf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65145 Tested-by:
-
Benni Mack authored
A new TER Extension "legacy_collections" has been added to FriendsOfTYPO3 which contains DB tables and TCA definitions for "sys_collection" and its MM relation table. The functionality was originally intended with the introduction of taxonomy and FAL File relations (which are stored in sys_file_collection) to be used as a generic TCA store for collections, which was never picked up in the past 8 years. A personal survey of several installations showed that almost none of the TYPO3 instances have the database tables filled, making this unneeded code and database code, for only a handful of people. Instead of providing the database tables by default in all installations, the database tables and their TCA definitions are now available in a separate extension "legacy_collections", which serves as a drop-in replacement for everybody who needs this API and the database tables. An update wizard checks if the sys_collection database table is filled, and allows to install this extension. The new extension is compatible with TYPO3 v10, so it should ease the migration path. Resolves: #91909 Releases: master Change-Id: I85d53cc7969f9f9ce93311dd483be31735bf8c05 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65147 Tested-by:
-
Anja Leichsenring authored
Language handling always bases on the existence of a page version for the requested language. If this is not available, handling follows fallback settings. Functional Tests that test for translated content to be returned as expected must provide such a translated page on their own, else the fallback handling kicks in, renders the test falsly reassuring. Resolves: #91905 Releases: master, 10.4, 9.5 Change-Id: I77d1e096cd0e62134ffd818f8bd32667e566d44a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65146 Tested-by:
-
