Cache: none should not be set on views.

Created on 20 May 2025, 2 months ago

In a previous issue, it was discussed how it is a problem that when a peice of content is locked, the views arent displaying the "locked by.." text.

This was because the correct caches werent being invalidated.

The conclusion in the issue was to set cache: none, but I feel like this is a mistake.

Instead, in the issue, there was a commit that actually used correct cache invalidation, but for some reason, it was glossed over (?)

I feel like this is the correct solution, so I will attach a MR, where this ^ is included, and the "set cache: none" is removed.

🐛 Bug report

Status

Needs review

Version

3.0

Component

Code

Created by

🇩🇰Denmark ras-ben Copenhagen

Live updates comments and jobs are added and updated live.

Merge Requests

!73Cache: none should not be set on views.
Open
🇩🇰Denmark ras-ben
updated 2 months ago
!72Cache: none should not be set on views.
Open
🇩🇰Denmark ras-ben
updated 2 months ago

Issue created by @ras-ben
Merge request !72Content lock 3525430 8.2 → (Open) created by ras-ben
Merge request !733525430: Cache: none should not be set on views. → (Open) created by ras-ben
Comment 2 months ago →
🇩🇰Denmark kasperg
Instead, in the issue, there was a commit that actually used correct cache invalidation, but for some reason, it was glossed over (?)

As I see it the current solution is intentional so I think this should be closed.

In a comment alexpott wrote 🐛 In Views, the "Is Locked" field does not get updated after a lock break Fixed :

I've fixed the view so that it works - but I'm scared... this means views an edit screen and locking a node will impact the cache. This does not feel like the correct solution.

Later a commit states "now that we opted for no caching at all".

Production build 0.71.5 2024