Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Issue is postponed until https://www.drupal.org/node/2235457 is resolved
Comment | File | Size | Author |
---|---|---|---|
#3 | create_link_field_menu_link_content-2302205-3.patch | 7.65 KB | hussainweb |
Comments
Comment #1
pwolanin CreditAttribution: pwolanin commentedSimilar to the plan for shortcut, we might get more efficient entity behavior to combine route, route parameters, etc
Shouldn't be worked on until after #2301319: MenuLinkNG part5: Remove dead code; and party!
Comment #2
mgiffordComment #3
hussainwebI am just uploading my work so far for review. I will be surprised if even Drupal installation succeeds.
Also, I think this might be a critical as it is related to many other critical issues around menu/routing. I am just setting it to major now like it's parent issue.
Comment #4
hussainwebOkay, there are some helper methods introduced in #2235457: Use link field for shortcut entity which are useful here. We can wait for that but I will try to move this ahead anyway.
Comment #6
pwolanin CreditAttribution: pwolanin commentedMaybe better to wait until we have a final link field schema?
Comment #7
hussainweb@pwolanin: You are right. I think the only thing left in the schema is the description but I at least wanted to see what would be the effect here. After seeing the failures, it seems it is better to wait out the related issues.
Comment #9
hussainwebI am retesting this as there are some helper methods in #2235457: Use link field for shortcut entity and that patch is in. Let's see how many tests fail now and we can carry on working on this.
Comment #11
amateescu CreditAttribution: amateescu commentedThis issue is a bit confusing.. it looks like a duplicate of #2406749: Use a link field for custom menu link?
Comment #12
dawehnerYeah, it is a duplicate, thank you for finding it.