Closed (fixed)
Project:
Drupal core
Version:
11.3.x-dev
Component:
content_translation.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
10 Dec 2024 at 13:14 UTC
Updated:
21 Nov 2025 at 19:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
eduardo morales albertiAs the \Drupal\content_translation\Plugin\views\field\TranslationLink extends from \Drupal\views\Plugin\views\field\EntityLink it should have the same schema.
Comment #4
eduardo morales albertiReady to review
Comment #5
bserem commentedreviewing
Comment #6
bserem commentedAttached screenshot with before and after.
MR !10503 fixes the schema.
Nice find @eduardo
Comment #7
quietone commentedChanges are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies.
Comment #8
alexpottThis means we're missing test coverage of this feature because otherwise we'd get the schema errors reported by the test.
Comment #13
dcam commentedMR 10503 was opened against the incorrect branch. It had to be rebased manually. So I decided to open a new branch instead and manually copy the changes. I also added a test.
Comment #14
idebr commented'Test-only changes' job reports the missing schema correctly, see https://git.drupalcode.org/issue/drupal-3492882/-/jobs/7181313
Comment #15
alexpottWe test all the config for schema in test automatically - the test changes here are unnecessary - if you only make the changes to the test view and not the schema changes you get
Going to remove the test class changes and then merge.
Comment #16
alexpottCommitted and pushed f48a87604dd to 11.x and b11f562bde0 to 11.3.x. Thanks!