Closed (fixed)
Project:
Nitobe
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Reporter:
Created:
3 Aug 2008 at 23:23 UTC
Updated:
19 Aug 2008 at 01:21 UTC
Jump to comment: Most recent
I'm trying to do an install profile that enables this theme instead of Garland. The problem is that by default, the Navigation menu ends up in the admin_header region, as pictured in the attached screenshot. This is because there is no 'left' region, only 'right'.
I'm not really sure what can be done about this, apart from renaming 'right' to 'left' and that just seems awfully confusing. :P
| Comment | File | Size | Author |
|---|---|---|---|
| Picture 5.png | 57.37 KB | webchick |
Comments
Comment #1
webchickWell, as a workaround I'm doing:
That seems fine. It'd be neat if this theme could somehow do this automatically when it's enabled, but that might not be possible.
Comment #2
Anonymous (not verified) commentedYeah, I've noticed this when I enable the theme on a fresh install. I'm considering just rendering the content of the 'left' region in the right column above the 'right' content. I need to play around with it to see if I can have it render there without exposing that region as an option.
I don't really like the idea of updating someone's database when they enable the theme. It makes me feel dirty.
Comment #3
Anonymous (not verified) commentedI added a region with the internal name 'left' and the pretty name 'Upper Sidebar'. The 'right' region now has the pretty name 'Lower Sidebar'. Each, if present, is printed in the right visual sidebar with 'left' rendered above 'right'. This accommodates switching from a theme that has left region content.
This fix is addressed in:
nitobe.infov 1.4page.tpl.phpv 1.8Comment #4
webchickOh nice. This is a much smoother fix than my dirty hack. Thanks a lot!
Comment #5
Anonymous (not verified) commentedI think this will also make it easier adapting the theme for right-to-left languages whenever I get around to that.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.