# "No action responded to yaml" when exporting (admin/export) **URL:** \ **Category:** Radiant CMS\ **Created:** [August 15, 2006, 2:20pm UTC](https://www.ruby-forum.com/t/no-action-responded-to-yaml-when-exporting-admin-export/64894 "2006-08-15T14:20:10Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\ **Post date:** [August 15, 2006, 2:20pm UTC](https://www.ruby-forum.com/t/no-action-responded-to-yaml-when-exporting-admin-export/64894/1 "2006-08-15T14:20:10Z")
Hello. I get the following when trying to export my radiant site (radiant 0.5.2 gem). Any hints will be appreciated. Thanks. --M * * * Processing ExportController#yaml (for 81.75.232.214 at 2006-08-14 20:51:55) [GET] Session ID: 6e30eceffd214d1b13cc731ee98ade0c Parameters: {“action”=\>“yaml”, “controller”=\>“admin/export”} ActionController::UnknownAction (No action responded to yaml): /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action\_controller/filters.rb:368:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in`perform\_action\_without\_rescue’ /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in`perform\_action\_without\_rescue’ /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action\_controller/rescue.rb:82:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in`process\_without\_filters’ /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action\_controller/filters.rb:377:in `process_without_session_management_support' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:in`process’ /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:in `dispatch' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/rails.rb:73:in`process’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:577:in `process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:576:in`process\_client’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:676:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:676:in`run’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:663:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/configurator.rb:257:in`run’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/configurator.rb:256:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:127:in`run’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/command.rb:199:in `run’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel\_rails:235 ---
**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\ **Post date:** [August 17, 2006, 11:46am UTC](https://www.ruby-forum.com/t/no-action-responded-to-yaml-when-exporting-admin-export/64894/2 "2006-08-17T11:46:57Z")
Hello. Did anyone experience the same issue when exporting? Thanks. --M ---------- Forwarded message ---------- From: Maurizio B. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Date: Aug 14, 2006 8:55 PM Subject: “No action responded to yaml” when exporting (admin/export) To: removed\_email\_address@domain.invalid Hello. I get the following when trying to export my radiant site (radiant 0.5.2 gem). Any hints will be appreciated. Thanks. --M * * * Processing ExportController#yaml (for 81.75.232.214 at 2006-08-14 20:51:55) [GET] Session ID: 6e30eceffd214d1b13cc731ee98ade0c Parameters: {“action”=\>“yaml”, “controller”=\>“admin/export”} ActionController::UnknownAction (No action responded to yaml): /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action\_controller/filters.rb:368:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in `perform\_action\_without\_rescue’ /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in `perform\_action\_without\_rescue’ /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action\_controller/rescue.rb:82:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in `process\_without\_filters’ /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action\_controller/filters.rb:377:in `process_without_session_management_support' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:in `process’ /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:in `dispatch' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/rails.rb:73:in `process’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:577:in `process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:576:in `process\_client’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:676:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:676:in `run’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb:663:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/configurator.rb:257:in `run’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/configurator.rb:256:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:127:in `run’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/command.rb:199:in `run’ /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel\_rails:235 ---
**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\ **Post date:** [August 17, 2006, 3:56pm UTC](https://www.ruby-forum.com/t/no-action-responded-to-yaml-when-exporting-admin-export/64894/3 "2006-08-17T15:56:21Z")
Hi Maurizio, My admin/export works fine, but I’m not running from the gem. What happens if you run this from Radiant’s root directory: ruby test/functional/admin/export\_controller\_test.rb ? In the meantime, if you need to backup/copy/move your database, you can use mysqldump: mysqldump -u mysql\_username -p radiant\_database\_name \> output\_filename.sql And to restore: mysql -u mysql\_username -p radiant\_database\_name \< output\_filename.sql Or to copy from one db to another in one fell swoop (development to production, for example): mysqldump -u mysql\_username -p radiant\_development | mysql -u mysql\_username -p radiant\_production -James ---
**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\ **Post date:** [August 17, 2006, 4:08pm UTC](https://www.ruby-forum.com/t/no-action-responded-to-yaml-when-exporting-admin-export/64894/4 "2006-08-17T16:08:22Z")
Hi James. Thanks for your feedback. On 8/17/06, James MacAulay [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > My admin/export works fine, but I’m not running from the gem. What > happens if you run this from Radiant’s root directory: > > ruby test/functional/admin/export\_controller\_test.rb I get the following: [http://pastie.caboo.se/9012](http://pastie.caboo.se/9012) –M ---
**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\ **Post date:** [August 17, 2006, 4:29pm UTC](https://www.ruby-forum.com/t/no-action-responded-to-yaml-when-exporting-admin-export/64894/5 "2006-08-17T16:29:26Z")
Hello John. The site (as an instance) is running fine, with several pages (BTW, thank you again for Radiant!). I’ve just a problem in exporting it. ---
**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\ **Post date:** [August 17, 2006, 4:17pm UTC](https://www.ruby-forum.com/t/no-action-responded-to-yaml-when-exporting-admin-export/64894/6 "2006-08-17T16:17:23Z")
Maurizio B. wrote: > I get the following: > > [http://pastie.caboo.se/9012](http://pastie.caboo.se/9012) Did you create config/database.yml? – John L. [http://wiseheartdesign.com](http://wiseheartdesign.com) ---
**Author:** ![Maurizio\_B](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b3f665/32.png) [@Maurizio\_B](https://www.ruby-forum.com/u/Maurizio_B)\ **Post date:** [August 17, 2006, 6:26pm UTC](https://www.ruby-forum.com/t/no-action-responded-to-yaml-when-exporting-admin-export/64894/7 "2006-08-17T18:26:46Z")
Maurizio B. wrote: > Hello John. The site (as an instance) is running fine, with several > pages (BTW, thank you again for Radiant!). I’ve just a problem in > exporting it. Ok, I think I found the problem. It’s fixed in head: [http://dev.radiantcms.org/radiant/changeset/103](http://dev.radiantcms.org/radiant/changeset/103) The problem was in app/controllers/admin/export\_controller.rb with this line: model :exporter, :user, :page, :page\_part, :snippet, :layout It should be: model ‘radiant/exporter’, :user, :page, :page\_part, :snippet, :layout I’m not sure why this only showed up in instance mode. Since you probably don’t want to wait another couple of weeks for the next release of Radiant, you have two options: 1. Make the appropriate change in your gem source directory 2. Run it in application mode instead of instance Let me know if that fixes your problem. – John L. [http://wiseheartdesign.com](http://wiseheartdesign.com)