# 500 Internal Server Error with Styles n Scripts

**URL:** <https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056>\
**Category:** Radiant CMS\
**Created:** [January 18, 2009, 8:44pm UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056 "2009-01-18T20:44:51Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [January 18, 2009, 8:44pm UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/1 "2009-01-18T20:44:51Z")

</div>

I performed the installation and setup steps according to the  
documentation, but when I click either the CSS or JS tabs in the admin  
view, I get this error.

Stack trace appears below.

Thanks in advance for your help!

/!\ FAILSAFE /!\ Sun Jan 18 13:37:29 -0600 2009  
Status: 500 Internal Server Error  
wrong argument type nil (expected Module)  
/home/mostfor/public\_html/vendor/radiant/vendor/rails/actionpack/lib/action\_controller/base.rb:1130:in  
`extend' /home/mostfor/public_html/vendor/radiant/vendor/rails/actionpack/lib/action_controller/base.rb:1130:in`initialize\_template\_class’  
/home/mostfor/public\_html/vendor/radiant/vendor/rails/actionpack/lib/action\_controller/base.rb:522:in  
`process_without_filters' /home/mostfor/public_html/vendor/radiant/vendor/rails/actionpack/lib/action_controller/filters.rb:568:in`process\_without\_session\_management\_support’  
/home/mostfor/public\_html/vendor/radiant/vendor/rails/actionpack/lib/action\_controller/session\_management.rb:130:in  
`sass_old_process' /home/mostfor/public_html/vendor/radiant/vendor/plugins/haml/lib/sass/plugin/rails.rb:19:in`process’  
/home/mostfor/public\_html/vendor/radiant/vendor/rails/actionpack/lib/action\_controller/base.rb:389:in  
`process' /home/mostfor/public_html/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:149:in`handle\_request’  
/home/mostfor/public\_html/vendor/radiant/vendor/rails/actionpack/lib/action\_controller/dispatcher.rb:107:in  
`dispatch' /home/mostfor/public_html/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in`synchronize’  
/home/mostfor/public\_html/vendor/radiant/vendor/rails/actionpack/lib/action\_controller/dispatcher.rb:104:in  
`dispatch' /home/mostfor/public_html/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:120:in`dispatch\_cgi’  
/home/mostfor/public\_html/vendor/radiant/vendor/rails/actionpack/lib/action\_controller/dispatcher.rb:35:in  
`dispatch' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:76:in`process’  
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/lib/mongrel/rails.rb:74:in  
`synchronize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/rails.rb:74:in`process’  
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/lib/mongrel.rb:159:in  
`process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:158:in`each’  
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/lib/mongrel.rb:158:in  
`process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in`run’  
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/lib/mongrel.rb:285:in  
`initialize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:285:in`new’  
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/lib/mongrel.rb:285:in  
`run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:268:in`initialize’  
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/lib/mongrel.rb:268:in  
`new' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel.rb:268:in`run’  
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/lib/mongrel/configurator.rb:282:in  
`run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/configurator.rb:281:in`each’  
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/lib/mongrel/configurator.rb:281:in  
`run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:128:in`run’  
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/…/lib/mongrel/command.rb:212:in  
`run' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:281 /usr/bin/mongrel_rails:19:in`load’  
/usr/bin/mongrel\_rails:19

---

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [February 2, 2009, 1:55am UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/2 "2009-02-02T01:55:43Z")

</div>

Thanks for the post, although it appears to be a different error. The  
stack trace in that other post was about ActiveRecord errors. My stack  
trace looks totally different.

Does anybody have any ideas?

Thanks again,  
Errol

---

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [January 19, 2009, 6:40pm UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/3 "2009-01-19T18:40:21Z")

</div>

Errol S.-3 wrote:

> I performed the installation and setup steps according to the  
> documentation, but when I click either the CSS or JS tabs in the admin  
> view, I get this error.
> 
> Stack trace appears below.
> 
> Thanks in advance for your help!

## I was having the same problem, this is what helped me: [http://www.nabble.com/SnS-Extension---500-Error-td21486070.html](http://www.nabble.com/SnS-Extension---500-Error-td21486070.html) [http://www.nabble.com/SnS-Extension---500-Error-td21486070.html](http://www.nabble.com/SnS-Extension---500-Error-td21486070.html)

View this message in context:  
[http://www.nabble.com/500-Internal-Server-Error-with-Styles-n-Scripts-tp21532055p21547835.html](http://www.nabble.com/500-Internal-Server-Error-with-Styles-n-Scripts-tp21532055p21547835.html)  
Sent from the Radiant - User (New) mailing list archive at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [February 9, 2009, 3:38am UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/4 "2009-02-09T03:38:01Z")

</div>

I am still having the same problem. I would really appreciate it if  
anybody had suggestions about where to begin trouble-shooting this  
problem.

---

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [February 12, 2009, 7:31pm UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/5 "2009-02-12T19:31:31Z")

</div>

I can confirm that the problem does not happen with 0.6.9 but does  
happen with 0.7.0.

---

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [March 5, 2009, 10:49am UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/6 "2009-03-05T10:49:37Z")

</div>

I can confirm that this still happens on 0.7.1.

I got a different 500 error regarding no\_login\_required?, managed to fix  
that and thought I was in the clear, but now I get this one instead.

Have any of you guys fixed it since you posted? Or have you just not  
edited your CSS and JS until someone else fixes it? 🙂

---

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [March 5, 2009, 4:55pm UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/7 "2009-03-05T16:55:59Z")

</div>

No resolution to this issue yet. I simply stopped using that extension.  
It’s kind of a bummer because I like using it.

---

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [February 9, 2009, 10:21am UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/8 "2009-02-09T10:21:33Z")

</div>

Hi,

I have the same problem. My (old) site with radiant 0.6.9 and sns is  
working fine, but yesterday I installed a new one with radiant 0.7.0,  
and got the same stack when trying to access /admin/css or /admin/js.

I think it’s a problem with the haml plugin.  
The weird thing is that there is no trace of the sns extension in the  
stack…

Thanks for any help with this,  
Vincent

---

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [June 5, 2009, 7:15am UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/9 "2009-06-05T07:15:23Z")

</div>

Found a fix… looks like the Admin::AbstractModelController.inherited  
method is broken. Adding a call to super to the end seems to do the  
trick for me:

def self.inherited(subclass)  
ActiveSupport::Deprecation.warn("‘Admin::AbstractModelController’  
has been deprecated. Please update ‘#{subclass.name}’ to use  
Admin::ResourceController.")  
super  
end

---

<div class="post-metadata">

**Author:** ![errolsiegel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/c77e96/32.png) [@errolsiegel](https://www.ruby-forum.com/u/errolsiegel)\
**Post date:** [March 6, 2009, 10:31am UTC](https://www.ruby-forum.com/t/500-internal-server-error-with-styles-n-scripts/158056/10 "2009-03-06T10:31:35Z")

</div>

Errol S. wrote:

> No resolution to this issue yet. I simply stopped using that extension.  
> It’s kind of a bummer because I like using it.

I am 50/50 on it personally. The only thing it really does is keep the  
scripts off the list of pages. Other than that it has no features which  
aren’t doable already. Seeing as I won’t be changing my style any time  
soon, not being able to get into the admin interface right now isn’t  
such a big deal anyway. At least it still works for serving the  
stylesheet.
