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

Add 404 page #411

Closed
wants to merge 1 commit into from
Closed

Add 404 page #411

wants to merge 1 commit into from

Conversation

jgable
Copy link
Contributor

@jgable jgable commented Aug 17, 2013

A very simple 404 page styled with the current theme (added some padding
but that's it). Sent as a static file instead of a view to prevent us
having to duplicate it on the theme and the admin side for now.

Closes #409.

A very simple 404 page styled with the current theme (added some padding
but that's it). Sent as a static file instead of a view to prevent us
having to duplicate it on the theme and the admin side for now.
@jgable
Copy link
Contributor Author

jgable commented Aug 18, 2013

Does this satisfy #356 or should I close this in favor of that getting implemented?

@ErisDS
Copy link
Member

ErisDS commented Aug 18, 2013

#356 is intended to add 404 support across the whole application not just if a post cannot be found. I would merge this for the time being but I want to get @JohnONolan's signoff on the appearance of the 404 page before I do :)

@cgiffard
Copy link
Contributor

I'm back online. :)

We should probably focus on the systems for integrating 404s, since users will definitely want to theme their own, and we'll want a flexible system in place to support that (but still have the ghost-themed 404 for admin routes.)

@matthojo matthojo mentioned this pull request Aug 19, 2013
@jgable
Copy link
Contributor Author

jgable commented Aug 20, 2013

Closing in favor of #453

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

Successfully merging this pull request may close these issues.

Handling non-existent content
3 participants