Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rails3 suddenly html-escapes inherited_resource html responses #50

Closed
argl opened this issue Apr 22, 2010 · 5 comments
Closed

rails3 suddenly html-escapes inherited_resource html responses #50

argl opened this issue Apr 22, 2010 · 5 comments

Comments

@argl
Copy link

argl commented Apr 22, 2010

as the subject says, all of a sudden (around april 21/22 2010), html responses from an inherited_resources controller escapes the html (yikes!). using edge rails3.

@josevalim
Copy link
Contributor

I cannot reproduce it. Just created a new app from Rails source code using Inherited Resources and everything works.

I also doubt this is an Inherited Resources issues. Are you using Haml? Which Inherited Resources version? Please give me more information.

@argl
Copy link
Author

argl commented Apr 22, 2010

i doubt it as well ;) yes, we're using haml for the html, latest git version as well. heres the relevant ections form the app's gemfile:

gem "rails", :git => "git://github.com/rails/rails.git"
gem 'haml', :git => 'git://github.com/nex3/haml.git'
gem 'inherited_resources', :git => "git://github.com/josevalim/inherited_resources.git"

i'll try to create a minimal test case to reproduce and report back.

thanks a 10^6 for the quick response.

@josevalim
Copy link
Contributor

It works fine with ERB. I bet on Haml issue. :) Please let me know!

@argl
Copy link
Author

argl commented Apr 22, 2010

i think we've found it, we were rendering a haml partial from an erb template (don't ask). switching over to using haml only seems to solve the issue. nothing wrong with inherited_resources.

@josevalim
Copy link
Contributor

Ok, thanks for reporting back! Closing!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants