This project is archived and is in readonly mode.
Per-request view paths and layouts
Reported by Andrew White | February 9th, 2009 @ 02:30 PM
The attached patch addresses some issues with layouts when they are being used with per-request view paths. The current implementation always refers to the class level view paths rather than the instance level view paths resulting in missing template errors when using template names that don't match between different view paths
The only issue that isn't address is the auto-detection of layouts which would require scanning of template directories on every request which isn't desirable. Since the main use case for per-request view paths is for some kind of theming of content then having consistent names for auto detection between different themes is probably what would be preferred anyway.
Comments and changes to this ticket
-
josh February 9th, 2009 @ 03:11 PM
- State changed from “new” to “open”
- Milestone cleared.
-
josh February 9th, 2009 @ 08:14 PM
- Assigned user changed from “josh” to “Yehuda Katz (wycats)”
-
josh February 21st, 2009 @ 05:41 AM
- State changed from “open” to “resolved”
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="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Andrew White
Gary Taylor
josh
Paweł Kondzior
Yehuda Katz (wycats)
Attachments
Referenced by
-
1974
Layout picked from wrong view_paths?
Josh, you can close #1919 as well since this ticket is es...