See title. Same as the view...
Here we go. The column is automatically added if there's more than one bundle enabled for translation of a given entity type, just like the filter.
Applied, works, provides valuable information.
It also makes visible that the nodes of content types with only field translation activated are listed in the node source page.
It that so on purpose?
No, that's a bug, but that's a different issue :)
Which, I think, already exists...
You are right: #1909824: Node sources view shows content with entity translation activated
For this issue, the patch resolves the request.
Commited, will try to add tests for this in #1931012: Column not found: 1054 Unknown column 'e.vocabulary_machine_name' in 'where clause'.
Automatically closed -- issue fixed for 2 weeks with no activity.
Comments
Comment #1
berdirHere we go. The column is automatically added if there's more than one bundle enabled for translation of a given entity type, just like the filter.
Comment #2
cgalli commentedApplied, works, provides valuable information.
It also makes visible that the nodes of content types with only field translation activated are listed in the node source page.
It that so on purpose?
Comment #3
berdirNo, that's a bug, but that's a different issue :)
Which, I think, already exists...
Comment #4
cgalli commentedYou are right: #1909824: Node sources view shows content with entity translation activated
For this issue, the patch resolves the request.
Comment #5
berdirCommited, will try to add tests for this in #1931012: Column not found: 1054 Unknown column 'e.vocabulary_machine_name' in 'where clause'.