- 04 Jun, 2020 2 commits
-
-
This fixes encoding issues in paths with URL-encoded spaces and other characters when indexed_search translates indexable file URLs into local paths. Resolves: #91586 Releases: master, 10.4, 9.5 Change-Id: Id20034137556f5705ee34b3adcca6250c77d83f2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64792 Tested-by:
Jonas Eberle <flightvision@googlemail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Jonas Eberle <flightvision@googlemail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
Common URLs like typo3.org, tools.ietf.org or php.net are nowadays available as HTTPS, however some places in TYPO3 still use http:// as reference. This should be streamlined to resemble https:// everywhere. Resolves: #91581 Releases: master, 10.4 Change-Id: I76b5211f7e14cab0c6d190059d2be761bc664b53 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64752 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 03 Jun, 2020 4 commits
-
-
Filter out pages user has no access to on query time in page tree. This patch reintroduce a change which was reverted with https://review.typo3.org/c/Packages/TYPO3.CMS/+/64369 Resolves: #91221 Related: #90880 Related: #91348 Releases: master, 10.4, 9.5 Change-Id: Id90752c331bc6fc12b0d3a7d047adacf08cb7804 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64639 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
Richard Haeser <richard@maxserv.com>
-
The plugin configuration of felogin is moved to the common used "Plugin" tab, to unify the position through the core. Resolves: #91416 Releases: master, 10.4 Change-Id: Ibbf26be6787795021e7ba6a0d3138bbf18121087 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64638 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
It is possible for values returned by stdWrap to be of type int. RequestHandler->generateMetaTagHtml() expects meta tag values to be of type string. In order to avoid php errors, return values are now casted to strings. Resolves: #91533 Releases: master, 10.4, 9.5 Change-Id: I642d5fe0189955e26689a6cf65cdbe23255356a2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64636 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
PageRepository->fixVersioningPid() needs "t3ver_wsid" and "t3ver_oid" to resolve a version, otherwise previewing in workspace context takes another SQL query per page slug candidate. Resolves: #91556 Releases: master, 10.4, 9.5 Change-Id: Ie95365fe76cd2e6e502324c5dbe145651795cff1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64635 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 02 Jun, 2020 4 commits
-
-
Benni Mack authored
In change https://git.typo3.org/Packages/TYPO3.CMS.git/commit/e6e40cd214acc8581729ef9f6e98c5d9324ec11c of bugfix #90656 the title attribute of the result was changed to always be added, which should only be added when the title is not empty. Resolves: #91506 Related: #90656 Releases: master, 10.4 Change-Id: Ie267f89b5ae82daeb036c820391099f06bfccbaf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64634 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
All code that is using the constant TYPO3_MODE is hard to test, as this needs to be encapsulated into various places. All testing framework places run with TYPO3_MODE=FE which makes it impossible to even consider making parts of the testing framework compatible running a pure Frontend-based request in the future. On top, the constant covers up cross-dependency between core dependencies (whereas $GLOBALS[TSFE]->fe_user is actually a dependency to EXT:frontend). Another testing-helper in Extbase's EnvironmentService allows to switch within Extbase to simulate Frontend behaviour. Resolves: #91521 Releases: master, 10.4 Change-Id: I85a34029e399b40d0780f907480f9059bfdb0edb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64633 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
The acceptance tests folder 'InstallTool' holds tests that ensure the proper display of options in the stand alone Install Tool. A brand new test suite takes care of execution. Resolves: #89489 Releases: master, 10.4 Change-Id: Iaeedfd5a2db26d4ba111855dc3137f2e8ca8fa27 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64547 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
Scalar values sent via HTTP query parameters to FileSystemNavigationFrameController are using `json_encode` instead of `unserialize`. The parameter stream is still secured with an HMAC before being deserialized. Resolves: #91548 Releases: master, 10.4, 9.5 Change-Id: I57be68aac1787bdc27f2bbae40f8d71b1b33f79f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64625 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <noreply@typo3.com> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 01 Jun, 2020 1 commit
-
-
When a live record that is hidden, but gets unhidden in a workspace version, the record should also be resolved within move placeholder resolving. Resolves: #88054 Releases: master, 10.4, 9.5 Change-Id: Ia5396c6d0cc6b6a915ac8af21008ff5c592c1fe1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64632 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Frank Nägler <frank.naegler@typo3.org> Reviewed-by:
Frank Nägler <frank.naegler@typo3.org>
-
- 31 May, 2020 2 commits
-
-
This change aims to reduce the amount of inline JavaScript by removing `onchange` or `onclick` events and dynamically created JavaScript code/settings. * moves inline JavaScript for avatar handling to new SetupModule * avoids using configuration options `onClick`, `onClickLabels` and `confirmData.jsCodeAfterOk` which contain inline JavaScript * introduces configuration options `conformationData.eventName` and `clickData.eventName` to substitute mentioned deprecations * adds PSR-14 `AddJavaScriptModulesEvent` which allows to apply custom RequireJS modules to handle mentioned new custom events Resolves: #91132 Releases: master, 10.4 Change-Id: Ia68d0c473db862e0381671604347bd15ec89be35 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64627 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
eot, otf and ttf font formats were used to support very old browsers like <= IE8. Since TYPO3 v10 does only support modern browsers, these formats can be safely removed. Used commands: >yarn remove npm-font-source-sans-pro >yarn add source-sans-pro >grunt build Resolves: #90904 Releases: master, 10.4 Change-Id: I0676bcdb2bc70454f73027e8e216bb889c419a57 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64551 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 30 May, 2020 2 commits
-
-
This patch rephrases the notifications rendered in the Admin Tools. Some notifications now contain a better description of their respective meaning or what the consequences of certain actions are. Additionally, useless rendering of notifications that are never available in some responses have been removed. Resolves: #91461 Releases: master, 10.4 Change-Id: I94be58c4ecba2f7c0639866aef830168d2459dba Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64550 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Scalar values sent via HTTP query parameters to ShowImageController are using `json_encode` instead of `unserialize`. The parameter stream is still secured with an HMAC before being deserialized. Resolves: #91509 Releases: master, 10.4, 9.5 Change-Id: I81b8d5a10a79536592b105c838470238e14b7dca Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64608 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
- 29 May, 2020 2 commits
-
-
Resolves: #91510 Releases: master, 10.4, 9.5 Change-Id: I5bfda8310342718dc696b182fd87b1954a6cdc39 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64549 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
Resolves: #91501 Releases: master, 10.4, 9.5 Change-Id: I7b77a3ee8aceac2cbdb6f3d4e0a02930b66eb863 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64546 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 26 May, 2020 1 commit
-
-
In order to avoid accidentally committing a FIRST_INSTALL for developers starting to contribute to TYPO3 Core and using Core git repository for its basis local development setup, the FIRST_INSTALL file is ignored from git. Resolves: #91119 Releases: master, 10.4, 9.5 Change-Id: Iad459240bbc8a68892f03adf547373bc608f6a90 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64544 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 25 May, 2020 4 commits
-
-
Resolves: #91472 Releases: 10.4 Change-Id: I1a28d8a1f3d42bcc4e6fbbf0c328cd712927bb72 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64576 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
Resolves: #91471 Releases: master, 10.4, 9.5 Change-Id: Ib008a46cc2edb368fed3fc937858f1f3870938b5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64542 Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Tymoteusz Motylewski authored
Also fix misleading comment about permissions. Resolves: #91454 Releases: 9.5, master Change-Id: I1a399f1be613f007440bf542441bee60f53e49e0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64557 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Richard Haeser <richard@maxserv.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com>
-
Deleting an extension in Extension Manager doesn't make much sense in a Composer-based installation. For this reason, the removal of extensions is prohibited now. Resolves: #91456 Releases: master, 9.5 Change-Id: Ia96cf2741fd749d9f50540366351c8b576cac96b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64568 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Mathias Brodala <mbrodala@pagemachine.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
- 22 May, 2020 8 commits
-
-
The PSR-14 event "AfterFileCopiedEvent" in FAL now also has the possibility to return the newly created file and the identifier. Resolves: #91373 Releases: master Change-Id: I08a01a0424e37fe2f010d2894d41a14628bdc950 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64478 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Susanne Moog <look@susi.dev>
-
If the TypoScript variable `plugin.tx_felogin_pi1.replyTo` was set to an email address, it triggered the following error: `Symfony\\Component\\Mime\\Exception\\InvalidArgumentException: An address can be an instance of Address or a string (\"array\") given)` Releases: master Resolves: #91458 Change-Id: I4179d42025d0373cd1d7c0938a83ec0c90e25465 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64559 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Git converts CRLF to LF when plaintext files are staged. The existing copies of the rte_ckeditor Contrib/* sources have therefore already been converted to LF by git [1]. Initially these files had been copied as CRLF from the ckeditor4 sources in node_modules by grunt npmcopy. Now, when `yarn build` is executed, the copy operation is performed again, which means the files are reverted back to CRLF. Git therefore needs to perform the CRLF to LF conversion again. (Which itself needs to be triggered by the developer by staging the changed files) We do now mimic git`s autocrlf behaviour and replace CRLF by LF in the files copied from ckeditor Contrib/* folders to prevent the files from clobbering the `git status` or `git diff` output. By passing `encoding: null` to the grunt.file.copy options we ensure that binary files will be copied as is. Also configure *.svg files to be checked out as LF on all platforms (namely windows) like we do for other plaintext files as well. This ensures svg files do not show up (in windows) as changed because their original from node_modules was stored as LF. *.patch is added as patching jquery on windows would fail otherwise. [1] https://git-scm.com/docs/gitattributes#_end_of_line_conversion Resolves: #91374 Releases: master, 9.5 Change-Id: I2977a6d44f96f6593152bfe698ba5d35f32b131f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64481 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Susanne Moog <look@susi.dev>
-
The point of repeatable update wizards is that they are not marked executed and thus always checked for possible updates. They therefore must not be marked executed during installation. Resolves: #91211 Releases: master, 9.5 Change-Id: Ic4e98b95711433705f77899d664cc7cf2c7a42ba Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64326 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Susanne Moog <look@susi.dev> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
TYPO3com <noreply@typo3.com>
-
Activating "showHiddenFilesAndFolders" in BE User settings shows hidden files and folders also when navigating through the files in filelist module. Resolves: #91309 Releases: master, 9.5 Change-Id: I8f04b43a2cc0df93b6e77290caed2b33c6951e44 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64424 Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Reviewed-by:
Susanne Moog <look@susi.dev>
-
Resolves: #91457 Releases: master Change-Id: I29009a9498b050942e34a27815acdf996e6f0539 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64558 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
Resolves: #91459 Relates: #91302 Releases: master Change-Id: Ic4af3247d7557a6c12a8d538e85795c507eab69a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64561 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
With the removal of `selicon_field_path` in #87937 also the automatic record type icon mapping was removed. As a result the record icon of a select item based on `foreign_table` is not resolved anymore. In addition, the `selectIcons` list is therefore no longer displayed. The previous functionality is now restored. Resolves: #91302 Relates: #87937 Releases: master Change-Id: If62f4ba65ef54ec2345131f6c117ce4336e76c4c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64560 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
- 21 May, 2020 3 commits
-
-
To highlight difference between BackendUtility::BEgetRootLine() and RootlineUtility->get() Resolves: #91455 Releases: 9.5, master Change-Id: I63d7ca395d5a052d29d718316474b69d6519ebc9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64554 Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Richard Haeser <richard@maxserv.com>
-
Resolves: #91345 Releases: master Change-Id: I54ab67e85b3bf24b06916b674765ed22fb5de76c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64508 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
If an action in the Install Tool is executed that is related to an inline module or an interactable module (a.k.a "modal"), its trigger button(s) get now properly disabled and enabled to avoid executing the same actions consecutively while any request is still pending. Resolves: #91076 Releases: master Change-Id: I9a61063819f21a33ac8ede644fa8f998212b342b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64207 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Jonas Eberle <flightvision@googlemail.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Susanne Moog <look@susi.dev>
-
- 20 May, 2020 3 commits
-
-
When initializing the configuration for a cache any existing configuration under its old name (cache_ prefixed) is applied as an additive override now. This ensures that basic configuration like groups are preserved and not removed with the formerly correct way to adjust cache-config. Resolves: #91306 Releases: master Change-Id: Ic862f80263f410688d2dffb7c13948c1c40488a3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64407 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Johannes Kasberger <johannes.kasberger@reelworx.at> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Johannes Kasberger <johannes.kasberger@reelworx.at> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
Benni Mack authored
The documentation for lowlevel commands are optimized so they make more sense: * Nightly checks are run with a --dry-run command * cleanup:versions info is removed (the command is gone) * Checks have a --dry-run command Resolves: #88874 Releases: master, 9.5 Change-Id: If82ab67f7aec48c1b533e84d70ecdadc94e528bd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64530 Reviewed-by:
Tobias Gaertner <tobias.gaertner@benaja-websolutions.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Benni Mack <benni@typo3.org>
-
Helmut Hummel authored
Set the current page id early, so that PageTS is fetched from the correct page instead of id 0. Releases: 9.5, master Resolves: #91445 Change-Id: I95a50b6c9d45be54291f27828d9f35cb62b3b4dd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64553 Reviewed-by:
Daniel Siepmann <coding@daniel-siepmann.de> Reviewed-by: Thomas Hohn Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Helmut Hummel <typo3@helhum.io>
-
- 19 May, 2020 4 commits
-
-
Change-Id: I22eb57766cd6ddd8aa31447ccd374e52920c2010 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64529 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
Change-Id: Ifd8e3cc62c5b0a27b0bc938e5dbc8cb136a1d07c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64528 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
When saving a record on a page that is not part of a site, the slug field of this record, despite being set to "uniqueInSite" is not checked for uniqueness, as it is assumed unique enough. This assumption needs to be applied as well when resolving the record, instead of assuming the resolved record is not part of the current site. Releases: master, 9.5 Resolves: #91438 Change-Id: I347909b9b4caa523de3ad8e5d84c465e5d57b052 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64520 Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org>
-
Re-added `$this->where_groupAccess` to init method. Resolves: #91429 Releases: master, 9.5 Change-Id: Ibd9b169e8d11e358023d8cfbd2085995769d16cc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64516 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-