Forum: Radiant CMS 500 Internal Server Error with Styles n Scripts

85917960704ecf79feffc6354c545276?d=identicon&s=25 Errol Siegel (eksatx)
on 2009-01-18 20:44
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
8e0f829374e9d875f71800db0aaaa739?d=identicon&s=25 coffeepostal (Guest)
on 2009-01-19 18:40
(Received via mailing list)
Errol Siegel-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-td...
http://www.nabble.com/SnS-Extension---500-Error-td...
--
View this message in context:
http://www.nabble.com/500-Internal-Server-Error-wi...
Sent from the Radiant - User (New) mailing list archive at Nabble.com.
85917960704ecf79feffc6354c545276?d=identicon&s=25 Errol Siegel (eksatx)
on 2009-02-02 01:55
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
85917960704ecf79feffc6354c545276?d=identicon&s=25 Errol Siegel (eksatx)
on 2009-02-09 03:38
I am still having the same problem.  I would really appreciate it if
anybody had suggestions about where to begin trouble-shooting this
problem.
6b4c6adcc88f3f072ee94b54f737ccdb?d=identicon&s=25 Vincent Behar (vinz)
on 2009-02-09 10:21
Attachment: stack.txt (4 KB)
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
85917960704ecf79feffc6354c545276?d=identicon&s=25 Errol Siegel (eksatx)
on 2009-02-12 19:31
I can confirm that the problem does not happen with 0.6.9 but does
happen with 0.7.0.
42b570f6f4312a872c2fc671e3ddc82b?d=identicon&s=25 Trejkaz Xx (trejkaz)
on 2009-03-05 10:49
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? :-)
85917960704ecf79feffc6354c545276?d=identicon&s=25 Errol Siegel (eksatx)
on 2009-03-05 16:55
No resolution to this issue yet.  I simply stopped using that extension.
It's kind of a bummer because I like using it.
42b570f6f4312a872c2fc671e3ddc82b?d=identicon&s=25 Trejkaz Xx (trejkaz)
on 2009-03-06 10:31
Errol Siegel 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.
Bc66e548a86d9635d5d1542080db5665?d=identicon&s=25 Jon Jensen (jenseng)
on 2009-06-05 07:15
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
This topic is locked and can not be replied to.