- Feb 19, 2020
-
-
With Feature #90052 the parsed YAML configuration can be viewed in the Configuration module. A tip is already available on the top of the page. The hint about manual debugging is therefore obsolete and can be removed. Resolves: #90432 Related: #90052 Releases: master Change-Id: Iff3e1ae0e15a30e679e8ca29fb5e54714d21f925 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63320 Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Siepmann <coding@daniel-siepmann.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Siepmann <coding@daniel-siepmann.de>
-
Georg Ringer authored
The options "SEO" and "Social Media" are added to the Pagetree Overview. Releases: master Resolves: #90425 Change-Id: Iaee3e15bf2699e349b02cb7950c2df3e9db0952a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/59773 Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Christian Eßl <indy.essl@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Christian Eßl <indy.essl@gmail.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Alexander Schnitzler authored
Bleeding edge configuration may be useful to use but shouldn't be enabled by default. To make the inclusion convenient, the include has only be commented and not be removed at all. Releases: master Resolves: #90403 Change-Id: I9a8dfdef29947df890db92d331f1b4b27d13b736 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63277 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Benni Mack authored
Due to site handling the TypoScript option content_from_pid_allowOutsideDomain is not needed anymore, and can be removed, as it does not have any effect on the result. This was domain-specific in combination with sys_domain and ?id=123. Resolves: #90371 Releases: master Change-Id: I90d6089af2461d4f605e7ff6778ccf36e008c537 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63238 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Christian Eßl authored
In the RecordHistory Rollback template it can happen, that the historyRow is missing messages about its differences. In this case, an empty div with a weird looking border would still be visible in the html. This patch fixes this by wrapping an if condition around the div, that checks first, if the needed information is available. Resolves: #90424 Releases: master, 9.5 Change-Id: Icdd5dbf1b1008ab6a64a2b241982450bd385a8f8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63314 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
- Feb 18, 2020
-
-
Christian Eßl authored
The fields no_follow and no_index were inverted some time ago, but still retained their previous non-inverted labels in TCA. These were not actually shown when editing a page, but could be read in by other parts of the backend. This lead to misleading labels in both the "Display information" window as well as the "Info -> Pagetree Overview" module. Resolves: #88812 Releases: master, 9.5 Change-Id: Ie1bddeae20f0ffb3958bb07dab78d68dc68eff74 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63312 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
Since TYPO3 v7, the new ModuleTemplate API is in place, which contains a fluid-based and fluent interface possibility to add DocHeader components and to render content. Resolves: #90421 Releases: master Change-Id: I5634ea0427486f37fbbfe3ee00695fc98e52d980 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63290 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
Benni Mack authored
When rendering custom formats with the <source> tag (as an example), it currently is not possible to specificy a target file extension (e.g. webp as alternative). A new argument "fileExtension" for the <f:image>, <f:media> and <f:uri.media> is introduced to specify a custom output format for having variants on image variants. Resolves: #90416 Releases: master Change-Id: I5fe2a60b968578e504cda851d2d5dd0f0eefe7e0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63289 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
Georg Ringer authored
As the templates for the FluidEmails are located in EXT:install, the configuration needs to be adopted. Resolves: #90345 Releases: master Change-Id: Ie4b7ea05090b6e77c3cfa4f9714b0a41cc0d57a6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63182 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Stefan Froemken <froemken@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Stefan Froemken <froemken@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
Several ADMCMD_ and TSFE_ADMIN_PANEL variables are excluded from cHash, but were never evaluated before. The GET parameters are removed from setting and calculation in cacheHash. Resolves: #90412 Releases: master Change-Id: I4c6781fca4fd6ccc50bd068f266619b2a2a0cf15 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63236 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
Benni Mack authored
Sending out emails when items have been processed on a stage change is now done via Fluid Email, allowing administrators to fully customize both subject and body of an email. All emails sent by default contain more information and better structured contents instead of marker-based templates. The following TSconfig options apply to customize the emails: - tx_workspaces.emails.stageChangeNotification.generatePreviewLink = 0 - tx_workspaces.emails.layoutRootPaths - tx_workspaces.emails.partialRootPaths - tx_workspaces.emails.templateRootPaths - tx_workspaces.emails.format = html (or "text" or "both") Resolves: #90411 Releases: master Change-Id: I837c1538230ed55f2e34d51288e3b943fdd65238 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63248 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
Christian Eßl authored
If a HMAC of a submitted form is invalid (because it has been tampered with), TYPO3 would previously throw an exception that leads to a status code 500. This is incorrect behaviour, as the error comes from bad user input and not a server error. In case the HMAC of a submitted form is invalid, both extbase and ext:form will now throw a BadRequestException, which will then lead to a status code 400 (BAD REQUEST). Resolves: #90134 Releases: master, 9.5 Change-Id: If4dad7ba27190b5992bab68b4ce64a423c0db645 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63272 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Reviewed...
-
- Feb 17, 2020
-
-
Chris Müller authored
When creating a new IRRE child element the uid of the parent element was not set. This is a problem when you use an itemsProcFunc for a select column which relies on the parent's element uid to show according values. With the parent uid you can query the stored values. Resolves: #63777 Releases: master, 9.5 Change-Id: I898de29020bf68e25de9ef1d80cc20353a635524 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61480 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Tobi Kretschmann <tobi@tobishome.de> Reviewed-by:
Henning Liebe <h.liebe@neusta.de> Reviewed-by:
Sascha Rademacher <sascha.rademacher+typo3@gmail.com> Reviewed-by:
Felix P. <f.pachowsky@neusta.de> Reviewed-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Nikita Hovratov authored
This patch: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62227 introduced decoding of attribute values in tags. This was necessary for email link parameter, but broke html inside attribute tags, because quotes were left unescaped. Resolves: #90339 Releases: master, 9.5 Change-Id: I3c336901df6e3ee5eeea46888db11c40986ced56 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63274 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Richard Haeser <richard@maxserv.com>
-
Manuel Selbach authored
With this change, the DocumentTypeExclusionRestrictionTest will use NOT IN instead of <>. This will allow to have only one instance of that restriction. Additionally multiple casts to integer have been removed. Resolves: #87938 Releases: master, 9.5 Change-Id: I3c1c5cc47800dae3f13afc654f55236634ad5bc5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60275 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Dennis Prinse <dennis@dennisprinse.com> Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
Dennis Prinse <dennis@dennisprinse.com> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Claus Due <claus@phpmind.net> Reviewed-by:
Richard Haeser <richard@maxserv.com>
-
Nicole Cordes authored
For PersistedAliasMapper and PersistedPatternMapper, language handling when resolving a URL route paramter was not explicit enough. PersistedAliasMapper incorrectly resolved language default records even when the HTTP request contained a language aspect and a more specific record (having the same slug value) would have been available. That was similar in PersistedPatternMapper when `uid` field was not defined in corresponding pattern (e.g. `^(?P<title>.+)-(?P<uid>\d+)$). For both mentioned scenarios language restrictions and fallback handling has been integrated. Records are retrieved in the following order: + "all language (-1)", most specific if present, can't be localized + "current language" most specific for the current given request context + "language fallbacks" (might include "default language") Resolves: #89153 Releases: master, 9.5 Change-Id: I25b17d1d618bb1509737d43b877a16c3a6da9f28 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61668 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Markus Klein authored
Resolves: #90408 Releases: master Change-Id: Ifefec22a13b0bf303fd06afa744fd9b1c1733a36 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63281 Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
Markus Klein authored
Preset the expected data values correctly to make the detail view of BE users functional if those have no table read or modify permissions. Resolves: #90409 Releases: master Change-Id: I3040390c7f702cd201909ded3499f445ea83e7c2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63280 Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
Oliver Hader authored
Patch for issue #90351 in master branch was merged fast. Some aspects were missing which are streamlined with this change. - workspace preview "ADMCMD_prev" using backend user setting ("strict" by default) Resolves: #90380 Releases: master Change-Id: I8d244db64a438d7537310787934a49abe3ebf28d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63256 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
Georg Ringer authored
The element information modal now shows all fields of the current record and the selected type. The TCA configuration `showRecordFieldList` inside the section `interface` is not evaluated anymore and all occurences have been removed. Resolves: #88901 Releases: master Change-Id: I7d2dcb60b04b16083e615bf23dccf54f0a493848 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61424 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Stefan Froemken <froemken@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Stefan Froemken <froemken@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Ralf Zimmermann authored
Make sure to apply all configured validators if a form is rendered multiple times on the same page. Resolves: #90083 Releases: master, 9.5 Change-Id: Ife1a8beb985cde4fdb7c635fd98f4e7bc5ccb9db Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62840 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Ralf Zimmermann <ralf.zimmermann@tritum.de> Reviewed-by:
Steffen Frese <steffenf14@gmail.com> Reviewed-by:
Sascha Rademacher <sascha.rademacher+typo3@gmail.com> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Ralf Zimmermann <ralf.zimmermann@tritum.de>
-
Anja Leichsenring authored
Resolves: #90391 Releases: master, 9.5 Change-Id: I8c69e206c175d3a230157a4ad3593365e05f2690 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63268 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Alexander Schnitzler authored
This patch adds two methods setDefaultValue and setProperty which are called from within class AbstractRenderable via $this->setDefaultValue() and $this->setProperty() but are meant to be called on a child class. The implementation of said methods with an empty method body only serve the purpose to please phpstan. As mentioned in those method bodies, someone with a deeper understanding of the form extension architecture needs to decide whether the abstract class AbstractRenderable should only declare those methods as abstract methods, i.e. child classes have to implement them or if the abstract class can provide a meaningful default behavior which can but doesn't need to be overridden by child classes. Releases: master Resolves: #90385 Change-Id: I1ac3b319746d8eca12b32394cd9da2073431b582 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63262 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Georg Ringer authored
After reworking the IP usage in logs with #85316 the IP address hasn't been substituted anymore in the login error log mails. Replace the IP address which can be found in the field 'IP'. Resolves: #90335 Releases: master, 9.5 Change-Id: I2472bd8902915bf964a167c389c2048242b29207 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63249 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Guido Schmechel <guido.schmechel@brandung.de> Tested-by:
Benni Mack <benni@typo3.org>
-
- Feb 16, 2020
-
-
Sybille Peters authored
Document change "Feature: #87451 - scheduler:run command accepts multiple task options". The scheduler command now accepts multiple --task options. Resolves: #90394 Releases: master Change-Id: Ie0f7973cab01db88f4df0cb4cd87a194bf4914b1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63270 Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
Sybille Peters authored
We move chapter on scheduler command line execution to top level in the menu. This was somewhat hidden under "Installation". Additionally, we add a link to this chapter to the section on cron. Additionally the chapter "Installation" is renamed to "Installation & setup". "Administration" is renamed to "Backend administration". Resolves: #90395 Releases: master, 9.5 Change-Id: Id25cdb16f9f3c87c9fdac1194246c5d471d1476c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63271 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
Sybille Peters authored
Events are named AfterSectionMarkupGeneratedEvent and BeforeSectionMarkupGeneratedEvent. Resolves: #90397 Releases: master Change-Id: I6a4b690894321d10a618f6056e0790a69d0921d6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63273 Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
Georg Ringer authored
Use mb_strlen & mb_substr to cut off TypoScript to avoid exceptions if the 20th character is a multibyte value. Resolves: #90372 Releases: master, 9.5 Change-Id: I8f90aa54a4cb6ede95d4fa50d557aeec4d8cd031 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63255 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com>
-
- Feb 15, 2020
-
-
Christian Eßl authored
A regression introduced with #87879 removed the _REF_ label in the header table row of the filelist module. This commit fixes this bug. Resolves: #90387 Relates: #87879 Releases: master Change-Id: I7c7289352d81b09576fce6b266fb6c7a11daeeb1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63265 Reviewed-by:
Claus Due <claus@phpmind.net> Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Guido Schmechel <guido.schmechel@brandung.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
Georg Ringer authored
Show all collected information of a user in the beuser module instead of just the information directly added to the user record. The UI will be improved with later patches This patch also switched to constructor injection in BackendUserController. Resolves: #90298 Releases: master Change-Id: I8cc19a475ae43404e29402b99852286bf6991b70 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63149 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Christian Eßl authored
The "Environment Overview" card in the admin tool will now show the application context the TYPO3 instance is running with. Resolves: #90136 Releases: master Change-Id: Ia9583ac093cdeba341e8cd079bbac341098a3b76 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63259 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Alexander Schnitzler authored
Used commands: composer remove rector/rector --dev composer require rector/rector:"~0.7" --dev Since updating phpstan to version 0.12.10, rector failed to run properly. Also, the updated version of rector brings a couple of bugfixes and new features. Releases: master Resolves: #90383 Change-Id: I29d66c5e34db594fbcf24949c61e6db85cecae1b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63260 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Alexander Schnitzler authored
This patch only pleases phpstan. The refactoring of the indexer which includes the removal of the direct dependency to 3rd-party classes is taken care of in the following issue. https://forge.typo3.org/issues/83603 Releases: master Resolves: #90384 Change-Id: Ia1ee984f692dce7f8293077cbea3359d6843cb46 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63261 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
Alexander Schnitzler authored
Releases: master, 9.5 Resolves: #90381 Change-Id: Ib7d3700ab928addec9c585e031fa9c0ba1bb50d3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63257 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Alexander Schnitzler authored
Releases: master Resolves: #90382 Change-Id: I26fe0116e48c64362c2b124e9daeec73182cccc2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63258 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Alexander Schnitzler authored
Both the \TYPO3\CMS\Core\Http\Client\RequestException and \TYPO3\CMS\Core\Http\Client\NetworkException declare a method getRequest which must return a RequestInterface object which they did not. Releases: master Resolves: #90379 Change-Id: I4cdee1cdf95efc1ebcabaacec7be2cd290f31989 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63254 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Alexander Schnitzler authored
Upgrade phpstan/phpstan to at least 0.12.10 and enable bleeding edge configuration to be able to run the phpstan analysis with all available cpu cores. Releases: master Resolves: #90378 Change-Id: I4c76a8f44c570b126844d1bde96998cf9d3790fa Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63253 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
Andreas Fernandez authored
Use the correct target (clicked button) to be able to access the button name. Resolves: #90036 Releases: master Change-Id: I3a2face0c10aa41dea13bc49d3f8f3e9f47b3fcc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63251 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
TYPO3com <noreply@typo3.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Nikita Hovratov authored
Since the querybuilder is used to fetch notes the default restrictions of both apply sys_note and be_users. This patch removes the default restrictions and adds them manually only for sys_note. The names of hidden or deleted authors are replaced with "unknown author" instead. Fixes: #90216 Releases: master, 9.5 Change-Id: I7613909dad078256747e8b719bf68d64729fb56d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63246 Tested-by:
Stefan Froemken <froemken@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Stefan Froemken <froemken@gmail.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Guido Schmechel authored
IP anonymization now takes the correct pattern when querying the database. Depending on the mask to be shortened. Resolves: #89788 Releases: master, 9.5 Change-Id: Ic09d2385b33434cc2d7553087c2014b190f9c339 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62992 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:
Georg Ringer <georg.ringer@gmail.com>
-