- Nov 10, 2022
-
-
Bastien Lutz authored
Site Settings were introduced with TYPO3 v10. In contrast to the rest of the site configuration, site settings are sane defaults for TypoScript constants, and consist of simple key value logic. In order to separate settings, make them accessible and editable in the TYPO3 Backend, and distinguish between the functionality between required site configuration and optional settings, the "settings" part of the settings are moved to a separate "settings.yaml" file in the site configuration folder, which will later-on be editable by the TYPO3 Backend with the new Settings API introduced in a separate patch. Resolves: #99047 Releases: main Change-Id: Idbcb33ccf1c0d8a728b80ad4c242b56ff2d69afd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76491 Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
-
Oliver Klee authored
This update makes a warning more specific. Run commands: > composer req --dev phpstan/phpstan:^1.9.2 > ./Build/Scripts/runTests.sh -s phpstanGenerateBaseline Resolves: #99045 Releases: main, 11.5 Change-Id: I4c5af9d69e0e5b8f4b0d78efd4caa4ed79aed795 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76538 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
Andreas Fernandez authored
Resolves: #99039 Releases: main Change-Id: If7ea6c584bad583a206815cef40d7628c3eded05 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76531 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
-
Bastien Lutz authored
With Doctrine DBAL in TYPO3 v8, a default value for various fields were added to avoid SQL errors (nullable), setting them to their default value. However, there is a culprit. When editing e.g. be_users.file_permissions where you have selectCheckbox field with all options, it was never possible to unselect all, as the default value was then used. Through some workarounds, DataHandler now checks the modified records on the selectCheckbox type to not fall back on the default value. Resolves: #70812 Releases: main, 11.5 Change-Id: I2cd3bf87c31cd4fe5244b26eb3fe2e58e3d8755c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76523 Tested-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
-
Benni Mack authored
A new TypoScript option config.forceAbsoluteUrls = 1 is added, which allows to create ANY link to be absolute (pages + files etc), as well as all images, included assets to have a full qualified domain name. Setting this option will override any option in config.absRefPrefix and any typolink.forceAbsoluteUrl = 0 options. The main benefit is to create a fully static version of the frontend. Ideally, config.absRefPrefix can then be phased out and the config.absRefPrefix option should be removed in favor of this new feature at a later stage. Resolves: #87919 Releases: main Change-Id: Ibbd3084a978c8a2a4ff803f9aef276679a1658f3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76463 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
-
- Nov 09, 2022
-
-
Christian Kuhn authored
The HtmlViewHelper relies of Frontend TypoScript "parseFunc" functionality and has an ugly hack to prepare Frontend rendering in Backend context. The core no longer uses f:format.html in Backend context since the introduction of f:sanitize.html and f:transform.html. Using f:format.html in Backend context should be deprecated. Resolves: #99031 Related: #94825 Releases: main Change-Id: I60c5ea36b664a35abde431d2ac845ee9e2bff4bb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76519 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
-
Susanne Moog authored
The sites module now displays a warning in case the same root page ID is used for multiple site configurations, as only the last one will be used. Resolves: #93423 Releases: main Change-Id: I984fde19a96ef73e6282f70d45775264c141c147 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76516 Tested-by:
-
Susanne Moog authored
To simplify imports in configuration and allow for compacter files, glob() patterns can now be used for importing files in the core YamlFileLoader. Example: imports: - { resource: "./**/*.yaml", glob: true } - { resource: "EXT:core/Tests/**/Configuration/**/SiteConfigs/*.yaml", glob: true } Resolves: #93112 Releases: main Change-Id: Ib352180444190c7d2cee5ed585d420b9a5b58d7d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76462 Tested-by: -
Christian Kuhn authored
Minor patch to reduce usages of class TypoScriptParser in comments and description. Resolves: #99029 Related: #97816 Releases: main Change-Id: Ic20aa9f90623590b219ef98c62ab121c42ae8fcd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76518 Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
-
Christoph Schwob authored
Add a description field also for redirects, which could be used to add notes for further handling of the correpsonding redirect. This follows the same logic like for other record types. Resolves: #99011 Releases: main Change-Id: I216eca8e72b9bf825ad9542997ec603f01ddc879 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76456 Tested-by:
-
Stefan Bürk authored
This change change the expectation check of one functional test to properly deal with unpredictable result order based on filesystem orderings. Resolves: #99027 Releases: main Change-Id: I26373a2f70ad60ef17ea7da453a6931109b9e152 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76515 Tested-by:
-
Achim Fritz authored
The new event PageContentPreviewRenderingEvent introduced in TYPO3 v12 now allows to modify the record itself, making it as flexible as the previous hook. Resolves: #99026 Releases: main Change-Id: I475c797c88e765972a915f77aeb0f0441d7548d1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76514 Tested-by:
-
Benni Mack authored
When using a TCA table without deleted, or any other enablefields except "endtime", then the SQL query is built in a wrong fashion both in PageRepository and BackendUtility. Thee source of this disaster is inproper encapsulation in parenthesis when comparisons are build. Instead of simply adding a manual "()" around the or() comparisons, this change adjusts CompositionExpresion to properly add corresponding parenthesis, which ensure this in every case and avoid missing usages. A couple of tests are adjusted to properly reflect this change. Resolves: #89616 Releases: main Change-Id: I4aed140cbca5b4b40dfacd459a4c3aa30549b582 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76481 Tested-by:
-
Benni Mack authored
The backend UI does not support handling of baseVariants for languages, however it is possible to define them in the config.yaml of a site configuration. However, when editing and saving a site, the baseVariants manually defined were removed. This has now been changed, as the baseVariants are kept when persisting the site configuratino via the UI. Resolves: #93719 Releases: main, 11.5 Change-Id: I8a0b3be72ddfab46da59b3f8a69ad16121c7246b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76460 Tested-by:
-
- Nov 08, 2022
-
-
Oliver Hader authored
Symfony's UrlMatcher takes multiple routes and returns the first match. However there might be better matches that are not considered at all. That's why a custom BestUrlMatcher is introduce, which resolves all matches for further reduction. Previously the route collection was sorted by names and identifiers, which now has been adjusted to focus on the actual matches when being compared to the current request. The fallback route (site base URI). This way, overlapping route definitions can be resolved better. Resolves: #93240 Releases: main, 11.5 Change-Id: Ib1a7361dc86ed48a474d5e55583a622df58e8939 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76464 Tested-by:
-
Susanne Moog authored
The YamlLoaderTests are better suited as functional tests as they access the file system and require accessible mocks otherwise. Resolves: #99025 Releases: main Change-Id: I2d355c5d19494408da2d1512f5f8c742087dd9a2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76490 Tested-by:
-
Christian Kuhn authored
With last non-b/w compatibility related calls to TypoScript/TemplateService being removed, we can now actively deprecate method usages of this class. The deprecation has been mentioned with v12.0 in Breaking-97816-NewTypoScriptParserInFrontend.rst already, the patch adds trigger_error() calls and streamlines some left over comments. Another ReST file is added pointing to the new Request attribute added in Frontend context. Resolves: #99020 Related: #98503 Related: #97816 Releases: main Change-Id: Id01f4a4cb230f632f599e06ff4efe67fd53717c3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76477 Tested-by:
-
Oliver Bartsch authored
Due to changes in #98960 the resolved entity name might contain slashes, which need to be quoted to prevent PHP warnings. Resolves: #99023 Related: #98960 Releases: main, 11.5 Change-Id: I75eecbdbbddc82b5b1189388413fabd7370d4229 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76488 Tested-by:
Dmitry Dulepov <9csxfqr4jy@liamekaens.com> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
-
Oliver Bartsch authored
Generation of a slug proposal based on defined generator fields does now also work for basic select fields, which were previously not considered by the JS component, because they do not use the FormEngine specific visible / hidden field combination. Resolves: #94371 Releases: main, 11.5 Change-Id: Iedd2d17e97db8abd9cf5c4a3b476825fcd854191 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76485 Tested-by:
-
Torben Hansen authored
Resolves: #98823 Resolves: #98824 Releases: main Change-Id: I81f0ccf1d76316635ad6f41d5b1bcfe7112442cd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76484 Reviewed-by:
-
Christian Kuhn authored
Resolves: #99022 Related: #99019 Releases: main Change-Id: Ia43b20a18e0a385603ed78964325980206a4ea2f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76482 Tested-by:
-
Christian Kuhn authored
TypoScript TLO _GIFBUILDER has been bug fixed with a previous patch. This patch adapts forgotten matches in auto completion. Resolves: #99021 Related: #98720 Releases: main Change-Id: I32fe0e01b176cf4b9ba075221dd76d6d043ac96a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76480 Tested-by:
-
Torben Hansen authored
Resolves: #98825 Releases: main Change-Id: I78bf3d08d4c996e57ceb1415cd9cf8bc2904a731 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76479 Tested-by:
-
Torben Hansen authored
Resolves: #98826 Releases: main Change-Id: I4ee06fd0e36f89e82b05050d9bc46b81d0d4c045 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76478 Tested-by:
-
Christian Kuhn authored
There is little point in not clearing all caches when extensions are loaded / unloaded using the extension manager. It's easier for extension developers to rely on all caches being cleared, it's one thing less to think about. The patch deprecates the clearCacheOnLoad and clearcacheonload array key in ext_emconf.php and removes the handling in extension manager. Resolves: #99019 Releases: main Change-Id: Id6ff3db02e2ff82813534e1d2a40cbfac0013b8c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76474 Reviewed-by:
-
Stefan Bürk authored
Default language page slug usage in combination with the siteLanguage base of non-default language has been resolved and delivering the language content. This made the page accessible with multiple urls. Available and existing translated pages should be only resolved by the language slug, not the default language page slug. However, if page is not translated, using the default language slug for the resolving should be only considered and working if fallback settings are provided. Resolves: #88715 Resolves: #96010 Releases: main, 11.5 Change-Id: Id618880fe2ba26fd3b6ab50b4813968923ec5acb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75101 Tested-by:
-
Alexander Schnitzler authored
Due to the dependency of those objects to the DataMapper and its own dependency chain, serialization of those objects lead to error: Serialization of \Closure not allowed. To ommit this issue and to reduce the footprint of the serialization data in general, the data mapper should be omitted and reinitialized via __serialize() and __unserialize() Releases: main, 11.5 Resolves: #97190 Resolves: #92148 Change-Id: If8b78a93308eb14d40080c9cceee95754b785ba8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73975 Tested-by:
-
Benni Mack authored
FormEngine's TreeRendering for categories utilizes the TreeDataProvider logic, which is handed over a list of available items loaded by FormEngine's AbstractItemProvider. These records have already been validated and a full record was already loaded by FormEngine at this point. The TreeDataProvider construct then fetches ALL records again, as it only works with the "IDs", but not with already loaded full rows. This makes the construct expensive. It needs a bigger overhaul. To mitigate the performance impact of bigger category trees, the patch applies a hack to suppress loading single category rows multiple times by handing them over from FormEngine to the TreeDataProvider construct. As this change is also backported to 11.5, the optimizations are only done for type=category to minimize impact for other Tree usages. Resolves: #84558 Resolves: #90398 Resolves: #97003 Resolves: #76581 Resolves: #98807 Releases: main, 11.5 Change-Id: Ief183f1673d3a17036ca5e68c62dc18a4277def1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76443 Tested-by:
-
Benni Mack authored
Resolves: #98175 Releases: main, 11.5 Change-Id: Iccc439eafbbb1f959c8c2bc12248b7c4aa560260 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76466 Tested-by:
-
Oliver Bartsch authored
This followup prevents an out of bounds exception and adds a couple of tests for the new functionality. The min length is now set to 8. This is now also checked when using the special "random" option. Resolves: #98540 Releases: main Change-Id: I5e89813794a0178b7d9c835e89c6272128b4b8c3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76461 Reviewed-by:
-
Torben Hansen authored
Resolves: #98827 Releases: main Change-Id: Ieb71ff04453f4c9b6b3a4c733b4e71732b21ecba Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76472 Tested-by:
-
- Nov 07, 2022
-
-
Benni Mack authored
This change adds the basic information for a type when adding a plugin as CType. When adding a plugin with "list_type" (default), then the "list" CType is used, and extension authors are able to add or remove fields easily with the API. However, when encouraging extension authors to use CType, this is currently much more boilerplate and not possible to make this more flexible. As shown, EXT:felogin and EXT:form previously used this concept manually, which does not allow to extend fields properly, but extensions with plugins as CTypes had to define them explicitly. As TYPO3 Core encourages people to use custom CTypes in favor of list_type (moving towards a unifieid Content Block concept), this change will also be available for 11.5. Resolves: #98960 Releases: main, 11.5 Change-Id: Iee5e1a35f2d99faf03081d7265c2fe6e4845397f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76319 Tested-by:
-
Frank Naegler authored
This patch adds a new TCA field control "passwordGenerator" for TCA type "password", which can be used to generate a random password, based on defined password rules. The field control will be used in EXT:reactions the first time. In the future the field control might be combined with the existing password policies functionality. Therefore, most of the new functions and classes are marked as internal for now. Another feature to be added in the future will be (according to #69190) a modal / wizard, which will allow to change rules for the password to be generated. Resolves: #98540 Related: #98373 Releases: main Change-Id: Iab21b8bd0b3c261a702234579f62ba841c54ea0d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76002 Tested-by:
-
Christian Kuhn authored
Switch the Extbase BackendConfigurationManager to use the new TypoScript parser. The implementation is quicker for Extbase Backend modules. Change-Id: Icb821fbe8804f219806abc5094ace3d404b96a73 Resolves: #99017 Related: #97816 Releases: main Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76447 Tested-by:
-
Andreas Fernandez authored
Resolves: #99018 Releases: main Change-Id: I7d45a2087255b9a0102db31f5718b8d9cb959b6c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76458 Tested-by:
-
Oliver Klee authored
Used command: > Build/Scripts/runTests.sh -s phpstanGenerateBaseline Resolves: #97420 Releases: main Change-Id: Id1ea668b1f313fa74292437755850eaa36511526 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74344 Tested-by:
-
Torben Hansen authored
Resolves: #98828 Releases: main Change-Id: I1adc2913954610fe678ce5a76a6b3020705f35da Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76438 Tested-by:
-
Torben Hansen authored
Resolves: #98829 Releases: main Change-Id: Ica7171dd9cfd4045d8f712315178f745ffeb16b8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76437 Tested-by:
-
Achim Fritz authored
Remove doktypes in page tree toolbar when not set in TCA items to prevent an undefined array key PHP 8 warning. Resolves: #99012 Releases: main, 11.5 Change-Id: I0fc98e448aca70dc85f671a68d68d63bba15a166 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76452 Tested-by:
-
Michael Telgkamp authored
Resolves: #99016 Releases: main Change-Id: I020558bcbeb635d3b330f71cc840f1e35450853d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76455 Tested-by:
Chris Müller <typo3@krue.ml> Tested-by:
Lina Wolf <112@linawolf.de> Reviewed-by:
-
