Forum history markers ("new" and "updated" markers, "x new posts" links) forces render caching to be per user

Created on 5 September 2013, about 11 years ago

Updated 24 April 2024, 7 months 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 comment 40.

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

🐛 Bug report

Status

Needs work

Version

1.0

Component

forum.module

Created by

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.

JavaScript

D8 cacheability

blocker

Incomplete comments

Comments & Activities

Not all content is available!

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

Comment almost 2 years ago →
🇳🇿New Zealand quietone
Forum is approved for removal. See #1898812: [policy] Deprecate forum module for removal in Drupal 11 →

This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

It will be moved to the contributed extension → once the Drupal 11 branch is open.
Status changed to Needs work 7 months ago1:32am 24 April 2024
Comment 7 months ago →
🇳🇿New Zealand quietone

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024