Contrib.social

Comment's node_new_comments View field history markers ("new" comment marker) forces render caching to be per user

Open on Drupal.org →
Created on 5 September 2013, almost 12 years ago
Updated 20 August 2025, 3 days ago

Details: see #1991684: Node history markers (comment & node "new" indicator, "x new comments" links) forces render caching to be per user → , particularly the issue summary and comments 14 and 40.

This issue was split off from that issue because the render cache breakage of the Comment module's Views integration does not break entity render caching, which is what we were trying to unblock there.

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

comment.module

Created by

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

  • Performance

    It affects performance. It is often combined with the Needs profiling tag.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment 3 days ago →
    🇺🇸United States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

  • Comment 2 days ago →
    🇬🇧United Kingdom catch

    I'm sure this hasn't been fixed. It's most likely that it will end up in contrib with history module before it is but we should move it there with that module.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024