I found that views_handler_field_history_user_timestamp didn't mark nodes as new which weren't filtered by 'Show only content that is new or updated' (views_handler_filter_history_user_timestamp).
The reason is that views_handler_filter_history_user_timestamp refers to the changed date while views_handler_field_history_user_timestamp refers to created date.
node_mark() from node.module also uses the changed date to mark content as new. ... Using the changed date to mark content as new makes completely sense, because it does not matter when it was created, for the user who hasn't read a changed content, this content always will be new to him.
Comment | File | Size | Author |
---|---|---|---|
#1 | views_handler_field_history_user_timestamp-mark-new-1712044-1.patch | 954 bytes | osopolar |
Comments
Comment #1
osopolarComment #2
dawehnerJust from looking at the behavior of node_mark this seems to make sense, as it will be more similar code ...
Update status
Comment #3
dawehnerPerfect! Committed to 7.x-3.x and 8.x-3.x Btw. git is awesome!