Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CM : Back arrow issue >> Relation field cache is not invalidated when going "back" #20217

Open
MarionLemaire opened this issue Apr 26, 2024 · 1 comment
Labels
issue: bug Issue reporting a bug severity: high If it breaks the basic use of the product source: core:content-manager Source is core/content-manager package status: confirmed Confirmed by a Strapi Team member or multiple community members version: 5

Comments

@MarionLemaire
Copy link
Contributor

Bug report

  • Node.js version: 20.9.0
  • Strapi version: v5.0.0-beta.5
  • Operating system: Windows

Describe the bug

In CM, when creating a new entry for a collection type with Relation field, after saving, if I click the Back arrow to create a new entry, the Relation field is still filled-in with the infos from previous entry (all other fields are empty).

Loom here : https://www.loom.com/share/2a740320420f4e81a09927c614412530?sid=1cf33509-4824-4ad4-8a35-973ce62fef8b

Steps to reproduce the behavior

  1. Create a Collection type with a Relation field
    2.Go to Content Manager
  2. Create a first entry with this CT, with one or many relations in the Relation field
  3. Save this entry (and/or publish it)
  4. Click Back arrow
  5. Check Relation field : still filled in with previous info

Expected behavior

Relation field should be cleared up and empty

Screenshots

Entry #1 saved and published :
image

Entry #2 after clicking on Back arrow :
image

Dashcam info here : https://app.dashcam.io/share/FU79RvPPj6PcV2obpIO9w

@derrickmehaffy derrickmehaffy added issue: bug Issue reporting a bug severity: high If it breaks the basic use of the product status: confirmed Confirmed by a Strapi Team member or multiple community members source: core:content-manager Source is core/content-manager package labels Apr 26, 2024
@derrickmehaffy
Copy link
Member

I see you @MarionLemaire

Image

And I raise you

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Issue reporting a bug severity: high If it breaks the basic use of the product source: core:content-manager Source is core/content-manager package status: confirmed Confirmed by a Strapi Team member or multiple community members version: 5
Projects
Status: To be reviewed
Status: Backlog
Status: To review
Development

No branches or pull requests

2 participants