This project is archived and is in readonly mode.

#4422 ✓resolved

Rails 3 Beta 3 label form helper causes "stack level too deep" exception

Reported by Hates_ | April 16th, 2010 @ 11:09 PM

Forms perviously working in beta1/beta2 now throw a "stack level too deep" on any form containing a label. For example my Devise sign in form:

<% form_for resource_name, :as => resource, :url => session_path(resource_name) do |f| -%>
  <p><%= label_tag :email %></p>
  <p><%= f.text_field :email %></p>

Returns the error:

stack level too deep
Extracted source (around line #4):

1: <h2>Sign in</h2>
3: <% form_for resource_name, :as => resource, :url => session_path(resource_name) do |f| -%>
4:   <p><%= f.label :email %></p>

Comments and changes to this ticket

  • Hates_

    Hates_ April 17th, 2010 @ 12:40 AM

    • Title changed from “Beta 3 label form helper causes "stack level too deep" exception” to “Rails 3 Beta 3 label form helper causes "stack level too deep" exception”
  • Diego Carrion

    Diego Carrion April 17th, 2010 @ 02:06 AM

    This didn't happen with me. I created a new application, made an scaffold and everything was fine, even after installing Devise and trying again.

    Maybe a conflict with some gem or plugin?

  • tcc

    tcc April 17th, 2010 @ 06:29 AM

    I'm seeing the same problem:

    I'm running on Mac OSX, ruby 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0]

  • tcc

    tcc April 17th, 2010 @ 06:35 AM

    Copied stacktrace for more info:

    Started GET "/users/sign_up" for at 2010-04-15 11:53:34
      Processing by Devise::RegistrationsController#new as HTML
    ActionView::Template::Error (stack level too deep) on line #6 of /
    3: <%= form_for(resource, :as => resource_name, :url =>
    registration_path(resource_name)) do |f| %>
    4:   <%= devise_error_messages! %>
    6:   <p><%= f.label :email %></p>
    7:   <p><%= f.text_field :email %></p>
    9:   <p><%= f.label :password %></p>
    app/views/devise/registrations/new.html.erb:6:in `_render_template__160276350_2202163960_0'
    Rendered /Library/Ruby/Gems/1.8/gems/actionpack-3.0.0.beta3/lib/
    action_dispatch/middleware/templates/rescues/_trace.erb (2.4ms)
    Rendered /Library/Ruby/Gems/1.8/gems/actionpack-3.0.0.beta3/lib/
    Rendered /Library/Ruby/Gems/1.8/gems/actionpack-3.0.0.beta3/lib/
    action_dispatch/middleware/templates/rescues/template_error.erb within
  • tetsuo692

    tetsuo692 April 17th, 2010 @ 07:21 AM

    I have the same issue with an application create with rails 3.0.0.beta2.
    I update dependent gems with last version : "haml" "3.0.0.beta.3" and "mongoid", "2.0.0.beta3".
    And now everything works...

  • Hates_

    Hates_ April 17th, 2010 @ 10:10 AM

    After clearing out all my vendor gems, making sure I'm running the latest version of everything and doing a fresh "bundle install", this problem has gone away.

    Hopefully someone can close this bug.

  • Mathias Kretschek

    Mathias Kretschek April 18th, 2010 @ 01:38 AM

    • Assigned user set to “Ryan Bigg”
  • Lord Norlan Mumar

    Lord Norlan Mumar April 18th, 2010 @ 11:16 AM

    Experienced the same issue before, what I did I updated haml to version 2.2.23 (in Gemfile) and like Richard issued "bundle install", solved my problem.

  • Santiago Pastorino

    Santiago Pastorino April 18th, 2010 @ 11:44 PM

    • State changed from “new” to “resolved”
  • klkk

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href=""></a>

People watching this ticket