- Apr 29, 2020
-
-
Oliver Hader authored
Resolves: #91229 Releases: master, 9.5 Change-Id: Ieb6211252a74983a89b7a1057574a1ebe29ae390 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64341 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
- Apr 28, 2020
-
-
Daniel Goerz authored
Resolves: #91224 Releases: master Change-Id: I47d30a21965c3d2246a53c51a68856642cca647a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64339 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:
Daniel Goerz <daniel.goerz@posteo.de>
-
Benni Mack authored
Change-Id: I654ba61c86a66b41f147f32a43bba473258e4f39 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64336 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
Change-Id: I5c7f36e32298917e78f6de564fe9c19dca412015 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64335 Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Oliver Bartsch authored
The TcaColumnsOverrides provider now handles overwriting of a fields default value for a specific record type. This is done by setting the value from `columnsOverrides` as the field value of the new `databaseRow` by respecting TSconfig `TCAdefaults`. Resolves: #86876 Releases: master, 9.5 Change-Id: If03871f262ed89011dbeda3f268f0b61c20036be Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64081 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
aslam idrisov <aslambek.idrisov1@swisscom.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
aslam idrisov <aslambek.idrisov1@swisscom.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Christian Eßl authored
If a html comment is placed in a fluid template at a position, that gets parsed by lib.parseFunc_RTE and no "tags" configuration exists for the parsefunc, a php warning is thrown, because it was not checked if $conf['tags.'] is an actual array. Resolves: #91172 Related: #39261 Releases: master Change-Id: Ia51ff78d7dcda6b74e9e4d218b5345f23c04333d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64304 Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Benni Mack <benni@typo3.org>
-
Helmut Hummel authored
Especially to ease using the API on CLI, we now add a request argument for the siteUrl which is preferred over the current site url to create a default site configuration. Resolves: #91214 Releases: master Change-Id: If00beb2550909c2334d99a61283c6d7f546b25d7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64329 Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benjamin Franzke authored
The extbase DataMapper was changed to use constructor based dependency injection with change #87305. The argument $query (of type QueryInterface) was set to a nullable and way therefore ignored by the Extbase ObjectManager. This class is currently only used via the Extbase ObjectManager in core. It was therefore excluded from the symfony dependency injection and therefore never fataled during symfony DI container build. Symfony DI does – in contrast to extbase DI – inject nullable constructor arguments. That means: Once core or an extension starts to inject this service, injection will fail, as QueryInterface points to the Query object which is not autowirable. (see exception below) Note: While it is not supported that extensions inject this internal service, we still fix this case, because the exception is a) hard to debug und b) core may inject it in future. The service is also declarted to be a prototype (shared: false) as it may contain state, as set via `setQuery`. [1] exception thrown by symfonyduring DI compilation: Symfony\Component\DependencyInjection\Exception\RuntimeException: Cannot autowire service "TYPO3\CMS\Extbase\Persistence\Generic\Query": argument "$type" of method "__construct()" has no type-hint, you should configure its value explicitly. Releases: master Resolves: #91200 Related: #87305 Change-Id: I58b1cff94136a4170fb7e6712470069a141940b7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64319 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Sebastian Fischer <typo3@evoweb.de> Tested-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Reviewed-by:
Sebastian Fischer <typo3@evoweb.de> Reviewed-by:
Alexander Schnitzler <git@alexanderschnitzler.de>
-
Helmut Hummel authored
The check for the constant TYPO3_PATH_WEB was an experiment, to allow a document root with public assets only, but this never worked out and was never really used. The check can safely be removed, as it won't do anything useful anyway. Also adapt a comment in SystemEnvironmentBuilder which still refers to this variable/constant and its usage in the helhum/typo3-secure-web package. This statement can be removed as helhum/typo3-secure-web is not actually using that constant/envvar. Resolves: #91215 Related: #63025 Releases: master Change-Id: I1b44ba97f4654d1e4e200d7ad1a7c228dba48c25 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64330 Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Reviewed-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Josef Glatz <josefglatz@gmail.com>
-
Helmut Hummel authored
\TYPO3\CMS\Install\Updates\DatabaseRowsUpdateWizard currently can only update rows. \TYPO3\CMS\Install\Updates\RowUpdater\WorkspaceVersionRecordsMigration however needs to delete rows and marks them as deleted. We now check for this value for tables without soft delete and delete the row straight away Resolves: #91213 Releases: master Change-Id: I21163c7db435c316231c8e25daa8c190b1507621 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64328 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Susanne Moog <look@susi.dev>
-
Benni Mack authored
The TypoScript conditions "[backend.user.*]" are documented, but were never implemented. https://docs.typo3.org/m/typo3/reference-typoscript/master/en-us/Conditions/Index.html#backend-user This patch is now introducing the missing conditions. Resolves: #90767 Releases: master, 9.5 Change-Id: If6db277f56a2ef3457deb027a676af62a3494151 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63752 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Julian Mair <julian.mair94@gmail.com> Reviewed-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benjamin Franzke authored
The existing "inline" rendering for icons causes bitmaps to be rendered for SVG-inline usage using the <image> tag. This tag can not be rendered in HTML context. The backend module menu uses inlined SVGs. Rendering bitmap icons with SVG-syntax, without an SVG root element, does not work in this context. (Note: It works in SVG trees because the optional svg container is removed by SvgTree.js and the image-tag is wrapped into a new <g> element) We do now wrap "inline" bitmap icons into an svg tag, which will fix the bitmap module case while the bitmap icons will still be embeddable into svg groups (<g>) for svg trees. Resolves: #89558 Related: #89206 Releases: master, 9.5 Change-Id: Ifaec3e697a45ba37b1ee23c0369414ce431cf4e8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64325 Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by: Markus Klein <markus.klei...
-
Benjamin Franzke authored
SMTP encrypt options were quite a hassle with swiftmailer: 'tls' was used as identifier to start a STARTTLS connection via SMTP (instead of using SMTPS), while strings like ssl/tlsv1.0/tlsv1.1/tlsv1.2 instructed to use a SSL/TLS connection via SMTPS (without STARTTLS). symfony/mailer does no longer allow to specify the STARTTLS usage, as it will use it by default (if the server provides support for it). Therefore, we now adapt the SMTP encryption configuration setting via a silent configuration upgrade to avoid that the previous STARTTLS 'tls' is casted to true while symfony/mailer expects false/null. While at it, we also fix an incorrect migration for the transport type 'mail'. This wizard didn't work because of a wrong typecast (which has probably been a copy & paste mistake). Releases: master Resolves: #91070 Related: #90295 Change-Id: I7fb1112730fedbbfcdb641c8ce04e17ea925d927 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64246 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Simon Gilli authored
This will check the dependencies of dependencies during the install of an extension with the extension manager. This solves especially issues with dependent extensions having various major versions for different TYPO3 major versions e.g. ext:powermail. Resolves: #91179 Releases: master, 9.5 Change-Id: I98e6c019066aab303e78b5455ac4dfb58f78cd50 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64308 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
-
- Apr 27, 2020
-
-
Daniel Siepmann authored
* Fix broken indentation * Add missing blank line * Fix wrong used reference target * Add missing interface to docs, which already was referenced Resolves: #91199 Releases: master Change-Id: If42021e0f7b4a0b879ba5be6bde9112b6c7e658d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64322 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Richard Haeser <richard@maxserv.com>
-
Benjamin Franzke authored
We fix PackageManager and ContainerBuilder to allow multiple container instances (including multiple cache identifiers) to be live. ExtensionManager will now load a new symfony container after installing a new extension, and before reloading all ext_localconf files. We need to ensure that possible services in ext_localconf can be loaded when they depend on symfony DI. Note: This is not a BUGFIX as this was never supported for extensions. But it may lead to hard-to-debug bugs when extension developers add a service to ext localconf but do not test the re-installation procedure before publishing the extension to TER. Releases: master Resolves: #91150 Change-Id: I9b01feae6fe2f1637ca653403336cd7d216483bd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64263 Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Raphael Zschorsch <rafu1987@gmail.com> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Raphael Zschorsch <rafu1987@gmail.com> Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
Benni Mack authored
The newly added ContentFetcher class uses the legacy cache name "cache_runtime" which was renamed in TYPO3 v10.0 to "runtime". The change modifies the cache to "runtime". Resolves: #91188 Releases: master Change-Id: I3d6f1b61f766120f13c5fee2fac78b50adfb35b0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64313 Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Reviewed-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
Benni Mack <benni@typo3.org>
-
Anja Leichsenring authored
The current nightly run simply takes too long, we need to cut down the sheer number of tests we run. The current setup aims to execute a small subset of all tests on each DBMS and Php version, but in total every test is run in each composer stage at least once. Resolves: #91058 Releases: master, 9.5 Change-Id: I94fc6627f5da0cc6f36cf789ef8aa227d73d8daa Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64152 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
Resolves: #91198 Releases: master, 9.5 Change-Id: Ibd8ec73ee4a3b38feced4fca3a8609be4b0a3757 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64317 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Daniel Siepmann <coding@daniel-siepmann.de> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Daniel Siepmann <coding@daniel-siepmann.de>
-
Stephan Großberndt authored
If caching is disabled in the CacheManager, caches using the TransientMemoryBackend are not adjusted to NullBackend anymore. This mainly affects the runtime cache, which is memory-based anyways and should be a "forget after the request"-cache. This also fixes a PDOException in the page slug update wizard when using PostgreSQL, as the Install Tool is using the core in "no-cache" mode. (See entry point of the Install Tool) Resolves: #91206 Releases: master, 9.5 Change-Id: Id9085bd85bdbf321ef210c75c2bb8aefc6f5f061 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64320 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Stephan Großberndt <stephan.grossberndt@typo3.org> Reviewed-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Stephan Großberndt <stephan.grossberndt@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Benjamin Franzke <bfr@qbus.de>
-
Georg Ringer authored
Replace the usage of `GeneralUtility::milliseconds` in Indexer class which has been deprecated with 91001. Resolves: #91192 Releases: master Change-Id: I2057ecec038195d67acab10946d4542b1fba9646 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64316 Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Andreas Fernandez authored
While migrating DataTables to tablesort, the sorting for updateable or (un)installed extensions went lost. This patch adds the ability to sort these columns again. Resolves: #91182 Related: #86343 Releases: master Change-Id: Ia33c3dcc789967a984090ccf26150f6d319e85e9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64310 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- Apr 25, 2020
-
-
Alexander Obert authored
Releases: master, 9.5 Resolves: #91189 Change-Id: Ice3d01530ce595b353fc90a5d672573b9a8d7d78 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64314 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- Apr 22, 2020
-
-
Oliver Hader authored
Previously `&returnUrl` has been generated in JavaScript dynamically. On changing to regular anchor links that information was forgotten. Resolves: #91171 Releases: master Change-Id: I4038122f769f1cf85949adbf6c5638a5ad8e5084 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64303 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Daniel Siepmann authored
Explain how to register dashboard widgets via Services.php instead of Services.yaml. This might be necessary if a widget is provided under certain circumstances, e.g. if a specific extension is enabled. Resolves: #91159 Releases: master Change-Id: Ic16e79f478b6da446ff1854979c3c3a822674d1e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64296 Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Richard Haeser <richard@maxserv.com>
-
Benni Mack authored
When a live page is hidden, but the workspace version is not hidden, the actual content is now shown properly. Resolves: #85003 Releases: master, 9.5 Change-Id: Ib41e1b6f24f32e5f6deb06f692b929f11ac8e38b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64215 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Oliver Hader authored
This change aims to reduce the amount of inline JavaScript by removing `onchange` or `onclick` events and dynamically created JavaScript code/settings. * adjusts invocations of top.TYPO3.InfoWindow.showItem * adjusts low-level inline `onchange` and `onclick` events Both JavaScript modules `TYPO3/CMS/Backend/GlobalEventHandler` and `TYPO3/CMS/Backend/ActionDispatcher` are required to actually handle these new triggers and correpsonding events - that's why they are loaded in `ModuleTemplate` and deprecated `DocumentTemplate`. Resolves: #91117 Releases: master Change-Id: Ie7012445d09c3aee253548cb3057c8e9e4b86809 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64242 Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
Oliver Hader authored
Resolves: #91166 Releases: master Change-Id: Ief1dfff09aba275a11306693cf39ebc71992f5f9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64301 Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Use newer formating, e.g.: * Definition lists for better readability. * Content directive to automatically update local TOC. To not update by hand. * Use short :: for yaml examples. To shorten rst code and make it more readable. * Use option directive to highlight options. * Update intersphinx urls to not trigger redirects. Always use YAML instead of yaml or Yaml. Use inline Fluid example, instead of adding it with another tip. Update Includes.txt to match current state and provide expected css classes and text roles. Resolves: #91137 Releases: master Change-Id: I185c17a80e69b723b292b9c99eddfe4412362f20 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64299 Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Daniel Siepmann <coding@daniel-siepmann.de> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Daniel Siepmann <coding@daniel-siepmann.de>
-
Josef Glatz authored
Resolves: #91164 Releases: master, 9.5 Change-Id: Ida1267d13ad2330945c0efafb00cf8ac1656bc61 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64300 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- Apr 21, 2020
-
-
Daniel Siepmann authored
Resolves: #91155 Releases: master Change-Id: I8e26f7d9bb0c22dcb00cadc704cf8c61ffaf8c0a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64293 Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benjamin Franzke <bfr@qbus.de>
-
Daniel Siepmann authored
Resolves: #91163 Releases: master Change-Id: I52c4323f2ef812e87015a203f0e2dbaa5a38a581 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64298 Tested-by:
Christian Eßl <indy.essl@gmail.com> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
Christian Eßl <indy.essl@gmail.com> Reviewed-by:
Daniel Goerz <daniel.goerz@posteo.de>
-
Christian Eßl authored
The fluidbased page layout refactoring done in #90882 missed two spots, where the no longer existing function getBackendLayout() is called on a GridObject. Resolves: #91162 Related: #90882 Releases: master Change-Id: I7d381fe35a02c4f1464f9c4bb9fc31b27ef02b1d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64297 Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
David Steeb authored
Releases: master Resolves: #91158 Change-Id: I71de97b4b62985e0630d2475523a96d4d7f206ba Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64294 Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Benni Mack <benni@typo3.org>
-
Christian Eßl authored
The code block using $scheme is never reached, because there is already an elseif condition further above, that is true for all urls containing ":". The last else block even states in the comment: "special handling without a scheme" Therefore the variable is removed to remove a bit of complexity from the function. Resolves: #90951 Releases: master, 9.5 Change-Id: I2bc9fe0c546cb946fc32789ee384c3c60ac7c1fa Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64077 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:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
Benni Mack authored
Change-Id: Ia7d214d29ca5fd958fd9c8169b2d76578cbeb511 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64292 Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org>
-
Benni Mack authored
Change-Id: I8f9c86cfb5a9785e6884ebd643127cac91bbbd67 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64271 Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Thomas Pronold authored
The 'else' part would never be returned in this cases. Used [a-zA-Z0-9]{3,}\)[^(]?\$.*\?\? to find the cases. Care, this brings up false positives as well. Resolves: #91154 Releases: master, 9.5 Change-Id: Ifdb0f75995543c3cc8abeb81aba52e935e9bf9a1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64270 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Susanne Moog <look@susi.dev>
-
Claus Due authored
Skip creation of the PageLayoutContext in PageLayoutController if the user has no access to the page, or if the ID parameter was malformed. Releases: master Resolves: #91147 Change-Id: Idd73aa7ba5e6b3a2b41429b1887ad8f9d1db45ad Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64259 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
Benni Mack authored
ZipService->extract was introduced for a security patch set but the permissions are not set correctly, as fixPermissions receives a directory with a slash at the end, resulting in "//" for recursive checks. This patch fixes the issue. Resolves: #90417 Relates: #90118 Releases: master, 9.5 Change-Id: Ie56ef6a3781b12c9ac2cf9a859ec226f48691d7f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64267 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
Danilo Caccialanza <supercaccia@bluewin.ch> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Reviewed-by:
Danilo Caccialanza <supercaccia@bluewin.ch> Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-