500 Internal Server Error with Styles n Scripts

Ruby Apps Radiant CMS
1

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:ininitialize_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:inprocess_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:inprocess’
/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:inhandle_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:insynchronize’
/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:indispatch_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:inprocess’
/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:inprocess’
/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:ineach’
/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:inrun’
/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:innew’
/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:ininitialize’
/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:inrun’
/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:ineach’
/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:inrun’
/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:inload’
/usr/bin/mongrel_rails:19

2

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

3

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

View this message in context:
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.

4

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

5

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

6

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? :slight_smile:

7

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

8

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

9

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

10

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.