Menu items cached for all language

Created on 3 March 2023, almost 2 years ago
Updated 28 July 2023, over 1 year ago

Problem/Motivation

For multilingual website where Menu can be translated, the endpoint does not take into account language context.

Steps to reproduce

Suppose a website has 2 languages English(en) and Dutch(nl)
Create a menu eg. "Main Menu" (main-menu) and make it translatable.
Create 2 menu items for english Menu 1 EN, Menu 2 EN and translate them to dutch Menu 1 NL, Menu 2 NL.
Now navigate to english endpoint /en/api/menu_items/main-menu, you will see English menus. So far all good
Now navigate to dutch endpoint /nl/api/menu_items/main-menu, you will still see English menus instead of Dutch.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Closed: works as designed

Version

3.0

Component

Code

Created by

🇮🇳India amitajgaonkar

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @amitajgaonkar
  • Status changed to Postponed: needs info over 1 year ago
  • 🇳🇱Netherlands batigolix Utrecht

    The patch applies well, but I am not able to reproduce the problem.

    I have caching enabled and I translated the menu and menu items like you described. But I get 2 different translated menu trees back from the endpoint.

    Can you explain how caching is configured in your case?

  • Status changed to Closed: works as designed over 1 year ago
  • 🇳🇱Netherlands batigolix Utrecht

    I am closing this as there is no more feedback. Feel free te re-open if needed.

Production build 0.71.5 2024