- 11 Jan, 2022 1 commit
-
-
Change-Id: Ia82e7fc67597b331ddb8f7eb35afb0598899a397 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72958 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
-
- 10 Jan, 2022 10 commits
-
-
When using a composer-based installation, public frontend assets such as JavaScript of stylesheet files are exposed in a dedicated `_assets/` folder. In those scenarios TypoScript settings for `config.absRefPrefix` need to be applied as well. Resolves: #96452 Releases: main, 11.5 Change-Id: I0695850be18c9c152c647883c122a0680e8e734f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72954 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Andreas Fernandez authored
The maintainer of the `colors` package decided to rampage and released a bonkers version, see [1] and [2], causing an implosion of the npm eco system. Albeit TYPO3 uses this as a transitive dependency only, we're going to be safe and enforce this package to version 1.4.0, the current known to-be-stable version. [1] https://github.com/Marak/colors.js/issues/285 [2] https://www.bleepingcomputer.com/news/security/dev-corrupts-npm-libs-colors-and-faker-breaking-thousands-of-apps/ Resolves: #96499 Releases: main, 11.5, 10.4 Change-Id: Ic8ad9105c9a9bc45bb2519547bb044be672db27c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72951 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
-
This restores the sort link for columns with "special" label, such as "tstamp" or "crdate". Resolves: #96489 Releases: main, 11.5 Change-Id: Iae7c9d2056256df5156f6fe8773d6b18e7ba8898 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72927 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Benni Mack <benni@typo3.org> Reviewed-by:
-
Update to CKEditor v4.17.1 which addressed browser compatibility issues and known security vulnerabilities: https://ckeditor.com/cke4/release-notes Commands: rm -r typo3/sysext/rte_ckeditor/Resources/Public/JavaScript/Contrib cd Build yarn add 'ckeditor4@^4.17.1' yarn build Resolves: #96494 Releases: main, 11.5, 10.4 Change-Id: I87039f5a5d1fe7488f6d4c5d0c36e90421d4c93e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72929 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Benni Mack authored
Some code in HMENU stems back from TYPO3 v3.x days, and this code aims to streamline the functionality given current functionality. HMENU now has its own sys_page object, which should be used. In addition, HMENU should fetch TSFE->id consistently across all its code base. Resolves: #96492 Releases: main, 11.5 Change-Id: I971a5958417077d51ea5c5070fc4b9ef513cd738 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72928 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Update to @claviska/jquery-minicolors v2.3.6 which addressed known security vulnerabilities: https://security.snyk.io/vuln/SNYK-JS-CLAVISKAJQUERYMINICOLORS-1930824 https://github.com/claviska/jquery-minicolors/releases/tag/2.3.6 Commands: cd Build yarn add '@claviska/jquery-minicolors@^2.3.6' yarn build Resolves: #96495 Releases: main, 11.5, 10.4 Change-Id: Iaafdd29dd50a18321746fb36702702302078fceb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72926 Tested-by:
Benjamin Franzke <bfr@qbus.de> Tested-by:
core-ci <typo3@b13.com>
Reviewed-by: -
Oliver Bartsch authored
The linkvalidator module shows the path to the page, a broken link is on. Since editors might only have access to a subtree (mount point), the corresponding parent pages should not be displayed. This is now fixed by providing the necessary permission clause to `getRecordPath` in LinkValidatorController. Resolves: #92539 Releases: main, 11.5 Change-Id: Ibdb54560561dba5d7ad932d89ff5b73fc558f5f2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72941 Tested-by:
core-ci <typo3@b13.com>
Tested-by: 
Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de> -
Oliver Bartsch authored
Resolves: #96481 Releases: main, 11.5 Change-Id: I41eeb4ecf0b90e998875701131b2c8a35bfa3225 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72925 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de> -
Benni Mack authored
This change uses typolink in EmailViewHelper, allowing to also use typolink hooks or custom Email Link Builder to be used consistently across TYPO3 Core (e.g. using the same hooks for all email link generation in the Frontend). Resolves: #96483 Releases: main, 11.5 Change-Id: Ia573dc5a7ebb9ca7f0f0b6b35126bd789f86a627 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72924 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Benni Mack authored
During the main work of TYPO3 v9 when Site Handling was introduced, the Page Link Builder turned into a single monster-method. Now, that most bugs are solved and we have a very good test coverage for this, this change splits several functionality into smaller methods, allowing for better readability, extensibility and further refactoring. Extending PageLinkBuilder now is much easier to replace a certain part of the existing functionality (also via XCLASS). Resolves: #96484 Releases: main, 11.5 Change-Id: I231cf3c13ec15dd1ad99f710ca27ce340c0deee2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72923 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 08 Jan, 2022 1 commit
-
-
Releases: main, 11.5 Resolves: #96488 Change-Id: I0ced03e4d551048414022214b832b3ceeb51400d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72922 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
- 07 Jan, 2022 6 commits
-
-
The scenario provided by tables tx_irretutorial_mnasym_* gets its own test extension and gets loaded where needed. Resolves: #96458 Releases: main, 11.5 Change-Id: I905bc6b7e33c54e343828f9569624fdd60042c2d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72921 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Benjamin Franzke authored
User supplied strings must not be concatenated into the format parameter of sprintf() as sequences like %s, or (more likely) %20S (which is ' S' url escaped) may be contained and cause warnings because sprintf() expects additional arguments in that case. Streamline to always use the static '%s: "%s"' format instead. Releases: main, 11.5, 10.4 Resolves: #96478 Change-Id: Ic3b09c6e1e7c617e78ea405289680bd78d0aab64 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72920 Tested-by:
core-ci <typo3@b13.com>
Reviewed-by: -
This patch adds a check to detect self referencing redirects, thus avoiding them and instead log an error in the corresponding frontend redirect middleware. Furthermore, add a bunch of tests along the way to cover this change and the different constellations, for example not avoiding redirect with the same path but external host. Resolves: #96427 Releases: main, 11.5, 10.4 Change-Id: I554ba51b53065dd754068e379f69c2a5dffc3054 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72918 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech> Tested-by:
-
Oliver Bartsch authored
Resolves: #96479 Releases: main, 11.5 Change-Id: I8f054a9dd38e8b25ac606c002f95cb673e4e280c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72919 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de> -
Sorting query results by text columns may require a filesort on harddisk which is slow. To boost up the search results of LiveSearch we have added an ORDER BY uid DESC to always show the newest created records first. Column "uid" exists in all TCA tables and as it is PRIMARY INDEX sorting will happen in memory. Resolves: #96365 Releases: main, 11.5 Change-Id: Icbf6e8c7717a495aaee995ff09cf2cd882173e65 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72917 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
In #87992 an early return was added to have <a> tags with just an "id" or "name" attribute. This is all nice, but when used further typolink settings (such as userFunc or custom "title"), these options were never run. This change now uses typolink() natively again and removes the introduced "resolveAnchorLinK" workaround. Added tests show that additional attributes are executed and links without href are actually created (was previously untested). Resolves: #96464 Related: #87992 Releases: main, 11.5 Change-Id: I67d4090228684fc89f72bc3d6367109437040ccf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72916 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de>
-
- 06 Jan, 2022 7 commits
-
-
Benni Mack authored
This change mainly adds tests for showing that the global TypoScript option config.ATagParams = tabindex="20" can be used and any given attributes are actually overridden if using typolink.ATagParams = tabindex="13". Resolves: #71703 Releases: main, 11.5 Change-Id: I984d66ecf7c303381e64e447a0cac731f055a567 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72915 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Benni Mack authored
When having a page of type "External URL", set to an email address, and config.spamProtectEmailAddresses = ascii set in TypoScript, the encoding now works properly. Resolves: #87787 Releases: main, 11.5 Change-Id: I15563f08a8a0007dc292f5d7e1a311e38a55db26 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72914 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Broken links are marked in RTE by using the attribute data-rte-error in the <a> tag, which results in a special style and lets the link be visible as broken. Previously this was not done for links to hidden pages and links to content elements. These links were however detected as broken by linkvalidator and displayed in the list of broken links. Marking them in RTE as well makes the behaviour consistent. This patch ensures the consistency between the list and the visual highlighting in RTE elements for links to hidden pages and hidden content elements. Highlighting links to hidden pages/content elements on hidden pages may be visually relaxed to a notice instead of an error in a dedicated patch as feature. One PHP8.0 array key warning is fixed along the way. Resolves: #93005 Releases: main, 11.5 Change-Id: Ib1ef4b81ab862657950a38e5ee6847dd82abb13f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72913 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Benni Mack authored
TYPO3's "makelinks" functionality parses for in-text external URLs and mailto links. This change uses Typolink under the hood now to consistently check for invalid content, and have the chance to use all hooks in typolink for such links as well. This way, typolink is used, but makelinks is executed AFTER possible resolved <a> tags avoiding double-calling parseFunc when <a> tag processing is configured. Resolves: #93012 Releases: main, 11.5 Change-Id: I574915e715793f6eccad1bdfc216e82e329179dd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72912 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Benni Mack authored
This change now always checks for the actual page ID in the default language, not of the translated page to see if the page should be excluded. Resolves: #94427 Releases: main, 11.5 Change-Id: I89c67b7955ccb69af28accbcf573576156919481 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72891 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
The scenario provided by tables tx_irretutorial_mnattr_* gets its own test extension and gets loaded where needed. Resolves: #96459 Releases: main, 11.5 Change-Id: I48b08772f8c4d64f8a3ea930fc307a8d5d3f2189 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72890 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Merging #22190 shortly after #96470 has introduced a invalid test case expectation, which fails now core ci execution. This patch adds a missing 'target' expectation for the test added through #22190 to match introduced expectation with #96470. Resolves: #96472 Related: #22190 Related: #96470 Releases: main, 11.5 Change-Id: Ia92c71302a8d875b2b8f5c23aac97bfa7e3bfadc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72889 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de>
-
- 05 Jan, 2022 11 commits
-
-
This change adds tests to a very old issue to ensure that a page with only hidden subpages is not marked as IFSUB etc. MenuProcessor is extended to set a "hasSubpages" flag when IFSUB, CURIFSUB or ACTIFSUB is set. Resolves: #22190 Releases: main, 11.5 Change-Id: Ia9b73e8ae1028eafa94ba4fa5ca0dacf2562c074 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72888 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de> -
Benni Mack authored
The database field "pages.target" allows to define a custom target attribute for links in menus of external URLs. Before this was (wrongly) built in HMENU but applied after Typolink worked. This option belongs to the actual link building when building links to external URLs where $conf[extTarget] is evaluated. In addition, HMENU tests now also evaluate "target" for regular pages as well. Resolves: #96470 Releases: main, 11.5 Change-Id: I3919b6b13666565687e8ff56dcfc867c871837e2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72887 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Oliver Bartsch authored
With the introduction of the multi record selection, the workspace actions, shown above and below the records, got prepended with labels. While the mass action targets the entire workspace, the label just read "all", which is misleading because one could think the action only targets all records of the current view and then accidentally publish or even worse, discard the entire workspace. This is fixed by changing the label. Resolves: #96468 Releases: main, 11.5 Change-Id: Id2205e843656af7576f7038dddc81ae53308a185 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72886 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by: Oliver Bartsch <bo@cedev.de> -
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: -
We removed the SQL query on pages (column: pid) for TYPO3 administrators, because this group of people has access to all pages anyway. Especially in large TYPO3 instances the collection of all pages UIDs took a lot of time. Resolves: #96356 Releases: main, 11.5 Change-Id: I436e15e79ce590c4228b9a9034f83497fa1db92e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72884 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Once a user simulated a time with the admin panel, it has not been easy to see the status of the field or to understand how to disable it. To make it easier for the user to handle a separate checkbox has been added that allows enabling or disabling the simulate time feature. Resolves: #94596 Releases: main, 11.5 Change-Id: I309475f19f64dd8324f2466082d979d0afdbd501 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72883 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
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: -
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: -
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: -
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: 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:
-
- 04 Jan, 2022 4 commits
-
-
Ensure that in a foreign language context the selected option will be translated in the finishers. Regression fix introduced with #93979. Resolves: #96455 Related: #93979 Releases: main, 11.5 Change-Id: Ie6b33f70d6d9a19232821bda77e37b6f290ea061 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72859 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Jan Helke <jh@f7.de> Tested-by:
-
The scenario provided by tables tx_irretutorial_mn_sym_* gets its own test extension and gets loaded where needed. Resolves: #96445 Releases: main, 11.5 Change-Id: I55a9c3ba1a5e1d238279a641f4e5380d936c23c9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72876 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
Benjamin Franzke authored
With the changes in #95854, database mounts are no longer sorted by the order they are defined in the group/user settings, but undefined by the order the database returns. DB mounts aren't sorted against each other, that means sorting values are not meaningful anyway, and results in uncontrolable orderings. Explicitly preserve the order using usort(). Also revert groupAndSortPages() to the state prior to #95854, as the forcePid parameter would now be unused. Releases: main, 11.5, 10.4 Resolves: #96359 Related: #95854 Change-Id: I64b8d90c68246cc0ac01abcbf3678aa1055189e3 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72875 Tested-by:
core-ci <typo3@b13.com>
Tested-by: -
The frontend preview aspect may be set from the admin panel or the frontend extension or even from a third-party extension in a middleware. The previous implementation overwrote the preview settings on every initialisation, resulting in lost preview information. Instead of overwriting the setting, this change takes the current preview value into account - if the preview was enabled by a previous instance this is kept. Additionally, the logic to set the preview flag in both frontend and admin panel has been streamlined. Resolves: #91225 Releases: main, 11.5 Change-Id: I9f642bca1928638cac5eb5c1468710f5fad28137 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72872 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
