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.
follow up to #2901939: Move the variations form to its own tab next to (Product) Edit.
With variations in their own tab, we need to ensure the content translation UI works. There's several isues
* Route generation provided by content_translation does not work since variations lack a canonical link template
* Link generation within content_translation dies since we require a {commerce_product} parameter, and links are somehow not being generated off of the variation.
Comment | File | Size | Author |
---|---|---|---|
#7 | 2999508-7.patch | 12.78 KB | bojanz |
| |||
#5 | 2999508-5.patch | 11.84 KB | mglaman |
#3 | 2999508-3.patch | 8.12 KB | mglaman |
#2 | 2999508-2.patch | 7.94 KB | mglaman |
Comments
Comment #2
mglamanThis doesn't quite work, but it is a start. The content translation overview must be manually building routes rather than toUrl() with a proper rel.
Comment #3
mglamanThis gets the translation overview to render without throwing route parameter exceptions.
Comment #4
mglamanActually, this seems to work fairly well now that the overview page was fixed. Needs tests.
Comment #5
mglamanTests! Just need the parent issue to land.
Comment #6
bojanz CreditAttribution: bojanz at Centarro commentedParent issue is now in.
Increasing priority, since we now have a regression.
EDIT: Opened #3004038: ContentTranslationRouteSubscriber should not construct its own URLs and #3004037: ContentTranslationController::overview() should not construct URLs manually in core for the issues we're working around. We'll want to document them in our docblocks.
Comment #7
bojanz CreditAttribution: bojanz at Centarro commentedNew patch, many cleanups.
Comment #9
bojanz CreditAttribution: bojanz at Centarro commentedManual tests were also fine. Committed #7.