Review main Merged Breaking

91291[!!!][FEATURE] Enhance page type `Link` to fully support typolinks

Lina Wolf CR +2 V +2 Expert +1768 −257 updated 11/24/25, 16:27

Commit message

TYPO3 provided the two doktypes `External URL (3)` and `Shortcut (4)`,
which could be used to have a linkable page and define the target and
ease management of the link target in one place. The main difference
between both of them is, that `Shortcut` targeted only pages and the
`External URL` only external resources. Using it for internal sources
made it hard to maintain on changes of page slugs, routing configuration
and similar.

TYPO3 provides the powerfull `TypoLink` based field type allowing to
link and reference broad variaty of targets including records on their
related detail page, external urls, email (mailto), telephon or even
custom link handler implementations.

The former page type "External link" has been renamed to "Link"
and now fully supports all typolink capabilities making use of
the new `TCAtype=link` based field `pages.link` and removing
the now obsolete `pages.url` field. Upgrade wizard is provided
to migrate to the new field.

The new implementation can be used, for example, to configure pages
linking to:

* external URLs
* other pages
* content elements or sections
* files and folders
* email addresses
* telephone numbers
* custom records, for example news records

Corresponding message is displayed in the `Layout` module for `Link`
pages to state the configured link target without needing to open
page settings edit form.

Dropping the `pages.url` field to cleanup the pages table is the
real breaking part of this change, otherwise only internal API's
has been touched to implement the enhanced capability.

This change provides a long-time wished feature for `editors`.

Review

  • Code review CR +2 Done
    • Georg Ringer +2
    • Sven Liebert +1
  • Verified V +2 Done
    • Georg Ringer +2
    • Sven Liebert +1
    • core-ci +1 CI

Issues 6

Files 56

Show 36 more files

Review log 106157

