- Feb 19, 2024
-
-
Johannes Nielsen authored
Add the configuration to the "Full" RTE preset, and also include some modules that missed in Full preset since #102099. npm install --save @ckeditor/ckeditor5-font@41.1.0 npm run build Resolves: #100847 Releases: main, 12.4 Change-Id: Iaa56d48e043397aefb902b6c9a5afbfcc453ae74 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/79006 Tested-by:
core-ci <typo3@b13.com> Reviewed-by:
Torben Hansen <derhansen@gmail.com> Tested-by:
David Bruchmann <david.bruchmann@gmail.com> Reviewed-by:
Benjamin Franzke <ben@bnf.dev> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Guido Schmechel <guido.schmechel@brandung.de> Reviewed-by:
-
- Feb 18, 2024
-
-
Chris Müller authored
Resolves: #103145 Related: #102628 Releases: main Change-Id: Ib629563e5289e2dc459b042fe8c5fb7c54beb829 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83029 Reviewed-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
Garvin Hicking <gh@faktor-e.de> Tested-by:
-
Chris Müller authored
Additionally, avoid double "see" in consecutive sentences. Resolves: #103146 Related: #102875 Releases: main Change-Id: If01e516c07c523dbb4dc7b6acb9cf487c4e6edf0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83030 Tested-by:
Stefan Bürk <stefan@buerk.tech> Reviewed-by:
-
- Feb 17, 2024
-
-
Stefan Bürk authored
New core-testing-* images have been build and published in the TYPO3 testing-infrastructure repository and pulled to the core ci gitlab runner instances. [1] This change modifies `Build/Scripts/runTests.sh` to set new image version to ensure the usage for all changes based on this change. For information what changed in the image see the patches in the testing-infrastrucure repository linked below. * core-testing-php82 => 1.11 * core-testing-php83 => 1.12 [1] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/072687df3a90e808143b3eded59176ee593e8112 Resolves: #103143 Releases: main, 13.0, 12.4, 11.5 Change-Id: Ia0ec77beb11e3f24614a0f5b531799494c1af988 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83028 Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Tested-by:
-
Benjamin Franzke authored
CKEditor5 renders tablecaptions as figcaption elements, therefore we allow them to be included in RTE and in frontend rendering. Resolves: #101874 Releases: main, 12.4 Change-Id: I0d1c05b2d8a35d765e64713741a0ab05a5aa1a5c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82185 Reviewed-by:
Andreas Kienast <a.fernandez@scripting-base.de> Reviewed-by:
-
- Feb 16, 2024
-
-
Christian Kuhn authored
This `@internal` property and method is another "has never been used" detail: It dates back to very early TYPO3 versions and TER reveals not a single usage. In case there are still extensions dealing with that public property, it should be possible to use hook 'processDatamap_postProcessFieldArray' instead, which is dispatched within process_datamap() a couple of lines later. Resolves: #103137 Releases: main Change-Id: If849f3f36aa160f8c467907b338aed27c7ef94eb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83020 Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
Christian Kuhn authored
Some cleanup of the class with obvious things: * Add ConnectionPool, CacheManager and runtime cache as property, created in __construct(), can be DI later. * Remove unused getResourceFactory(), remove getCacheManager() and getRuntimeCache() since they are properties now. * Add type hints to most properties: Those that can be set without headaches since DH would crash if they'd not be of that type, or other obvious reasons. * Turn a protected magic-string property into a constant and add another related constant to avoid a magic-string in code. * Add a series of method return types: Obvious ones where the method clearly can't return something else. * Minor comment spelling improvements. Change-Id: I117548d2ed44236208063774680079578e8392b5 Resolves: #103135 Releases: main Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83019 Reviewed-by:
-
Oliver Bartsch authored
Since FileInterface->getPublicUrl() might return `NULL`, corresponding constructor arguments are updated to now expect `?string`. Resolves: #103051 Releases: main, 12.4 Change-Id: I8d16c6b9361694733dc2c5c4b2e69693fe25cff4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83011 Reviewed-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
-
Andreas Kienast authored
In v11, extension authors were able to enhance the site configuration "TCA" with richtext fields. Since v12, this is not possible anymore due to the missing `backend.form` imports, required to load necessary JavaScript modules tagged as such. This commit adds the missing instruction, allowing to make use of ckeditor and related modules again. Resolves: #103115 Releases: main, 12.4 Change-Id: I2fb6d6b917ee99d9616593f118daa72d3f3a460b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83000 Reviewed-by:
-
Oliver Bartsch authored
To allow `BackendUtility::getProcessedValue()` to properly resolve the labels for select options, added via TSconfig, the `pid` is now provided by `StandardContentPreviewRenderer`. Resolves: #103076 Releases: main, 12.4 Change-Id: I20777ae532b66800ea61143e1824c895c7673042 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83008 Tested-by:
Jochen Roth <rothjochen@gmail.com> Reviewed-by:
-
Christian Kuhn authored
Similar to #103132. This time, public `@internal` property $data_disableFields is only read, but never written. Reading the property comment, it looks as if this may have been used as a detail scenario within ext:impexp that has been removed long ago. History reveals no core usage since ever: That property hasn't even been used with Kaspers initial commit in 2003. Let's drop this artifact and keep it in versioning museum forever. Resolves: #103133 Related: #103132 Releases: main Change-Id: I2bfddad06f2cbb2610fb55f67a9dda40d75ab7e8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83016 Tested-by:
Simon Schaufelberger <simonschaufi+typo3@gmail.com> Tested-by:
-
- Feb 15, 2024
-
-
Christian Kuhn authored
In this episode of 'Cracking the Cryptic' we are looking at the DataHandler puzzle ;) Let's get some obvious things done, first: Protected property DataHandler->remapStackChildIds is only written but never read. Remove property and protected addNewValuesToRemapStackChildIds() with all its callers to reduce complexity a bit. Resolves: #103132 Releases: main Change-Id: I914ae36875906acc8e39799e640899116b3206ee Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83015 Tested-by:
-
Andreas Kienast authored
Resolves: #103131 Releases: main Change-Id: I19617a4b2610bd622a887c0a2c1b974ca7617d01 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83014 Reviewed-by:
-
Christian Kuhn authored
Argument 3 $data of `checkRecordUpdateAccess()` is funny: It is only used if argument 4 is given as well. This is only done in method `process_datamap()`, so `checkRecordUpdateAccess` hook method is only triggered from within that method. This situation allows us to move the hook call into `process_datamap()` directly, making it more obvious it's only triggered by that `main` method. This allows us to get rid of arguments 3 and 4. Also point out a logical issue within the method. Resolves: #103126 Releases: main Change-Id: I4f4b2711784c005ed312ca491775c3e1d39b35d3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83010 Tested-by:
-
Christian Kuhn authored
There is no point to substitute GU::trimExplode() of the rather short TCA 'eval' string by substituting it with an md5() operation plus runtime cache object operations. Both things are most likely similarily quick, and the time consumed by queries in DH is multiple orders of magnitude bigger than this simple operation, a difference is not measurable. Let's thus simplify the code a bit. Resolves: #103125 Releases: main, 12.4 Change-Id: I474d3fbe6b503a99a9129856b0f59c777b171844 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83007 Tested-by:
Stephan Großberndt <stephan.grossberndt@typo3.org> Reviewed-by:
Markus Klein <markus.klein@typo3.org>
-
Oliver Bartsch authored
The EXT:form "version2" is using bootstrap 5, which requires <select> elements to use the `form-select` class. This is now fixed for corresponding form elements. Resolves: #103117 Releases: main, 12.4 Change-Id: I712cecfa4c5ac8facc84bc3cf0f742867ecc9613 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83002 Tested-by:
-
Torben Hansen authored
Install tool suggests to set `$GLOBALS['TYPO3_CONF_VARS']['GFX']['processor_colorspace'] = sRGB` if images appear too dark. In general this is the correct suggestion, but the value must be quoted. This change adds the missing single quotes for the value. Resolves: #103124 Releases: main, 12.4 Change-Id: I2e1fd2ebebf1d67870145df29ec0e40b330a5065 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83005 Tested-by:
-
- Feb 14, 2024
-
-
Oliver Bartsch authored
Since the node is `collapsed` on initial rendering, the `aria-expanded` attribute is set to "false". Resolves: #103119 Releases: main Change-Id: Ia06d0a268cf572453b17f5bd332e7d482019b561 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82997 Tested-by:
-
Oliver Bartsch authored
Due to the previously used pagination, the "items per page" option has been reset when searching in the record list. However, since the "new" pagination is able to handle such filtered list, resetting the "items per page" option is no longer necessary and therefore makes lists with a lot of matched items usable again. Resolves: #103107 Releases: main, 12.4 Change-Id: Ibeb5a65666a3796f98d3dd61c9efc0bd3bfb0c72 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82998 Tested-by:
-
Stefan Bürk authored
With #103015 the table definition merge has been moved to an earlier point, providing an associative array with the table definitions. This change modifies `DefaultTcaSchema` to operate on that array and simplifies the required handling code. More precise doc-block annotations for humans and PHPStan are added along the way. Resolves: #103016 Related: #103015 Related: #103014 Releases: main Change-Id: I7d2120ee836854b2fa9072e44444e7387873bd2e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82760 Tested-by:
-
Nikita Hovratov authored
The BootCompletedEvent receives the constructor argument `$cachingEnabled`. However, the variable `$disableCaching` was passed in Bootstrap::init() which is the exact opposite. In fact, the caching is logically always enabled when reaching the dispatched event. Resolves: #103114 Releases: main, 12.4 Change-Id: I81c26027bb8e2cb4009fbfcd0bfd6015bd9c1dec Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82993 Reviewed-by:
-
Oliver Bartsch authored
It's now possible to use a TCA type `group` field as `foreign_selector` together with the `useCombination` functionality. The corresponding "child child table" information is in this case fetched from the `allowed` option. Side note: Using TCA type `group` for a `foreign_selector` field is not really documented, but it's also not forbidden. Actually, it's a valid use case and also working quite well as the new styleguide examples demonstrate. However, the documentation should be adjusted to mention that only one table can be defined in `allowed` for such fields. Resolves: #102904 Releases: main, 12.4 Change-Id: Icdde6a8acb1fb9166da8e6259758f6bf64d6c41f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82721 Tested-by:
-
Garvin Hicking authored
The original patch in [1] wrongly stated that the column type was changed to "bigint unsigned", when in fact it is "bigint signed" (to allow dates before 1970). This documentation mistake is now fixed. [1] https://review.typo3.org/c/Packages/TYPO3.CMS/+/80668 Resolves: #103113 Releases: main Change-Id: Iff9b1cc00a040c4315ce3ee13bb6bd93afb97fb0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82992 Reviewed-by:
-
- Feb 13, 2024
-
-
Andreas Kienast authored
This commit updates ckeditor5 to v41.1. See changelog at https://github.com/ckeditor/ckeditor5/releases/tag/v41.1.0. Executed commands: npm i --save \ @ckeditor/ckeditor5-alignment@^41.1.0 \ @ckeditor/ckeditor5-autoformat@^41.1.0 \ @ckeditor/ckeditor5-basic-styles@^41.1.0 \ @ckeditor/ckeditor5-block-quote@^41.1.0 \ @ckeditor/ckeditor5-clipboard@^41.1.0 \ @ckeditor/ckeditor5-code-block@^41.1.0 \ @ckeditor/ckeditor5-core@^41.1.0 \ @ckeditor/ckeditor5-editor-classic@^41.1.0 \ @ckeditor/ckeditor5-engine@^41.1.0 \ @ckeditor/ckeditor5-essentials@^41.1.0 \ @ckeditor/ckeditor5-find-and-replace@^41.1.0 \ @ckeditor/ckeditor5-heading@^41.1.0 \ @ckeditor/ckeditor5-horizontal-line@^41.1.0 \ @ckeditor/ckeditor5-html-support@^41.1.0 \ @ckeditor/ckeditor5-indent@^41.1.0 \ @ckeditor/ckeditor5-link@^41.1.0 \ @ckeditor/ckeditor5-list@^41.1.0 \ ...
-
Christian Kuhn authored
The database column defined by TCA ctrl 'origUid' ('t3_origuid') had a bumpy ride over the years. It was mostly obsoleted in v8 with the introduction of 'translationSource' ('l10n_source'). A patch to fully remove it with #88495 has been reverted with #88501, leaving the field in limbo. The only remaining "true" usage of 'origUid' is in an inline relation scenario in DataMapProcessor when an inline parent *is* localizable (TCA ctrl 'languageField' and 'transOrigPointerField' set), but a child *is not*: Due to the copy strategy of all inline children upon localization of a parent record, the core needs to know if a child exists already or needs to be created. 'origUid' then stores the uid of the default language child. A couple of tests refer to this scenario as "monoglot" children. We could potentially get rid of that scenario by postulating that an inline child has to be localizable as well if the parent is, but that decision can be taken later. The patch does not touch this scenario, but looks at 'origUid' from a different perspective: If a table *is* localizable, or is not used as inline child, then 'origUid' is not needed. The patch thus removes TCA ctrl 'origUid' from TCA tables, keeping it only in the test scenario extensions 'test_irre_csv', 'test_irre_foreignfield' and 'test_irre_foreignfield_non_ws'. The bulk of the patch is about removing 't3_origuid' from the functional test .csv fixture files, while the most important TCA changes are dropping ctrl 'origUid' from table 'pages' and 'tt_content'. Resolves: #103099 Related: #79856 Related: #88494 Related: #88495 Related: #88501 Releases: main Change-Id: I622afde74294c389639974d312f121d0a6466b60 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82888 Tested-by: -
Stefan Bürk authored
The constant editor has been revamped with #98357 using the new TypoScript parser introduced with TYPO3 v12 under the hood. For category and subCategory handling lower-cased keys have been used, missing to lower-case the custom categories and subcategories names (keys) integrator are able to add since aeons. That leads to a failing match later on, and adding constants to the generic `other` subcategory. The revamped code supports only one category per subCategory sorting value. The documentation say that this **should** be omitted, but it worked in the past and broke with the revamped implementation. This change fixes muliple issues with the constant editor: * Ensure that custom categories and subcategories are read lower-case, otherwise later lookup will fail and sorted into sub-categorie `other`. * Add addtional array level to have `subCategory->items` per second sorting value as array (to avoid overriding). * Add additional item loop to the fluid template to respect the additional array level. Note: In the past it was possible to display a constant in multiple categories/subcategories by adding them again with different category configure comment lines. This is not supported anymore and not considered as bug. Resolves: #103088 Related: #98357 Related: #97816 Releases: main, 12.4 Change-Id: I4403420cc957cdef4bf077365deac0f7af621c71 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82898 Tested-by:
Thomas Anders <me@naderio.de> Tested-by:
-
Oliver Hader authored
Write access to table `sys_file` is denied per default, unless data is being imported. In addition, write access to related FAL entities `sys_file_reference` and `sys_file_metadata` is denied in case a file on legacy storage (uid=0) is used or corresponding user does not have permissions to access a particular file. Resolves: #93969 Releases: main, 13.0, 12.4, 11.5 Change-Id: Ic8ac7132d732bd117aa63f6a33545ceb1d1f421d Security-Bulletin: TYPO3-CORE-SA-2024-006 Security-References: CVE-2024-25121 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82962 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
Benjamin Franzke authored
Resolves: #93571 Releases: main, 13.0, 12.4, 11.5 Change-Id: I9622bfa47ef9637cecaff4a790f742445f598682 Security-Bulletin: TYPO3-CORE-SA-2024-005 Security-References: CVE-2024-25120 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82961 Reviewed-by:
-
Benjamin Franzke authored
The encryptionKey is a secret that must never be sent within any request, therefore it is now dropped from the editing interface in "Configure Installation-Wide Options". The log file writer has been adapted to be aware of the fact that the encryption key might not be set when TYPO3 has not yet been installed (which is the case when `vendor/bin/typo3 setup` is executed). Resolves: #103046 Releases: main, 13.0, 12.4, 11.5 Change-Id: I260a8a2e9af29908543dfe48ac3658d8c45cc440 Security-Bulletin: TYPO3-CORE-SA-2024-004 Security-References: CVE-2024-25119 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82960 Tested-by:
-
Oliver Hader authored
Backend form fields of TCA `type=password` should never expose the persisted value - especially, in case the value is explicitly configured not to be hashed (having TCA `hashed=false`). Resolves: #101965 Releases: main, 13.0, 12.4, 11.5 Change-Id: Ie05a708185c621b8a2120ad7851ac4caf180893f Security-Bulletin: TYPO3-CORE-SA-2024-003 Security-References: CVE-2024-25118 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82959 Tested-by:
-
Benjamin Franzke authored
Resolves: #102799 Releases: main, 13.0, 12.4, 11.5 Change-Id: I673b6fbac853b0a977a5e5833a683c6952a55458 Security-Bulletin: TYPO3-CORE-SA-2024-002 Security-References: CVE-2024-22188 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82958 Reviewed-by:
-
Oliver Hader authored
The File Abstraction Layer Local Driver did not verify whether a given absolute file path is allowed, and made it possible to access files outside of the project path, and to by-pass the setting in $GLOBALS['TYPO3_CONF_VARS']['BE']['lockRootPath']. In case lockRootPath is not set, any local file path must be at least located in the base directory of the current project. The lockRootPath setting now supports array values as well. The trailing slash is enforced automatically. Example: * instead of 'lockRootPath=/var/spe' previously matching the paths '/var/specs/' and '/var/specials/, * now both paths need to be declared explicitly, since 'lockRootPath=/var/spe' is evaluated as '/var/spe/' Resolves: #102800 Releases: main, 13.0, 12.4, 11.5 Change-Id: I6561df562c5dbaff1f77d33db24d5f1c6358b198 Security-Bulletin: TYPO3-CORE-SA-2024-001 Security-References: CVE-2023-30451 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82957 Reviewed-by:
-
Benjamin Kott authored
The style guide should aid in testing and constructing backend components. In this change, we're removing the mandatory light mode for examples to enhance visibility of adjustments within sub-components. Resolves: #103093 Releases: main Change-Id: Ia838d75fdaccb48e4f43a0cdd9fa31e309603d2b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82879 Tested-by:
-
Benjamin Franzke authored
The autocomplete="off" parameter is ignored by current browsers, autocomplete="new-password" is to be used for disable autocompletion. The explicit request for autocompleting the password is autocomplete="current-password", which is now used in case config TCA autocomplete is set. See following article for more information: * https://web.dev/articles/sign-in-form-best-practices#new-password * https://web.dev/articles/sign-in-form-best-practices#current-password Resolves: #103067 Related: #97104 Releases: main, 12.4 Change-Id: Ice3c7a50020d7e17b14c51dc89c1c8e1700fe9a6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82830 Reviewed-by:
-
Stefan Bürk authored
A new PHPStan version has been released, which is pulled in automatically in the composerInstallMax nightly test. The higher version allows to remove a ignore pattern from the baseline and a superfluous key unset is detected. This change raises the PHPStan version, removes the superfluous `unset()` and regenerates the baseline to remove the invalid ignore pattern. Used command(s): > Build/Scripts/runTests.sh -s composer \ -- require --dev "phpstan/phpstan":"^1.10.58" > Build/Scripts/runTests.sh \ -s phpstanGenerateBaseline Resolves: #103105 Releases: main, 13.0, 12.4 Change-Id: I689079eaac7f9461084e6a71ff08ef716cf551e4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82932 Reviewed-by:Anja Leichsenring <aleichsenring@a...>
-
- Feb 12, 2024
-
-
Oliver Hader authored
Executed command: composer update composer/composer see https://github.com/advisories/GHSA-7c6p-848j-wh5h Resolves: #103102 Releases: main, 13.0, 12.4, 11.5 Change-Id: Ib3a0baa5c94f0a19b36b8440a30f47f25eab6e65 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82899 Tested-by:
-
Oliver Bartsch authored
This fixes several bugs in FileList: 1. Properly initializing the `searchTerm` ensures it is kept while sorting. 2. Sorting for "filesize" is now working properly, using corresponding collator attribute. 3. Pagination is properly reset on searching. 4. Correct search term is kept on paginating. Resolves: #103053 Releases: main, 12.4 Change-Id: Ibf7dd278d13aed6142286d7408b9380588485801 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82826 Reviewed-by:
Sybille Peters <sypets@gmx.de> Tested-by:
-
Sybille Peters authored
Since the linktypes are automatically registered in Linkvalidator, it is no longer quite as easy to replace the "external" linktype. You cannot register another linktype using the same identifier "external", so a different identifier must be used. A minimal example is added to the developer section in the documentation. Resolves: #101673 Related: #96935 Releases: main, 12.4 Change-Id: I9afa1a77fe56675dff2dbc1bacc3635b1b9b36c6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82894 Reviewed-by:
Chris Müller <typo3@krue.ml> Tested-by:
-
- Feb 11, 2024
-
-
Oliver Bartsch authored
The query for fetching extension versions is extended to also find "outdated" extension versions (review_state = -2). Note: For now, this does not change anything in the EM, since the remote XML does not use the -2 state currently, due to the wrong constraint. This can however now be properly fixed in XML. Resolves: #93082 Releases: main, 12.4, 11.5 Change-Id: I522a2c166c6d1af6e8b2a14de51d63a15c4211d2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82821 Tested-by:
-
Torben Hansen authored
The language labels for `noPluginSelected` and `edit` in StandardContentPreviewRenderer can not be resolved, because the extension path is wrong. This change fixes the extension path and additionally streamlines one label output, by using `htmlspecialchars` to escape the generated label similar to the other label output in this class. Additionally a similar wrong extension path in `ExampleLinkType.rst.txt` has been adapted. Resolves: #103095 Related: #100675 Releases: main, 12.4 Change-Id: I4882133025c938fc3b6928b36237e782e9465dcc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82884 Tested-by:
-
