Skip to content

Instantly share code, notes, and snippets.

@deepak
Last active April 22, 2016 13:05
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
Star You must be signed in to star a gist
Save deepak/62ac3345a4b70999186aa8e6385f03ae to your computer and use it in GitHub Desktop.
useful things while debugging a rails app you have not written yourself
1. view paths ?
2. where are the layout and view file located ?
3. is the database.yml valid ?
sanity check: eyeball if it is running locally.
4. any "very" old libs and/or known security vulnerabilities ?
for (1) can delete a partial and see the stacktrace
something like
```
Missing partial shared/foo with {:locale=>[:en], :formats=>[:html], :handlers=>[:erb, :builder, :jbuilder, :axlsx, :coffee, :haml, :csvbuilder, :liquid, :writeexcel]}. Searched in:
* "../app/themes/new_default/views"
* "../app/views"
* "../app/themes/default/views"
* "../gems/devise-2.2.4/app/views"
* "../app/views"
* "../app/themes/default/views"
* "../devise-2.2.4/app/views"
```
for (2) check for logs for rendered layout
eg. `Rendered devise/sessions/new.html.haml within layouts/public (9.2ms)`
and search layout in view path as per (1)
for (3) can do a simple "rails console"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment