As mentioned in another issue, I'm evaluating the Omega theme for my current project. We're currently using Fusion Core with a custom sub-theme.

Does the Omega theme have collapsible regions? I've read through the documentation and played around with the theme, and my guess is "no," but I want to double-check.

Part of our current design takes advantage of the fact that if there is nothing in [sidebar-last], for example, the main content area automatically fills in the [sidebar-last] space. Is this possible with the Omega theme?

Comments

himerus’s picture

himerus CreditAttribution: himerus commented

By collapsible regions, do you mean a link/button/etc to toggle a regions visibility? Like you'd see in blocks sometime to click on the header and expand or collapse the block's content??
If this is the question, then no... that is not present (in the 6.x version, but is planned for the 7.x-2.x branch)

In your last line:

Part of our current design takes advantage of the fact that if there is nothing in [sidebar-last], for example, the main content area automatically fills in the [sidebar-last] space. Is this possible with the Omega theme?

This functionality IS true.... If you have your "content area" (sidebars AND content regions) set to a 4-8-4 layout in settings, and on some pages ALL regions are used and populated with data, it will respect this setting, BUT if in another area, there are no blocks or content present in sidebar second/last, and only the first sidebar and content regions have data, then the layout would be 4-12, thus still taking up the full width of the page.

Let me know if this answers your question!!

rhymeswithcamera’s picture

rhymeswithcamera CreditAttribution: rhymeswithcamera commented

Thanks for your response. Yes, I'm referring to the second scenario (sorry, still learning the right lingo). That's the behavior I'm expecting. For example, if I go to the Modules admin page, I'm expecting for the list to take up 12 columns (8-4) in a 4-8-4 setup. Right now, it's only displaying in the middle (8) column. I have no blocks assigned to [sidebar-last] at the moment. Let me play around with it a bit more on a clean install; I may be having some caching issues.

himerus’s picture

himerus CreditAttribution: himerus commented

If you still have the issue where it's not adding the empty space to the content region, post a screenshot for me... this SHOULD work... and is DEFINITELY the desired behavior...

rhymeswithcamera’s picture

rhymeswithcamera CreditAttribution: rhymeswithcamera commented

Well, it appears that it's my site and not the theme. Here's what I discovered:

Test A: Fresh installation
1. On fresh Drupal install, enable Garland and Omega (default) themes.
2. Go to Blocks admin page, and make sure same blocks are enabled in left sidebar for both themes. [NOTE: Theme switching works as expected.]
3. Go to Modules page. The expected and actual result is the Modules list displays in columns 5-16 (in 16-column layout).
4. Switch to Garland theme. Results are as expected, even though it's not grid-based: Module list fills content area; no empty right sidebar area.
5. Enable Fusion Core theme. Make default. "Modules" page results are as expected (same as Omega results).

Test B: Custom installation (my project)
1. Same as #1 and #2 above. Two differences to note:
(1) Theme switching does not work on Blocks admin page.
(2) The yellow-highlighted region titles aren't displayed.
2. Go to Modules page. Expected result is for Modules list to display in columns 5-16. Actual result is it displays in columns 5-12 (in 16-column layout).
3. Switch to Garland theme. Results are as expected, even though it's not grid-based: Module list fills content area; no empty right sidebar area.
4. Enable Fusion Core theme. Make default. "Modules" results same as Omega.

Summary: All works as expected for grid-based and non-grid-based themes on a fresh installation. On my custom site, non-grid themes work as expected. Grid-based (Fusion Core and Omega) don't. The crazy thing is that yesterday before I installed Omega for the first time, my Fusion Core/sub-theme combination was working as designed. Even if I uninstall Omega now, I can't get my Fusion combo to work correctly anymore. I do have a backup, but I was hoping to get things working on Omega.

I believe this is something on my end to fix. I'll keep you posted if/when I resolve this issue.

himerus’s picture

himerus CreditAttribution: himerus commented

Truly bizarre...

I "think" this must be related to somehow on the modules page, (since this is happening for Fusion AND Omega) that somehow, some data is being passed into the content for right sidebar (EVEN if it's just a silly empty div or nbsp) and our themes are attempting to render the region thinking that there IS valid content there...

If I could see a screenshot of the layout (with omega) and a copy/paste of the relevant code that is present in the rendered HTML (view source) of the page (maybe attached as a text file so it's not too long in here) I might be able to help you track it down....

rhymeswithcamera’s picture

rhymeswithcamera CreditAttribution: rhymeswithcamera commented
Status: Active » Closed (works as designed)

Okay, so you're never going to believe this craziness. I reverted back to my backup from yesterday - when everything was working properly pre-Omega. I then installed, enabled and made Omega the default. Worked exactly as expected. Switched back to my custom Fusion subtheme. Still okay. Installed the Omega subtheme I created yesterday (without any custom CSS files). Worked as expected. I am now happily clicking between my smorgasbord of themes and all is working as it should.

So it seems that I clearly had a hiccup - more like a burp - yesterday for some reason, but all is well now. I really appreciate your offer to help. Thank you! Now onto making the Fusion>Omega transition...

murrayw’s picture

murrayw CreditAttribution: murrayw commented

For D7 version, when debug info is turned on in the theme the sidebars are shown, even with no content in them. The CSS class is container-12 for all of the divs but the main content area when displayed still takes up only 6 units (the default). I don't know why this but probably related to some CSS emitted by debug. It could certainly explain the intermittent behaviour described above.

minneapolisdan’s picture

minneapolisdan CreditAttribution: minneapolisdan commented

Ah ha, thank you, I was wondering about this myself. Turn off debug info, and the empty sidebars don't show/take up space.