Unknown column 'node.changed' in 'field list' when sorting by updated/commented date [#2841379]

When creating a view with the "Updated/commented date" sort, I receive the following error:

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'node.changed' in 'field list':

The "changed" field is no longer contained in the node table; it's in the node_field_data table. I attempted to change line 18 of core/modules/comment/src/Plugin/views/sort/StatisticsLastUpdated.php to reflect that, which resolves the error and sorts correctly but seemed to cause duplication in my case.

Comment	File	Size	Author
#5	views.view_.activity.yml	6.83 KB	stephenward

Comments

Comment #1

5 January 2017 at 17:29

StephenWard created an issue. See original summary.

Comment #2

stephenward commented 5 January 2017 at 18:03

Title:

Updated/commented date throws

» Updated/commented date sort throws SQL error

Comment #3

cilefen commented 5 January 2017 at 22:45

Title:	Updated/commented date sort throws SQL error	» Unknown column 'node.changed' in 'field list' when sorting by updated/commented date
Component:	comment.module	» views.module

Comment #4

cilefen commented 5 January 2017 at 22:47

Component:	views.module	» comment.module
Priority:	Normal	» Major

Actually, you were probably right about the comment component if that's where you think the bug is. Usually we like to have the view definition exported and attached to a comment if you don't mind.

Comment #5

stephenward commented 6 January 2017 at 02:50

Status	File	Size
new	views.view_.activity.yml	6.83 KB

Apologies. Here you go. Please let me know if I can be of any more help.

Comment #6

jonathanshaw

English

Stroud, UK

commented 6 January 2017 at 12:10

I've hit the same bug, but not been able to trace the root of it. I think I found that it did not happen on a clean blank install, but once I imported my site configuration it happened even when creating a new view with any content type. I do have more than one comment type configured, that may be a direction to explore.

Comment #7

stephenward commented 6 January 2017 at 15:25

Since @jonathanshaw mentioned it, I can confirm that my site was recently upgraded from Drupal 7 using the Migrate suite of modules. This may or may not be probative, however, since the changed field still doesn't exist in the node table anymore. One way or another, it seems like this must be in error.