Cache clearing fails after 1.11.7 upgrade

Support Ticket

+status
+tags
 

On a brand-new 1.11.7 installation of wagn (and existing wagns upgraded to 1.11.7), accessing http://foo.wagn.whatever/admin/clear_cache results in a 500 Hitch! page. The server log reports:

 

exception = ArgumentError: There was no default layout for AdminController in #<ActionView::PathSet:0xa1e1950 @paths=[#<ActionView::OptimizedFileSystemResolver:0x9b46578 @pattern=":prefix/:action{.:locale,}{.:formats,}{.:handlers,}", @cached={#<ActionView::LookupContext::DetailsKey:0xa1f88bc @hash=75558413>=>{"admin"=>{"layouts"=>{false=>{[]=>[]}}}, "card"=>{"layouts"=>{false=>{[]=>[]}}}, "application"=>{"layouts"=>{false=>{[]=>[]}}}, "base"=>{"layouts/action_controller"=>{false=>{[]=>[]}}}}}, @path="/opt/wagn/foo/app/views">]>

 

This is coming out of actionpack-3.2.13/lib/abstract_controller/layouts.rb:412, by way of /opt/wagn/foo/app/controllers/admin_controller.rb:117:in `render_text'

 

 

thanks for the bug report!

 

You're obviously right that there's a bug, but the good news is that it does appear to happen after the cache gets cleared. It's just an error displaying the final message (because of new layout handling). I'll patch it quickly, but know that if you get this message your cache has been cleared.

--Ethan McCutchen.....2013-07-21 20:52:41 +0000

I posted a fix. It was tiny, and we just got out the release yesterday, so I just re-tagged the release. But the latest on master should not have this problem.

 

(note: for now it will just give the response as simple text. Soon it will go back to the old behavior.)

--Ethan McCutchen.....2013-07-21 23:13:20 +0000