"No action responded to yaml" when exporting (admin/export)

Ruby Apps Radiant CMS
1

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:inperform_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:inperform_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:inprocess_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:inprocess’
/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:inprocess’
/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:inprocess_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:inrun’
/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:inrun’
/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:inrun’
/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

2

Hello. Did anyone experience the same issue when exporting? Thanks. --M

---------- Forwarded message ----------
From: Maurizio B. [email protected]
Date: Aug 14, 2006 8:55 PM
Subject: “No action responded to yaml” when exporting (admin/export)
To: [email protected]

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

3

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

4

Hi James. Thanks for your feedback.

On 8/17/06, James MacAulay [email protected] 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

–M

5

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.

6

Maurizio B. wrote:

I get the following:

http://pastie.caboo.se/9012

Did you create config/database.yml?

–
John L.
http://wiseheartdesign.com

7

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

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