Cache is not invalidating

Created on 24 May 2022, almost 3 years ago
Updated 11 April 2025, 18 days ago

Problem/Motivation

Hi, I've found a problem with cache not being invalidated in some circumstances.

Steps to reproduce

  1. Create a new menu.
  2. Add some menu link(s) to this menu, but don't enable it(them).
  3. Go to /decoupled_kit/menu/{menu-id}. You should see an "empty response".
  4. Go back to your menu item(s) and enable it(them).
  5. Go back to /decoupled_kit/menu/{menu-id}. You should see an "empty response", instead of the actual one. Clearing the cache solves the problem.
  1. Create a new menu.
  2. Add some menu link(s) to this menu and enable it(them).
  3. Go to /decoupled_kit/menu/{menu-id}. You should see a correct response with your menu item(s).
  4. Go back to your menu and disable all of its items.
  5. Go back to /decoupled_kit/menu/{menu-id}. You should see an "empty response".
  6. Go back to your menu and enable at least one of its items.
  7. Go back to /decoupled_kit/menu/{menu-id}. You should see an "empty response", instead of the actual one. Clearing the cache solves the problem.

Empty response:

{
    "id": "custom-menu",
    "data": {
        "#cache": {
            "contexts": [],
            "tags": [],
            "max-age": -1
        }
    }
}
πŸ› Bug report
Status

Needs review

Version

1.3

Component

Code

Created by

πŸ‡΅πŸ‡±Poland tivi22

Live updates comments and jobs are added and updated live.
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.

Production build 0.71.5 2024