- 14 Jan, 2022 1 commit
-
-
This happens when "transOrigPointerField" is not defined in TCA configuration. Additionally, a PHP 8.1 deprecation is fixed when passing a null to trim(). Resolves: #96514 Releases: main, 11.5 Change-Id: Ic99bd0b0c166397bda23d2e45ca2d4cb766000be Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72981 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 13 Jan, 2022 1 commit
-
-
Doctrine uses mixed type for most of their method arguments in QueryBuilder. Since TYPO3 core uses variadic arguments for some methods in the wrapping QueryBuilder, argument types have been streamlined to match the ones in the concrete QueryBuilder instance from Doctrine. Resolves: #96507 Related: #96457 Releases: main, 11.5, 10.4 Change-Id: I834240f764feac7af9fba7db0d45aaf4927abb2e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73009 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 11 Jan, 2022 3 commits
-
-
The change for issue #94357 introduced handling for `event/` URLs, and accidentally modified handling for `video/` URLs as well. As a result, the `video/` IDs were incorrectly resolved containing a leading slash. Resolves: #96509 Releases: main, 11.5, 10.4 Change-Id: I5623ff59dac44a699877e4e5a2e91707f72a407e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72968 Tested-by:
Jigal van Hemert <jigal.van.hemert@typo3.org> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Jigal van Hemert <jigal.van.hemert@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
Change-Id: I7acf728adcceb640d21918dcabe77f5cacfa66f1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72959 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
Change-Id: Ia82e7fc67597b331ddb8f7eb35afb0598899a397 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72958 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
- 05 Jan, 2022 6 commits
-
-
With #96393 forward-compatible prepared statement suport has been added, which lacks support for the broadly known doctrine/dbal 'PARAM_STR_ARRAY' and 'PARAM_INT_ARRAY' types. Internal methods as alternatives were introduced as core internal methods with #92493 in the internal 'QueryHelper' class. This patch now moves these internal implementations to the 'QueryBuilder' to provide an forward-compatible public alternative, which is needed to prepare statements with 'in()' or 'notIn()' expression with array values, which can only be used as non-placeholder, which is not supported by PHP PDO implementation. Further usage of internal implementation which was introduced with #92493 are replaced with new public methods and internal methods in QueryHelper removed. Resolves: #96434 Related: #96393 Related: #92493 Releases: main, 11.5 Change-Id: I1f7f532eb82a248a28d8d7ec707d678d59a73ec0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72885 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Some methods have the wrong type declaration. E.g. string instead of mixed. Add type-hints for completeness. Resolves: #96463 Releases: main, 11.5 Change-Id: I415e8fa572ecbe278aa8323fd206494d314c559f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72882 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Benni Mack authored
This change moves the method resolveShortcutPage() into PageRepository as it is now also used in determining if a page is marked as active / current. The method `resolveShortcutPage()` is much more convenient when working with $page records instead of the properties, instead of `getPageShortcut()`. This also allows MenuProcessor to have a proper "active" and "current" values set properly without any workarounds. Resolves: #85138 Resolves: #80841 Resolves: #87923 Releases: main, 11.5 Change-Id: Ic401fb42696757199c5974120f24250c467d9b75 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72881 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
If a page slug ends with 'index' and site has a routing configuration with a PageTypeSuffix with index and suffix '.php' as default suffix, route resolving cuts 'index.php' from the uri, ending with a slug without index in it and thus not resolving the page and displaying 404 page. The reason for this is the code fragment which strips the document root from the uri as a cleanup for some systems, and fixes an issue for calling id/type parameters with index.php (main entry point), which has been added as a bugfix in v9 with #88028. There was a first attempt to fix this page resolving issue with #94537, which has been a regression and reverted with issue #94968. To ensure everything works and regression is covered before a new patch, there has been two patches with #95096 and #95362. After the regression there has been a really deep analysis, to get all puzzle pieces together over the time, which ended in the pre-patches and finally in this patch. The stripping of the document root has been implemented to late in the resolving chain to solve #88028, thus the followup fixes interferred with the resolving concept. This patch moves this stripping from the page-resolving point some steps early to the site-resolving step, and doing the stripping only on the left site of the uri and avoiding a generall str_replace(), thus fixing past issues and the current issue in the correct place. Furthermore tests for this issue are (re)added with this patch, as they were removed with the revert. Resolves: #94905 Related: #95096 Related: #95362 Related: #94537 Related: #94968 Related: #88028 Releases: main, 11.5 Change-Id: I2e10689893047e2d8f19057dfac2fb3b5f0bdcde Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72880 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
With the introduction of itemGroups, the index 3 of the select items array has been shifted one position to the right. Before that, the index 3 was used for descriptions and index 4 for an optional keyword EXPL_ALLOW or EXPL_DENY. These are used together with authMode=individual to explicitly allow or deny single items. Since descriptions now occupy the index 4, the former usage of this index needs to be shifted as well to index 5. For backwards compatibility reasons, a TCA migration is added, which will check for these special keywords and move them one index up. Resolves: #96444 Related: #91008 Releases: main, 11.5, 10.4 Change-Id: I32a96f5c6377871551ab4ee60a402a585da7eaa0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72877 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
This patch adds missing 'CompositeExpression' as union type for QueryBuilder methods 'where()', 'andWhere()' and 'orWhere()' to match the ability of the underlaying doctrine/dbal QueryBuilder methods. Resolves: #96457 Releases: main, 11.5, 10.4 Change-Id: Ib9330ffabcdc7680bfd5bb8a991cec60889c9773 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72878 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 04 Jan, 2022 1 commit
-
-
The option "autoplay" only works if "mute" is enabled. See https://developer.chrome.com/blog/autoplay/ for reference. Resolves: #96320 Releases: main, 11.5, 10.4 Change-Id: Ic4e2de0576fe3d1619af8e35274adeb013c72b31 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72845 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 03 Jan, 2022 2 commits
-
-
Resolves: #96415 Releases: main, 11.5 Change-Id: I4f96cd250b1f1ef27c7232b8fff3214cb555ab32 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72841 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Johannes Seipelt <johannes.seipelt@3m5.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Make sure to pass strings to html formatting methods. Initialize hierarchy array correctly. Resolves: #96448 Releases: main, 11.5 Change-Id: I2b9c28303c1c96d0a2ea1bc3ca971da3b4b3fe7d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72838 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 30 Dec, 2021 1 commit
-
-
This error occurs when running linkvalidator in scheduler: Undefined array key 1. Resolves: #96439 Releases: main, 11.5 Change-Id: Idbe4b5bf52722a800026fc7af566daba925eaad2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72837 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 23 Dec, 2021 1 commit
-
-
Benni Mack authored
Resolves: #96344 Releases: main, 11.5 Change-Id: I986945e16e0a2adef827fc0532a431be7ab25e03 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72787 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 21 Dec, 2021 3 commits
-
-
This patch changes the behaviour when building the SchemaDiff on a non-default connection to only fetch tables which are mapped to that connection instead of fetching table details of all tables and discarding the information for unmapped tables later on. This improves the performance and avoids errors for data types unknown to doctrine/dbal in details of unmapped tables. Resolves: #92959 Releases: main, 11.5 Change-Id: Ia4a62d861ea0748995eb0dec4f01e9e65eb3ed46 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72765 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
According to https://docs.phpdoc.org/latest/guide/guides/types.html#union-types it is only allowed to use "string|null" and not "?string" Resolves: #96407 Releases: main, 11.5 Change-Id: I4e9ec53d05feb5cfffc4eebc29de447d6225ab66 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72774 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
Benni Mack authored
Currently, HMENU generates the direct destination for a shortcut URL, but typolink does not. This is an inconsistency, and since HMENU is actually using typolink now as well (in 4.x this was different), the resolving of shortcuts can now be moved into the typolink/link building functionality. Page Shortcuts are now resolved (recursively!) at a single point for all links, except for RANDOM_SUBPAGE variants, as this is sorted out during runtime when hitting the RANDOM_SUBPAGE shortcut page. Resolves: #80113 Resolves: #95947 Releases: main, 11.5 Change-Id: Ib6204ff1b0ecb699ec87f5154dc18c974676e65c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72772 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 20 Dec, 2021 3 commits
-
-
The function `idn_to_ascii()` will return either `false` or a string, the former one is returned on errors. In #93900, the result was cast to string, making the check for `false` useless. As `idn_to_ascii()` can return both, the string cast is removed to make the check for `false` functional again. Resolves: #96399 Related: #93900 Releases: main, 11.5 Change-Id: Ib5327766fc545a75feb7389d18358aa85b76e5db Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72720 Tested-by:
Simon Schaufelberger <simonschaufi+typo3@gmail.com> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Simon Schaufelberger <simonschaufi+typo3@gmail.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
doctrine/dbal:^3.2 changed return type of result for QueryBuilder execute methods, no longer have used prepared statement accessible for further query execution with other placeholder values. To raise doctrine/dbal:^3.2 two places have been changed to reuse the QueryBuilder instance itself instead of prepared statement with the corresponding patch #96287, thus given up the performance gain through reusable query execution plan in corresponding dbms systems. This patch adds support for prepared statements to TYPO3's QueryBuilder facade as this was not publicly available yet for TYPO3 users to be forward-compatible with Doctrine DBAL 3. Resolves: #96393 Related: #96287 Releases: main Change-Id: I814670ebf9920ed3162a31f98ad9efd4031f47c9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72716 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
doctrine/dbal deprecated quite some methods to cleanup their codebase and provided replacements with more speaking method names. Most deprecated method usages have been replaced in the core, but we missed some. The patch replaces the deprecated method 'executeUpdate()' with the corresponding 'executeStatement()' method in several places to clean this up. This can be done also in 11.5 too, the required minimum version of doctrine/dbal provides these new methods as upwards compatible layer. Resolves: #96389 Releases: main, 11.5 Change-Id: Ibf8f49a27a1c8c4b34bda88a20f4fba6afe45cb8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72715 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 18 Dec, 2021 1 commit
-
-
Helmut Hummel authored
A "type" does not need to be set in a composer.json, so the checks for package type must account for the type being null, to not trigger a warning in PHP 8 Releases: 11.5, main Resolves: #96372 Change-Id: Ic607c3dbb16dfcf4a28b0417b8340be36bcafa87 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72712 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Helmut Hummel <typo3@helhum.io>
-
- 17 Dec, 2021 1 commit
-
-
Helmut Hummel authored
Get rid of the select query entirely, which optimises the task to only require one update query instead of one select and possibly multiple update queries and gets rid of doctrine version related incompatibilities with fetching the select result. Resolves: #96369 Related: #87162 Releases: main, 11.5, 10.4 Change-Id: I87b570f5efa3d77ed5f2c5fc0074e84bef4675a4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72690 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
Helmut Hummel <typo3@helhum.io>
-
- 16 Dec, 2021 3 commits
-
-
The FinisherOptionGenerator of the form extension generates the data structure for the form setting overrides on the fly. By doing so, it didn't make a distinction between normal TCA fields and flexform specific sections/containers and added the wrapper "TCEforms" to sections as well, which broke the validation in DataHandler for the fields inside the container (E.g. the email field). The patch checks if section is set to "true" and adds the "TCEforms" key only for normal TCA field configurations. Unit tests have been added for the DataHandler checkValue_flex_procInData_travDS method, which show cases with and without the "TCEforms" key. Also, since this works now, a PHP 8 warning appeared. This is fixed now, too. Resolves: #95441 Releases: main, 11.5 Change-Id: Ib12a0484bcbdc827664181ca6af89edfadee13d8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72688 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Fix PHP8 warning issue if $_SERVER['PATH_INFO'] is not set. Resolves: #96373 Releases: main, 11.4 Change-Id: I427aee39c6f6389e418f27474c01cbfd973355e1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72687 Reviewed-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Helmut Hummel <typo3@helhum.io>
-
Benni Mack authored
HMENU special="directory" and special="updated" did not use PageRepository directly, which led to duplicate entries with workspaces. This change does not use "$cObj->exec_..." anymore and fixes all problems. composer req --dev typo3/testing-framework:^6.15.2 Resolves: #96226 Releases: main, 11.5 Change-Id: I595ac05981d03246eb7671c9ae072f499bff5188 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72684 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 15 Dec, 2021 2 commits
-
-
The following deprecation occurred in PHP 8.1: PHP Runtime Deprecation Notice: trim(): Passing null to parameter #1 ($string) of type string is deprecated. This happens in various places: * Using stdWrap_field() or in stdWrap() places * BackendUtility (e.g. new IRRE elements) * ExtensionManager Resolves: #96354 Releases: main, 11.5 Change-Id: Ie5c721784b51ed5493c8d9e1d557b08611263f6b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72677 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Resolves: #96350 Releases: main, 11.5 Change-Id: I67e9fd68de038b84c83f7f12a465e6e37f918568 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72676 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 14 Dec, 2021 2 commits
-
-
Change-Id: I39067da924f96b5e69eaf2e060b348edd39a6755 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72650 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org>
-
Benni Mack authored
Change-Id: Idaced9f8520ebf697cbb175716989946acac3c92 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72649 Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 13 Dec, 2021 2 commits
-
-
Oliver Bartsch authored
Actions to site configurations, in the site configuration module, are now properly logged with the new logging type "site". Resolves: #91744 Releases: main, 11.5 Change-Id: I43156f0ac4eaa538e1f10442d4e54d141073e6da Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72587 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
-
This adds missing tests for the TCA "filter" option for group, select and inline. Resolves: #96339 Related: #36810 Releases: main, 11.5 Change-Id: I402edf4774f35c3b15aa53eb630d9d098f847e87 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72585 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 12 Dec, 2021 1 commit
-
-
Helmut Hummel authored
To decide whether an error should be handled by the ErrorHandler or not, only three things must be taken into account. 1. The current error_reporting() level 2. Error levels that are ignored by configuration 3. Error level of the error that is just handled When combining the first two (with logical and), results in the error level for the errors that should be handled at all. When combining this with the error level of the currently handled error (again with logical and), we can determine wether the error should be handled or not. This always works with any PHP version and with suppressed errors and without. Therefore the PHP version check becomes obsolete and is removed. Releases: main, 11.5 Resolves: #96311 Change-Id: I96d440d9db05a3acf1f8a12664787e05a3e31254 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72581 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
Helmut Hummel <typo3@helhum.io>
-
- 10 Dec, 2021 2 commits
-
-
Make HTML parser more tolerant for single tags with ending slash but without white spaces. So `<hr/>` already was allowed and internally converted to `<hr />` while parsing the HTML. This patch extends this replace rule to all tags so that also `<br/>` can be used in RTE fields. Resolves: #96307 Releases: main, 11.5, 10.4 Change-Id: I7ba6c88e35804c6b5f991fb6b730fbc3d7a2514e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72579 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
Any database changes are now logged as info (same as clearing caches and changing file handling). Resolves: #96316 Related: #94433 Releases: main, 11.5 Change-Id: I22daefc7111eb9abdafa2f66c1d21b2fbfcaf011 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72576 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 09 Dec, 2021 2 commits
-
-
Helmut Hummel authored
Fix condition that checks the extension type, to only re-throw the exception when an extension does not define an extension key. Resolves: #96276 Releases: main, 11.5 Change-Id: Iacc0680f21cd3daa2f049f5ccfd25ea6d44bf241 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72575 Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
core-ci <typo3@b13.com> Reviewed-by:
Helmut Hummel <typo3@helhum.io>
-
Helmut Hummel authored
Allow composer installers ^4.0 and also enforce some constraints that could be violated with the new installers. 1. Do not allow duplicate extension keys Multiple packages could define the same extension key. When all extensions are then installed in vendor folder, there won't be any conflicts on the file system, so an exception is now thrown to make people aware of this misconfiguration. 2. Throw an exception if extensions of type typo3-cms-extension do not define an extension key Actually this exception is thrown in the installers package, but the artifact builder must propagate this exception to ensure it reaches the users. composer req typo3/cms-composer-installers:"^2.0 || ^3.0 || ^4.0" composer req typo3/cms-composer-installers:"^2.0 || ^3.0 || ^4.0" \ --no-update -d typo3/sysext/core/ Resolves: #96276 Releases: main, 11.5 Change-Id: Ib76e829f09dbf095fb01031389e301c6e7742103 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72570 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Helmut Hummel <typo3@helhum.io>
-
- 08 Dec, 2021 1 commit
-
-
Benni Mack authored
This change adds the new createSchemaManager() to our Doctrine DBAL Connection subclass to make it forward-compatible with Doctrine DBAL 3.x. createSchemaManager() is introduced with DBAL 3.x and is replacing getSchemaManager() which will be removed in Doctrine DBAL 4. Since this is a very lowlevel change, the method can be added without most notice for extension authors. Resolves: #96286 Releases: main, 11.5 Change-Id: Ifdccc2b0dff443bfe38d23a1bd1333b5c7c5db40 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72555 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 07 Dec, 2021 1 commit
-
-
Benni Mack authored
The past changes of migrating to Doctrine DBAL 3.x had some flaws: * Not all changes from Doctrine DBAL 3.x was applied * core relies on various invalid interfaces and classes, so the return types were wrong (also Tests used the old Statement class) * No explicit ->execute() and ->iterateAssociative() calls and fetchColumn() vs. fetchOne() * added executeQuery() and executeStatement() to QueryBuilder decorator class This change adapts most places to help in migrating to Doctrine DBAL 3.x for TYPO3 v12, but also avoids some unneeded deprecations for now. Resolves: #96247 Releases: main, 11.5 Change-Id: I60e99511efc4f9ec6d8d651c63becff028de4cf2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72430 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org>
-