#90 ✓resolved
atmorell

Custom Content module fails

Reported by atmorell | September 4th, 2010 @ 06:09 PM | in 1.0 Release

Hi,

When I try to add a new custom content module webiva just hangs forever. No errors in the console. I have to restart the webserver to get things running again. When I click one of the new modes I get the following error:

Administrative User

Location: cms:/website/content/view/2

Reported Type: auto

Reporting Domain: mywebiva.com

Behavior


A NoMethodError Exception occurred in content#view

You have a nil object when you didn't expect it!
The error occurred while evaluating nil.classify
[RAILS_ROOT]/app/models/content/content_model_generator.rb:16:in `content_model'

* URL: http://www.mywebiva.com/website/content/view/2
* Parameters: {"action"=>"view", "path"=>["2"], "controller"=>"content"}
* Rails root: /home/Webiva
* User Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; da; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8* Process: 2465
* Server : ubuntu

[RAILS_ROOT]/app/models/content/content_model_generator.rb:16:in `content_model'
[RAILS_ROOT]/app/controllers/content_controller.rb:116:in `generate_active_table'
[RAILS_ROOT]/app/controllers/content_controller.rb:155:in `view'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `send'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `perform_action_without_filters'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/filters.rb:617:in `call_filters'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
[RAILS_ROOT]/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
[RAILS_ROOT]/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/rescue.rb:160:in `perform_action_without_flash'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/flash.rb:146:in `perform_action'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `send'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `process_without_filters'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `process'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:391:in `process'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:386:in `call'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:437:in `call'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:87:in `dispatch'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:121:in `_call'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:130
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call'
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call'
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/query_cache.rb:9:in `cache'
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/query_cache.rb:28:in `call'
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/head.rb:9:in `call'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/session/abstract_store.rb:122:in `call'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/failsafe.rb:26:in `call'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/lock.rb:11:in `synchronize'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:114:in `call'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/reloader.rb:34:in `run'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:108:in `call'
[RAILS_ROOT]/vendor/rails/railties/lib/rails/rack/static.rb:31:in `call'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/urlmap.rb:46:in `call'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/urlmap.rb:40:in `each'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/urlmap.rb:40:in `call'
[RAILS_ROOT]/vendor/rails/railties/lib/rails/rack/log_tailer.rb:17:in `call'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/content_length.rb:13:in `call'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/chunked.rb:15:in `call'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/handler/mongrel.rb:61:in `process'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:159:in `process_client'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `each'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `process_client'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `initialize'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `new'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `initialize'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `new'
/var/lib/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `run'
[RAILS_ROOT]/vendor/gems/rack-1.0.0/lib/rack/handler/mongrel.rb:34:in `run'
[RAILS_ROOT]/vendor/rails/railties/lib/commands/server.rb:111
/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
script/server:3

Notes

The custom module status page does not look good:
INVALID MODEL: test (Destroy) INVALID

Any ideas?

Comments and changes to this ticket

  • atmorell

    atmorell September 5th, 2010 @ 07:50 AM

    I am not sure what happened but after rebooting my server this morning, all "Custom Content Modules" seems to be fine except the first entry I created. Status is INVALID MODEL: test (Destroy) and the server just hangs if I try to remove the model. No logs in the console.. everything just hangs.

    Any ideas on how I can cleanup this manually?

  • Pascal Rettig

    Pascal Rettig September 5th, 2010 @ 08:04 AM

    I think the first problem may just have been caused buy the background process not running when you created the content model. Why the destroy isn't working I'm not sure, I'll leave the bug open and take a look.

    You can clean up the page by manually deleting the offending entry from the "content_models" table.

  • atmorell

    atmorell September 5th, 2010 @ 03:28 PM

    Maybe it would be useful to have a have warning after logging in with an administrator if there is a problem with the background process... :/

  • Pascal Rettig

    Pascal Rettig September 20th, 2010 @ 10:42 AM

    • State changed from “new” to “open”
  • Pascal Rettig

    Pascal Rettig November 9th, 2010 @ 01:55 PM

    • Milestone set to 1.0 Release
    • Milestone order changed from “192440” to “0”
  • Pascal Rettig

    Pascal Rettig November 17th, 2010 @ 10:22 AM

    • State changed from “open” to “resolved”

    Added a warning in development mode on the dashboard if starling is not running.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Shared Ticket Bins

People watching this ticket

Referenced by

Pages