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.

Sign up for GitHub

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

Jump to bottom

Component loses category when switching to advanced settings #7523

Closed
derrickmehaffy opened this issue Aug 19, 2020 · 0 comments · Fixed by #7597
Closed

Component loses category when switching to advanced settings #7523

derrickmehaffy opened this issue Aug 19, 2020 · 0 comments · Fixed by #7597
Labels
issue: bug Issue reporting a bug severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve source: core:content-manager Source is core/content-manager package status: confirmed Confirmed by a Strapi Team member or multiple community members

Comments

@derrickmehaffy
Copy link
Member

Describe the bug
While creating a new component and adding a category for it, if you switch to the advanced settings tab and back to base settings, the category field will be missing.

In my case I was adding a single time with a component.

Steps to reproduce the behavior

  1. Create a single-type
  2. Add a component as a field
  3. Set the name and category
  4. Switch to advanced settings
  5. Switch back to base settings
  6. See missing category

Expected behavior
Category should be cached in the browser when switching between tabs

Screenshots
image
image
image

System

  • Node.js version: 12.18.3
  • NPM version:6.14.6
  • Strapi version: 3.1.4
  • Database: SQLite
  • Operating system: Linux Mint 19.3 Tricia
@derrickmehaffy derrickmehaffy added issue: bug Issue reporting a bug severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve source: core:content-manager Source is core/content-manager package labels Aug 19, 2020
@lauriejim lauriejim added the status: confirmed Confirmed by a Strapi Team member or multiple community members label Aug 20, 2020
soupette added a commit that referenced this issue Aug 25, 2020
@soupette
Fixes #7523
4e4cb8e 
Signed-off-by: soupette <cyril.lpz@gmail.com>
@soupette soupette mentioned this issue Aug 25, 2020
Merged
renz45 pushed a commit to renz45/strapi that referenced this issue Aug 26, 2020
@soupette
Fixes strapi#7523
5bb66c2 
Signed-off-by: soupette <cyril.lpz@gmail.com>
Signed-off-by: Adam Rensel <renz45@github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
issue: bug Issue reporting a bug severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve source: core:content-manager Source is core/content-manager package status: confirmed Confirmed by a Strapi Team member or multiple community members
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix front-end small issues strapi/strapi
2 participants
@lauriejim @derrickmehaffy