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

A 'configure the view' button doesn't work correctly in Content-Types Builder. #7301

Closed
ByungJun25 opened this issue Aug 3, 2020 · 2 comments · Fixed by #7312
Closed

A 'configure the view' button doesn't work correctly in Content-Types Builder. #7301

ByungJun25 opened this issue Aug 3, 2020 · 2 comments · Fixed by #7312
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 status: confirmed Confirmed by a Strapi Team member or multiple community members

Comments

@ByungJun25
Copy link
Contributor

Describe the bug
A 'configure the view' button doesn't work correclty in Content-Types Builder.

Steps to reproduce the behavior

  1. Go to 'Content-Types Builder'.
  2. Select any Collection types and click Configure the view. (First trying works well)
  3. Click back button.
  4. Select other collection types and click Configure the view.
  5. See error.

Expected behavior
The function should show the correct view of what user select.

Screenshots
bug

Code snippets
Nothing.

System

  • Node.js version: 12.16.3
  • NPM version: 6.14.5
  • Strapi version: 3.1.3
  • Database: MongoDB
  • Operating system: Windows 10 / Docker
@ByungJun25 ByungJun25 changed the title A 'configure the view' button doesn't work correclty in Content-Types Builder. A 'configure the view' button doesn't work correctly in Content-Types Builder. Aug 3, 2020
@derrickmehaffy
Copy link
Member

Hello,

Thank you for the bug report, I was able to reproduce this on the latest version (v3.1.3) as you specified. For this issue I will ping @soupette and @HichamELBSI . If you would like to help by submitting a pull request you can. If you aren't sure where to start, no problem we will take a look into this ASAP.

@derrickmehaffy derrickmehaffy added severity: high If it breaks the basic use of the product status: confirmed Confirmed by a Strapi Team member or multiple community members issue: bug Issue reporting a bug labels Aug 3, 2020
@soupette soupette added severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve and removed severity: high If it breaks the basic use of the product labels Aug 4, 2020
soupette added a commit that referenced this issue Aug 4, 2020
@soupette
Fixes #7301
f34c947 
Signed-off-by: soupette <cyril.lpz@gmail.com>
@soupette soupette mentioned this issue Aug 4, 2020
Merged
@ByungJun25
Copy link
Contributor Author

ByungJun25 commented Aug 4, 2020 •
edited

Hello, @derrickmehaffy

Well, I find a reason now, but @soupette solves it before 24 minutes. ;D

Thanks strapi Teams! :D

Byungjun Woo

alexandrebodin pushed a commit that referenced this issue Aug 12, 2020
@soupette
Fixes #7301 (#7312)
99dfd24 
Signed-off-by: soupette <cyril.lpz@gmail.com>
gilfernandes pushed a commit to onepointconsulting/strapi that referenced this issue Aug 13, 2020
@soupette @onepointconsulting
Fixes strapi#7301 (strapi#7312)
87c0838 
Signed-off-by: soupette <cyril.lpz@gmail.com>
Signed-off-by: Gil Fernandes <gil.fernandes@onepointltd.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 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.

Fixes #7301 strapi/strapi
3 participants
@derrickmehaffy @ByungJun25 @soupette