Home/ Questions/Q 534733
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T09:38:36+00:00

I think this has been asked before but even though I searched Google I

  • 0

I think this has been asked before but even though I searched Google I haven’t come up with a solution.

So this is what I’m trying to do in Rails 2.3.5:

layouts/application.html.erb:
<html>
  <head>
    ... some other stuff
    <%= yield :head %>
  </head>
  <body>
    <% content_for :head, "something that belongs in the head" %>
  </body>
</html>

Notice the yield before the content_for.

I know that Rails – by default – doesn’t allow the content of :head to be defined after yield has been used – makes sense.

I even tried hooking into the template render process but no success so far.

So my goal is to be able to define content_for inside partials/templates and have the “yield” somehow delayed and executed just before the response is send to the browser.

Has somebody come up with a solution?

Greetings and thanks,
Frank

Update
I’ll go with weppos’s idea and try myself on rack middleware. thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The rendering process first loads and executes the action template, then decorates the template with the selected layout.
    The layout is rendered from top to botton, thus you can’t add more content to :head after :head is already rendered.

    You need to change your strategy. Either place the fragment in a partial and attach it to your action views or use a post-processing strategy such as a Rack module/after_filter to alter the html code directly.

    I probably would try to find a better solution based on what I actually need. If you are encountering this issue, chances are the error is somewhere else, perhaps in the app architecture.

    • 0