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

Better status code and error message for when a component isn't found #399

Closed
mheiber opened this issue Apr 25, 2017 · 3 comments
Closed
Assignees
Labels

Comments

@mheiber
Copy link

mheiber commented Apr 25, 2017

Summary:

When a page can't render because a component isn't found, we should get an error message saying that the page can't render because a component isn't found.

Steps to reproduce

Add a new component reference to editable_components for a component that doesn't exist
Try to create a page
Result: 404 with no message

Expected result: better error message like "component not found". Maybe a 500 would be a better status code.

Thanks for your help!

@jonwinton jonwinton self-assigned this May 2, 2017
@jonwinton jonwinton added the bug label May 2, 2017
@pfeytser
Copy link

pfeytser commented Dec 4, 2017

This is fixed in cases where the data is 404-ing, but needs to be addressed for render.

@nelsonpecora
Copy link
Contributor

@jonwinton this is fixed for rendering by #544 yeah?

@jonwinton
Copy link
Contributor

Yeah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants