Rails controller processing as HTML instead of XML

Question

I've recently upgraded from Ruby 1.8.6 and Rails 2.3.4 to Ruby 1.9 and Rails 3.0.3.

I have the following controller:

class ChartController < ApplicationController

  before_filter :login_required

  respond_to :html, :xml  

  def load_progress  

    chart.add( :series, "Memorized",  y_memorized )
    chart.add( :series, "Learning",   y_learning  )
    chart.add( :series, "Mins / Day", y_time      )  
    chart.add( :user_data, :secondary_y_interval, time_axis_interval )

    respond_to do |fmt|
      fmt.xml { render :xml => chart.to_xml }
    end

    # Also tried
    # respond_with chart

  end   
end

However, when I call the 'load_progress method' I get the following:

Started GET "/load_progress.xml" for 127.0.0. Processing by ChartController#load_progress as HTML Completed 406 Not Acceptable in 251ms

I have also tried changing the respond_to block to

respond_with chart

But I get the same response. I've read all the new Rails documentation on the new respond_with format but I can't seem to elicit an XML response. Am desperately hoping someone has some ideas.

Zsolt · Accepted Answer · 2011-05-09 07:31:22Z

3

I had the same issue, and the following snippet worked for me:

  respond_to :xml
  def list
    @items = Item.all
    render :xml => @items
  end

406 can happen for several reasons - usually when one uses wrong MIME types -, but based on the rails guides when you create an XML response as described above, everything will be filled out correctly by rails.

There is one disadvantage of the above snippet. It will list every attribute of your model.

In your example I'm not sure whether the chart variable is initialized/visible or not.

answered May 9, 2011 at 7:31

Zsolt

1,48413 silver badges22 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Zsolt Over a year ago

additionally you may need a :format => :xml in your routes.rb for the proper controller

Andy Over a year ago

Yes, forcing the format in the routing seems to solve the problem.

Tim Stephenson · Accepted Answer · 2011-01-14 21:12:20Z

0

What you are doing looks right. Are you using Ruby 1.9.2? I know that 1.9.0 has problems, but I'm not sure it would explain this.

answered Jan 14, 2011 at 21:12

Tim Stephenson

8301 gold badge7 silver badges15 bronze badges

1 Comment

Andy Over a year ago

Yep, I'm on Ruby 1.9.2. Have seldom been so perplexed by Rails.

Collectives™ on Stack Overflow

Rails controller processing as HTML instead of XML

2 Answers 2

2 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related