#2555 Dynamic layout - self.class.layout doesn't work in 2.3.2 - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#2555 ✓stale

Dynamic layout - self.class.layout doesn't work in 2.3.2

Reported by rubynewbie | April 24th, 2009 @ 09:35 AM | in 3.x

I have upgraded to 2.3.2 and I am determining layouts based on URL in the application.

In application_controller, get_layout_details gets the layout information and sets self.class.layout (It is called before every call as it is set as before_filter for application_controller and working in earlier version)

Home page renders fine. When user makes a search, a 302 redirect happens internally and then there is no layout on results page. Forcing a layout :file_name in searchresults_controller is also not working.

I found one other person talking about a hack to make it work -

http://jystewart.net/process/200...

I am not using the theme plugin, so what should I do to make it work in rails 2.3.2

Please advise.

Thanks

Comments and changes to this ticket

You flagged this item as spam.
Steve St. Martin April 16th, 2010 @ 01:10 AM
- Assigned user set to “Ryan Bigg”
Can you provide more detail as to what it is your trying to accomplish and/or code examples? for now can probably mark as incomplete or needs-more-info
Ryan Bigg April 16th, 2010 @ 01:29 AM
- State changed from “new” to “incomplete”
Jeremy Kemper May 4th, 2010 @ 06:48 PM
- Milestone changed from “2.x” to “3.x”
[bulk edit]
Rohit Arondekar October 14th, 2010 @ 10:49 AM
- State changed from “incomplete” to “stale”
- Importance changed from “” to “”
Marking ticket as stale. If this is still an issue please leave a comment with suggested changes, creating a patch with tests, rebasing an existing patch or just confirming the issue on a latest release or master/branches.