Show 89132 earlier messages
  1. Lina Wolf uploaded patch set 1 10/27/25, 19:19

  2. Oli Bartsch commented on patch set 1 10/27/25, 19:25

    pages.php:266

    People might use this field for their own doktypes. Since we can not override the type for only the link doktype - due to columnsOverrides restrictions - we either should add a new field or this must be a breaking change.
  3. core-ci voted on patch set 1 V -1 10/27/25, 19:27 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87722

  4. Lina Wolf uploaded patch set 2 V -1 10/27/25, 19:57

  5. core-ci voted on patch set 2 V -1 10/27/25, 20:10 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87731

  6. Lina Wolf uploaded patch set 3 V -1 10/27/25, 20:22

  7. Lina Wolf uploaded patch set 4 10/27/25, 20:23

  8. Lina Wolf commented on patch set 4 10/27/25, 20:25

    pages.php:266 Reply

    Done
  9. Lina Wolf uploaded patch set 5 10/27/25, 20:29

  10. Oli Bartsch commented on patch set 5 10/27/25, 20:37

    pages.php:266 Reply

    Thanks. We now would need an upgrade wizard, migrating existing doktype records to copy the link to the new field.
  11. core-ci voted on patch set 3 V -1 10/27/25, 20:45 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87736

  12. core-ci voted on patch set 4 V -1 10/27/25, 20:46 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87737

  13. core-ci voted on patch set 5 V -1 10/27/25, 20:52 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87741

  14. Mathias Brodala commented on patch set 5 CR -1 10/28/25, 08:04

    PageLayoutController.php:398

    I wonder if this could be changed to simply call resolvePageLink() and check if the resulting URL is empty. This way we need to know about this structural detail only once.

    PageLayoutController.php:404

    Since it's typolink now, it doesn't need to be a page link. It could also be mailto, file, an arbitrary record, etc. The naming should reflect that.

    PageLayoutController.php:407

    No external URL anymore, the naming should reflect that.

    locallang_layout.xlf:292

    This should keep saying "URL". The "target" can be interpreted as link "target" attribute.

    tsref.xml:3540

    > 3 (Link) and 4 (Shortcut) Let's make this clearer while we're at it.

    ShortcutAndMountPointRedirect.php:89

    Do we really need all this post-processing? Why not directly redirect to the URL?

    ShortcutAndMountPointRedirect.php:93

    It feels like we're repeating existing logic here.

    ShortcutAndMountPointRedirect.php:110

    Links to mail/phone may be valid. In navigation rendering definitely, on access depending on the context.

    PageLinkBuilder.php:213

    This should be moved after the following condition, otherwise it's stored pointlessly on error.

    PageLinkBuilder.php:215

    > on It's the link "on" this page.
  15. Lina Wolf uploaded patch set 6 CR -1 V -1 10/28/25, 08:16

  16. core-ci voted on patch set 6 V -1 10/28/25, 08:32 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87766

  17. Lina Wolf uploaded patch set 7 V -1 10/28/25, 08:42

  18. Lina Wolf commented on patch set 7 10/28/25, 08:45

    PageLayoutController.php:398 Reply

    Done

    PageLayoutController.php:404 Reply

    It is a page of type link and it gets resolved.

    PageLayoutController.php:407 Reply

    Done

    ShortcutAndMountPointRedirect.php:89 Reply

    Yes, as internal and external redirects receive different status codes and additional information, Compare how currently external link and shortcut handle redirects

    ShortcutAndMountPointRedirect.php:93 Reply

    Where did you find the same logic?

    ShortcutAndMountPointRedirect.php:110 Reply

    On menu rendering they are output, however, when you attemp to open the page directly you get a 404 just like you would with a Sysfolder

    PageLinkBuilder.php:213 Reply

    I dont really get your comment?
  19. core-ci voted on patch set 7 V -1 10/28/25, 08:57 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87768

  20. Lina Wolf commented on patch set 7 10/28/25, 09:14

    locallang_layout.xlf:292 Reply

    Done

    tsref.xml:3540 Reply

    Done

    PageLinkBuilder.php:215 Reply

    Done
  21. Lina Wolf uploaded patch set 8 V -1 10/28/25, 09:15

  22. Lina Wolf uploaded patch set 9 10/28/25, 09:22

  23. Lina Wolf commented on patch set 9 10/28/25, 09:24

    pages.php:266 Reply

    Done
  24. Mathias Brodala commented on patch set 9 10/28/25, 09:34

    PageLinkBuilder.php:213 Reply

    If $url is empty then $linkResultType is not used anymore. So it should be set after the check instead.
  25. core-ci voted on patch set 8 V -1 10/28/25, 09:41 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87776

  26. core-ci voted on patch set 9 V -1 10/28/25, 09:46 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87780

  27. Lina Wolf uploaded patch set 10 V -1 10/28/25, 15:43

  28. core-ci voted on patch set 10 V -1 10/28/25, 15:56 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87854

  29. Lina Wolf uploaded patch set 11 V -1 10/28/25, 16:06

  30. Benni Mack commented on patch set 11 10/28/25, 16:13

    I just bricked my system by building a simple loop over two pages pointing at each other now. Out of memory - PHP limit.
  31. Benni Mack commented on patch set 11 10/28/25, 16:15

    Reply

    If i create a link to one of these pages (e.g. in the menu) the page is also not stopping to be created.
  32. core-ci voted on patch set 11 V -1 10/28/25, 16:25 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87858

  33. Lina Wolf commented on patch set 11 10/28/25, 16:42

    Reply

    So the link page type has always been a "stupid" link, if you have linked to the page itself you would receive an infinite loop. Should we test this and to what level? Only for links of type page or also for external links that resolve to the current site? Or those that are forwarded via httaccess to my current site? There is like an almost infinitive possibility to create infinitive loops, no?
  34. Benni Mack commented on patch set 11 10/29/25, 08:11

    Reply

    we need to have a loop detection. doktype=shortcut has a loop detection of depth=20, I think that's be sufficient.
  35. Lina Wolf uploaded patch set 12 V -1 10/29/25, 09:04

  36. Lina Wolf marked it work in progress 10/29/25, 09:08

  37. core-ci voted on patch set 12 V +1 10/29/25, 09:14 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87917

  38. Lina Wolf commented on patch set 12 10/30/25, 07:12

    This change is ready for review.

    PageLinkBuilder.php:213 Reply

    Done
  39. Lina Wolf marked it work in progress 10/30/25, 07:27

  40. Lina Wolf uploaded patch set 13 V +1 10/30/25, 11:28

  41. core-ci voted on patch set 13 V -1 10/30/25, 12:29 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88120

  42. Lina Wolf uploaded patch set 14 V -1 10/30/25, 12:59

  43. Lina Wolf commented on patch set 14 10/30/25, 13:00

    This change is ready for review.

    Reply

    It is resolved, also when shortcuts link to page links and vice versa

    ShortcutAndMountPointRedirect.php:93 Reply

    Done
  44. Lina Wolf commented on patch set 14 10/30/25, 13:00

    Reply

    Done
  45. core-ci voted on patch set 14 V -1 10/30/25, 13:16 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88139

  46. Lina Wolf uploaded patch set 15 V -1 10/30/25, 14:02

  47. Mathias Brodala commented on patch set 15 10/30/25, 14:10

    Just to be sure it's not forgotten: we need a Feature RST for this. Also is pages.url about to the deprecated with this? If yes, then we also need a Deprecation RST.
  48. Lina Wolf commented on patch set 15 10/30/25, 14:18

    Reply

    Yep if the tests ever pass I will make one....
  49. core-ci voted on patch set 15 V -1 10/30/25, 14:22 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88149

  50. Lina Wolf uploaded patch set 16 V -1 10/30/25, 15:09

  51. core-ci voted on patch set 16 V -1 10/30/25, 15:23 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88159

  52. Stefan Bürk commented on patch set 16 10/31/25, 08:24

    Working on it ...
  53. Lina Wolf marked it work in progress 11/10/25, 12:09

  54. Lina Wolf commented on patch set 16 11/10/25, 12:09

    Working on it again
  55. Lina Wolf uploaded patch set 17 V -1 11/10/25, 12:21

  56. core-ci voted on patch set 17 V -1 11/10/25, 12:50 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88839

  57. Lina Wolf uploaded patch set 18 V -1 11/11/25, 03:41

  58. core-ci voted on patch set 18 V -1 11/11/25, 03:50 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88932

  59. Lina Wolf rebased onto patch set 19 V -1 11/11/25, 04:10

  60. core-ci voted on patch set 19 V -1 11/11/25, 04:18 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/88936

  61. Lina Wolf uploaded patch set 20 V -1 11/11/25, 18:17

  62. Lina Wolf uploaded patch set 21 11/11/25, 18:20

  63. core-ci voted on patch set 20 V -1 11/11/25, 18:33 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89051

  64. core-ci voted on patch set 21 V -1 11/11/25, 18:36 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89052

  65. Lina Wolf uploaded patch set 22 V -1 11/11/25, 19:51

  66. core-ci voted on patch set 22 V -1 11/11/25, 20:05 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89066

  67. Lina Wolf uploaded patch set 23 V -1 11/11/25, 20:16

  68. core-ci voted on patch set 23 V -1 11/11/25, 20:30 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89068

  69. Lina Wolf uploaded patch set 24 V -1 11/11/25, 21:46

  70. core-ci voted on patch set 24 V -1 11/11/25, 21:57 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89084

  71. Lina Wolf uploaded patch set 25 V -1 11/12/25, 11:30

  72. core-ci voted on patch set 25 V +1 11/12/25, 11:38 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89289

  73. Lina Wolf uploaded patch set 26 V +1 11/12/25, 13:30

  74. core-ci voted on patch set 26 V +1 11/12/25, 13:39 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89324

  75. Lina Wolf marked it ready for review 11/12/25, 13:40

  76. Lina Wolf commented on patch set 26 11/12/25, 13:44

    Reply

    Done

    Reply

    Done
  77. Garvin Hicking commented on patch set 26 11/12/25, 15:08

    Breaking-17406-FieldUrlInTablePagesHasBeenRemoved.rst:5

    when it's breaking we need a [!!!] commit message. also maybe add a commit message?
  78. Lina Wolf updated the commit message in patch set 27 V +1 11/12/25, 15:47

  79. Lina Wolf commented on patch set 27 11/12/25, 15:47

    Breaking-17406-FieldUrlInTablePagesHasBeenRemoved.rst:5 Reply

    Done
  80. core-ci voted on patch set 27 V +1 11/12/25, 15:55 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89360

  81. Simon Schaufelberger commented on patch set 27 11/17/25, 12:47

    PageLinkMessageProvider.php:91

    I don't know if it makes much sense to make most of the stuff protected but these methods private. Either everything private or everything protected. What do you think?

    PageTypeLinkResolver.php:34

    these can be readonly

    PageInformationFactory.php:78

    final -> private
  82. Francois Suter commented on patch set 27 CR -1 V -1 11/17/25, 21:03

    This is a really cool feature and I'm all for it. About the code, I feel like there are very few comments and I wish there would be more, explaining the logic, the various conditions, etc. I know you can guess from the code, but I feel it's so much easier with an explanation. It makes the intent clear and the code easier to understand. About using the feature, it all went well, except when using a t3://record type of link. In the page layout module, the link type was not correctly detected and the message about the link being invalid was displayed. The link is resolved fine in the frontend.
  83. Lina Wolf uploaded patch set 28 CR -1 V +1 11/17/25, 22:28

  84. Lina Wolf commented on patch set 27 11/17/25, 22:30

    Reply

    Thanks for the feedback. I tried to add more comments, please have another look and tell me where you think more comments are missing. Thanks also for pointing out the record link.

    PageLinkMessageProvider.php:91 Reply

    Done

    PageTypeLinkResolver.php:34 Reply

    Done

    PageInformationFactory.php:78 Reply

    Done
  85. core-ci voted on patch set 28 V +1 11/17/25, 22:36 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89975

  86. Lina Wolf marked it work in progress 11/18/25, 09:15

  87. Lina Wolf commented on patch set 28 11/18/25, 09:15

    Working on including message for records
  88. Lina Wolf uploaded patch set 29 V +1 11/18/25, 13:13

  89. Lina Wolf commented on patch set 29 11/18/25, 13:14

    This change is ready for review.

    Reply

    I added handling for custom records
  90. core-ci voted on patch set 29 V +1 11/18/25, 13:21 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90023

  91. Francois Suter commented on patch set 29 11/18/25, 15:54

    Thanks for this new version, with more comments and support for record-type links. I add a few minor comments in the code. However I have a more general question: it is possible to define custom link handlers. How does your code cope with that? Is the message about a "destination" kind of a default one (I have seen it when defining a telephone-type link)? Should we actually delegate to the link handlers the task of assembling the message for the page layout module? Or have an event for customising the message?

    PageLinkMessageProvider.php:83

    record

    PageLinkMessageProvider.php:219

    What about having a specific message (indicating that it is a link to a record)? Right now, it's a bit confusing, because it says "Page of type "Link" links to the following page", but link is to edit some arbitrary record. I think the message should be more detailed like the one for when the record is not found.
  92. Stefan Bürk commented on patch set 29 CR -1 11/19/25, 02:52

    (Working) on it ...
  93. Lina Wolf commented on patch set 29 11/19/25, 05:23

    Reply

    Custom link types resolve like any other typolink in the frontend. In the backend they use the default fallback message if they resolve in a backend context. I can introduce an event in a follow up to override the backend message

    PageLinkMessageProvider.php:219 Reply

    Ack, forgot about it
  94. Stefan Bürk commented on patch set 29 11/20/25, 12:31

    Reply

    Still on it ...

    PageRepository.php:1130

    This line is obsolete, `$doktype` is not used/passed. Can be removed.

    PageRepository.php:1180

    Throwing an extension ? Nice, Maria Kart in TYPO3 core 😄. I assume that `exception` was ment here. Going to fix that with next push.

    PageRepository.php:2167

    Public method should get some description for consumer (developers). Also let's move public methods more up.

    PageRepository.php:2170

    I guess we can streamline the method to use early returns, making the code flow a little bit smarter and avoids nesting if-else levels and structures.

    PageRepository.php:2191

    Currently, this exception is thrown in two different cases: * Cycling has been detected (page already in the chain) * Iteration limit reached without having the page already in the chain. That does only mean that chain is "huge" but does not necessarily mean that it **would** end up in a cycling chain if continued. I'd say we should have two dedicated exception for the different cases being on this here right now.

    CircularChainException.php:24

    This exception is thrown in case resolving referenced (page) records in a chain could not be resolved within given iterations (20 for core usage) and not related to Rootline, which are technically different things. Following that, this exception should not extend `RootlineException` as parent exception class. `PageNotFoundException` also extends the RootlineException which confuses me slightly. So we should either extend from `\RuntimeException` or `PageNotFoundException`. The latter would reflect that the referenced page could not be resolved (found) within 20 iterations looking into the reference chain. Need to think about it, and it is possible that I'm overseeing the technical reason basing this on `RootLineException`. Another point is the naming .. `CirularChain` is to generic and opens reusing it in the future for completly unrelated things breaking a concrete exception messaging.
  95. Stefan Bürk commented on patch set 29 11/20/25, 12:55

    PageLinkMigration.php:28

    We should not add the upgrade wizard to EXT:install .. one upgrade wizard lesser to move in v14 ...
  96. Stefan Bürk commented on patch set 29 11/20/25, 14:07

    PageLinkMigration.php:28 Reply

    Keeping it in EXT:install and move it with the other once when it is time.
  97. Stefan Bürk uploaded patch set 30 CR -1 V +1 11/20/25, 16:22

  98. Stefan Bürk voted on patch set 30 CR -1 11/20/25, 16:22

  99. Lina Wolf marked it work in progress 11/20/25, 16:23

  100. core-ci voted on patch set 30 V -1 11/20/25, 16:39 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90315

  101. Lina Wolf rebased onto patch set 31 CR -1 V -1 11/20/25, 17:50

  102. core-ci voted on patch set 31 V -1 11/20/25, 18:05 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90340

  103. Lina Wolf uploaded patch set 32 V -1 11/20/25, 18:07

  104. core-ci voted on patch set 32 V -1 11/20/25, 18:20 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90343

  105. Lina Wolf uploaded patch set 33 V -1 11/20/25, 18:27

  106. core-ci voted on patch set 33 V -1 11/20/25, 18:42 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90344

  107. Stefan Bürk uploaded patch set 34 V -1 11/21/25, 08:33

  108. core-ci voted on patch set 34 V +1 11/21/25, 08:42 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90456

  109. Christian Kuhn commented on patch set 34 11/21/25, 09:45

    This change is ready for review.

    PageLinkMigration.php:189

    we don't manage zzz_deleted_url: this does not exist from core PoV anymore. nowhere. and not in wizards, either. the upgrade deal is: add NEW fields, then run wizards. delete fields / rename-to-delete after that.
  110. Lina Wolf commented on patch set 34 11/21/25, 09:48

    PageLinkMigration.php:189 Reply

    This change was marked as WIP since it is not finished yet. I think you just accidently marked it for review?
  111. Lina Wolf marked it work in progress 11/21/25, 09:48

  112. Stefan Bürk uploaded patch set 35 V +1 11/21/25, 10:22

  113. core-ci voted on patch set 35 V +1 11/21/25, 10:30 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90480

  114. Stefan Bürk uploaded patch set 36 V +1 11/21/25, 11:04

  115. core-ci voted on patch set 36 V -1 11/21/25, 11:12 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90486

  116. Stefan Bürk uploaded patch set 37 V -1 11/21/25, 13:23

  117. core-ci voted on patch set 37 V +1 11/21/25, 14:00 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90525

  118. Stefan Bürk uploaded patch set 38 V +1 11/21/25, 16:14

  119. core-ci voted on patch set 38 V -1 11/21/25, 16:31 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90545

  120. Stefan Bürk uploaded patch set 39 V -1 11/21/25, 16:39

  121. Stefan Bürk commented on patch set 39 11/21/25, 16:42

    PageLinkMessageProvider.php:83 Reply

    Done

    PageRepository.php:1130 Reply

    Done

    PageRepository.php:1180 Reply

    Done

    PageRepository.php:2170 Reply

    Done

    PageRepository.php:2191 Reply

    Splitted into two exceptions and renamed the cycling one.

    CircularChainException.php:24 Reply

    Extended the exception (both) now from the PageNotFound instead of the rootline parent exception.

    PageLinkMigration.php:189 Reply

    @lolli@schwarzbu.ch ack. Removed it and other stuff reducing the wizard. @112@linawolf.de For sure. Pressure, sleep absence, ... ;)
  122. core-ci voted on patch set 39 V +1 11/21/25, 16:46 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90552

  123. Lina Wolf commented on patch set 39 11/22/25, 05:47

    Reply

    Custom links produced by a link handler are displayed as external link both in the frontend and the backend

    PageLinkMessageProvider.php:219 Reply

    Done
  124. Lina Wolf rebased onto patch set 40 V +1 11/22/25, 11:59

  125. core-ci voted on patch set 40 V -1 11/22/25, 12:23 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90633

  126. Stefan Bürk commented on patch set 40 11/22/25, 15:18

    PageRepository.php:2167 Reply

    Done
  127. Stefan Bürk uploaded patch set 41 V -1 11/22/25, 15:19

  128. core-ci voted on patch set 41 V -1 11/22/25, 15:28 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90651

  129. Stefan Bürk uploaded patch set 42 V -1 11/22/25, 16:54

  130. core-ci voted on patch set 42 V +1 11/22/25, 17:07 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90669

  131. Stefan Bürk uploaded patch set 43 V +1 11/22/25, 18:28

  132. core-ci voted on patch set 43 V +1 11/22/25, 18:38 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90678

  1. Stefan Bürk uploaded patch set 44 V +1 11/22/25, 20:12

  2. core-ci voted on patch set 44 V -1 11/22/25, 20:19 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90689

  3. Stefan Bürk uploaded patch set 45 V -1 11/22/25, 21:04

  4. core-ci voted on patch set 45 V +1 11/22/25, 21:19 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90693

  5. Stefan Bürk uploaded patch set 46 V +1 11/24/25, 10:53

  6. core-ci voted on patch set 46 V -1 11/24/25, 11:06 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90819

  7. Simon Schaufelberger wrote 11/24/25, 11:07

    Removed cc Simon Schaufelberger.
  8. Stefan Bürk uploaded patch set 47 V -1 11/24/25, 11:47

  9. core-ci voted on patch set 47 V +1 11/24/25, 11:56 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90825

  10. Stefan Bürk uploaded patch set 48 V +1 11/24/25, 12:25

  11. core-ci voted on patch set 48 V +1 11/24/25, 12:34 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90832

  12. Stefan Bürk uploaded patch set 49 V +1 11/24/25, 15:01

  13. Stefan Bürk commented on patch set 49 11/24/25, 15:02

    Reply

    Done
  14. Stefan Bürk uploaded patch set 50 11/24/25, 15:09

  15. core-ci voted on patch set 49 V +1 11/24/25, 15:10 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90853

  16. core-ci voted on patch set 50 V +1 11/24/25, 15:18 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90854

  17. Lina Wolf marked it ready for review 11/24/25, 15:20

  18. Oli Bartsch commented on patch set 50 11/24/25, 15:46

    PageDoktypeLinkMigration.php:53

    ```suggestion return 'Migrate field "pages.url" to "pages.link" for pages of type Link.'; ```

    PageDoktypeLinkMigration.php:58

    ```suggestion return 'Migrates "pages.url" to "pages.link", preserving former behaviour of the page type "External Link".'; ```
  19. Stefan Bürk uploaded patch set 51 V +1 11/24/25, 15:54

  20. Stefan Bürk commented on patch set 51 11/24/25, 15:55

    PageDoktypeLinkMigration.php:53 Reply

    Done

    PageDoktypeLinkMigration.php:58 Reply

    Done
  21. core-ci voted on patch set 51 V +1 11/24/25, 16:07 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/90863

  22. Sven Liebert voted on patch set 51 CR +1 V +1 11/24/25, 16:17

  23. Georg Ringer voted on patch set 51 CR +1 V +1 11/24/25, 16:17

  24. Georg Ringer voted on patch set 51 CR +2 V +2 11/24/25, 16:27

  25. Georg Ringer merged patch set 52 11/24/25, 16:27