# Depreciation warnings

**URL:** <https://www.ruby-forum.com/t/depreciation-warnings/192129>\
**Category:** Rails\
**Created:** [July 24, 2010, 1:18pm UTC](https://www.ruby-forum.com/t/depreciation-warnings/192129 "2010-07-24T13:18:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dee](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/58956e/32.png) [@dee](https://www.ruby-forum.com/u/dee)\
**Post date:** [July 24, 2010, 1:18pm UTC](https://www.ruby-forum.com/t/depreciation-warnings/192129/1 "2010-07-24T13:18:41Z")

</div>

I’m working with Rails 3.0.0.beta4 and found a spot where the input  
controls in the form disappeared. The code was using the old-style  
block notation (\<% rather than \<%=) with fields\_for in a deeply nested  
form. So, a fields\_for was nested within another fields\_for. There was  
no depreciation warning in the server output.

I suspect this might be a “won’t fix” but I could log it in Lighthouse  
anyway. Recommendations?

Also, what’s the official policy (if there is one) on what deprecated  
means? In my experience, sometimes depreciated rails code still works  
but you get a warning. Other times, I’ve seen it where the code  
doesn’t work anymore and still you get a warning, which seems more  
like “unsupported” at that point.