- First commit to issue fork.
- πΊπΈUnited States Kasey_MK
I find the current status of Last read comment field/filter/argument uses still the node.changed instead of node_field_data.changed column π Last read comment field/filter/argument uses still the node.changed instead of node_field_data.changed column Needs review to be pretty confusing, and I can't find a way to get my site working from it.
The patch here in #10 made my views work, but introduced another error in the config. For what it's worth, swapping in the config update from that other issue seems to do the trick for my site.
So on
core/modules/comment/config/schema/comment.views.schema.yml
:Remove this change:
views.filter.comment_ces_last_updated: - type: views.filter.date + type: views.filter_value.date
Add this change:
views.field.comment_ces_last_updated: - type: views_field + type: views.field.date
I haven't tried making issue forks before now, and it doesn't look like I can upload the patch I made here. I just wanted to say thanks for the patch in #10 and to share the tweak that made it work for me.
Commit 014a85f2 includes a "Plain Diff" in the "Options" dropdown which you can save locally as a .patch file, in case that's helpful to anyone else.
I didn't make a pull request, because it looks like the "real work" is being done on that other issue, so probably not worth trying to advance this issue - except that for me, at least, it lets me get back to a working site until everything else is resolved.