#158 ✓resolved
Marty McGee

Error creating (saving) a new section immediately after installing

Reported by Marty McGee | November 4th, 2008 @ 06:49 PM

After installing adva_cms in a production environment successfully, updating my user profile successfully, and renaming my Home page and permalink successfully, I went to create a New Section and ran into this error. I tested this twice, once by creating a new Forum section, then again by creating a new Blog. IMPORTANT: The error only occurred when trying to create a new Forum section; creating a new Blog section worked just fine. This error should probably be considered URGENT since it kills the whole admin side of the application. Here is the error:

Processing Admin::SectionsController#create (for 76.102.80.147 at 2008-11-04 17:41:04) [POST]
Session ID: BAh7CToUcmV0dXJuX2xvY2F0aW9uQzoeSGFzaFdpdGhJbmRpZmZlcmVudEFj Y2Vzc3sIIgthY3Rpb24iCmluZGV4IgttZXRob2Q6CGdldCIPY29udHJvbGxl
ciIQYWRtaW4vc2l0ZXM6DGNzcmZfaWQiJWJkNmQ3YTdjMDI0MzBkOTk3MmFj
MzkzMzYwY2VhMmI0Ogh1aWRpBiIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxl
cjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA==--db24c8b68a021e29d5d276753e5c49d16b1b6c54
Parameters: {"commit"=>"Save", "site_id"=>"1", "authenticity_token"=>"e64e3ec1d6d5c9e69695923a7e72cf4820ffc0d9", "$

NoMethodError (undefined method admin_topics_path' for #<Admin::SectionsController:0x7feace063810>): /vendor/adva/engines/adva_cms/app/controllers/admin/base_controller.rb:32:insend' /vendor/adva/engines/adva_cms/app/controllers/admin/base_controller.rb:32:in admin_section_contents_path' /vendor/adva/engines/adva_cms/app/controllers/admin/sections_controller.rb:24:increate' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:1166:in send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:1166:inperform_action_without_filte$ /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:579:in call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:600:inrun_before_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:176:in call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:176:inaround_proc' /usr/lib/ruby/gems/1.8/gems/activesupport-2.1.2/lib/active_support/callbacks.rb:177:in call' /usr/lib/ruby/gems/1.8/gems/activesupport-2.1.2/lib/active_support/callbacks.rb:177:inevaluate_method' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:154:in call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:597:inrun_before_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:577:in call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:572:inperform_action_without_ben$ /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in perform_action_without$ /usr/lib/ruby/1.8/benchmark.rb:293:inmeasure' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in perform_action_without$ /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/rescue.rb:201:inperform_action_without_cach$ /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/caching/sql_cache.rb:13:in perform_action' /usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/connection_adapters/abstract/query_cache.rb:33:$ /usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/query_cache.rb:8:incache' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/caching/sql_cache.rb:12:in perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:insend' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:in process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:568:inprocess_without_session_ma$ /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/session_management.rb:130:in sass_old_proces$ /vendor/adva/gems/haml-2.0.3/lib/sass/plugin/rails.rb:19:inprocess' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:389:in process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:149:inhandle_request' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:107:in dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:insynchronize' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:120:indispatch_cgi' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:35:in dispatch' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/rack/adapter/rails.rb:54:inserve_rails' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/rack/adapter/rails.rb:74:in call' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/connection.rb:63:inpre_process' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/connection.rb:54:in process' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/connection.rb:39:inreceive_data' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.2/lib/eventmachine.rb:231:in run_machine' /usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.2/lib/eventmachine.rb:231:inrun' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/backends/base.rb:57:in start' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/server.rb:150:instart' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/controllers/controller.rb:80:in start' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/runner.rb:173:insend' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/runner.rb:173:in run_command' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/lib/thin/runner.rb:139:inrun!' /usr/lib/ruby/gems/1.8/gems/thin-1.0.0/bin/thin:6 /usr/bin/thin:19:in `load' /usr/bin/thin:19

Rendering /home/user/public_html/pursuebeauty.com/public/500.html (500 Internal Server Error)

Comments and changes to this ticket

  • Sven Fuchs

    Sven Fuchs January 9th, 2009 @ 01:50 PM

    • State changed from “new” to “resolved”

    I think this is now fixed. Marko did a bunch of work on the forum. The forum previously was not ready to use.

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 »

<p>Cutting edge cms, blog, wiki, forum ... plattform.</p>

<p>Find the code on <a href="http://github.com/svenfuchs/adva_cms/tree/master">GitHub: adva cms</a></p>

<p>Part of the business application framework <a href="http://www.advabest.org/">adva best</a>.</p>

People watching this ticket

Pages