Theme Rails' default 404 and 500 error pages.

[briri]

Please complete the following fields as applicable:

Expected behaviour: Rails has built-in handling for any 404 and 500 errors that occur when running in production mode (dev and other modes should continue to display the detailed error information). We should ideally return to the previous page (need to consider best approach for ajax. Ajax should be able to catch a 404 response from the controller) or the My Dashboard if that is not possible. A user firnedly error message should appear in the normal notifications section at the top of the page

Refer to the ActionController documentation for handling generic 404 and 500 errors http://guides.rubyonrails.org/action_controller_overview.html#the-default-500-and-404-templates

Actual behaviour: Screenshot of a 404 error when running in production mode:

Steps to reproduce:

1. Update your database.yml to ensure that you will not be testing against any live data!
2. Make sure your production secrets key is set in secrets.yml
3. Start the application in production mode bundle exec rails s -e production
4. Login
5. Go to a fake plan page (e.g. http://localhost:3000/plans/i5ty495yth5)

[magdalenadrafiova]

@briri is this still relevant?

[briri]

yes. this is still something we should consider doing.