Follow-up to #2594195: [meta] Improve support for multiple comment fields.
Problem/Motivation
The NodeNewComments field handler provides a "New comments" field to nodes. It does not support selection of a specific comment field to report on or link to - as this report is written, it will use (if present) the comment field named 'comment', and the proposed fix for #2588547: CommentLinkBuilder causes fatal error when comment field not named 'comment' will have it use the "first" comment field. If there are multiple comment fields on the node type, there is no way to choose which specific comment field to use for the New comments field.
Proposed resolution
Remaining tasks
Task | Novice task? | Contributor instructions | Complete? |
---|---|---|---|
Create a patch | Instructions | ||
Add automated tests | Instructions | ||
Review patch to ensure that it fixes the issue, stays within scope, is properly documented, and follows coding standards | Instructions |
Comments
Comment #2
mikeryanComment #3
YesCT CreditAttribution: YesCT commentedComment #14
catchMarked #2969255: Comments + History "new" link only works with one comment field as duplicate. Providing a field name configuration in the view plugin makes a lot of sense.