I'm guessing this isn't a bug, since you've demonstrated working copies, so I'm probably just missing some configuration step, but I've attached a screenshot to explain the problem I'm seeing. As far as I can tell, this was affecting not just my subtheme, but the Omega base theme as well, when I set it as the default theme. I think the only configuration change I made was to turn on the grid overlay option, leaving it disabled on page load.
I just updated my dev7 site and installed your theme since it looks like it's a really powerful base theme, so I'm pretty sure I have a clean install. Do you have any suggestions for figuring this one out?
Comment | File | Size | Author |
---|---|---|---|
#4 | first-screenshot.png | 64.68 KB | safetypin |
#2 | Screen shot 2010-08-28 at 1.59.52 PM.png | 64.68 KB | safetypin |
#1 | Screen shot 2010-08-28 at 2.30.29 PM.png | 56.51 KB | safetypin |
Comments
Comment #1
safetypinJust started playing around with the content layout options, and putting both sidebars first, I get the appropriate layout, but it moving both sidebars to the left of the main content yields the attached results, both sidebars overlay the main content.
Comment #2
safetypinHrm. I guess I forgot to attach the first screenshot, so here it is.
Comment #3
safetypinHrm. I guess I forgot to attach the first screenshot, so here it is.
Comment #4
safetypinWeird. Maybe there's something about that file name d.o doesn't like.
Comment #5
sangeight CreditAttribution: sangeight commentedReplacing line 207 with this bit did the trick for me.
$sl_pull = (!isset($vars['page']['sidebar_second']) || count($vars['page']['sidebar_second']) == 0 ) ? $content_width - $sidebar_first_width : $content_width - $sidebar_first_width - $sidebar_second_width;
Not sure $vars['page']['sidebar_second'] will always be an array.
EDIT: preprocess-page.inc is the file i'm talking about
Comment #6
sangeight CreditAttribution: sangeight commentedMore changes required within template.php
Need to check for an empty array rather than null.
Comment #7
himerus CreditAttribution: himerus commentedThanks guys for continuing to debug this.
I believed that the issue was fixed in the last dev release, and should have made the last tagged release.
I may not have the proper use cases setup in my test environment, but thought I had got all the appropriate issues for each layout type.
I will look at this further as soon as I get a chance over the next couple of days!!
Comment #8
himerus CreditAttribution: himerus commentedCould you guys both help me to test this bug in the current beta6 state by if you haven't already, installing the Omega Tools module, and exporting your theme settings so that I may use an exact copy that is demonstrating the bug?
You can either paste the settings here, or attach a text file with the data in it... This will help me replicate the bug, as I was completely sure I had finally squished this one in most use cases and positions for the sidebar layouts.
If I can just test this in the buggy format, I will quickly get this resolved and committed and released in a new tagged version.
Comment #9
tnanek CreditAttribution: tnanek commentedI have been experimenting with this as a base theme (actually Gamma) and quickly saw this issue. I am getting a screen similar to the first screenshot (though more colored since this is a Gamma subtheme).
Here's my export of current settings:
Comment #10
safetypinHere's my settings export:
Comment #11
himerus CreditAttribution: himerus commentedOkay, I think I have this solved in the latest commits.
My sandbox is working in both the above configurations, and in any configuration I could test, along with each configuration WITH sidebars combined.
Please revert the files as appropriate. I took a different approach as the first_last_content layout option wasn't utilizing a feature built into the API.
The 'width' property is the maximum amount the sidebar could be pulled, which in this case would be the full content width minus the width of the current sidebar.
By using the $content_regions['sidebar_first']['pull'] method, the opposite sidebar (related item) is added to the 'conditions' array, and assigned a type of TRUE, which tells the function that if the related sidebar (second) DOES exist, to subtract the width of sidebar_second from the pull distance.
This has been committed, and will be tagged in the BETA7 release as soon as I look over a few other issues.
Comment #12
gafenn08 CreditAttribution: gafenn08 commentedI Just tested this after downloading the new beta7 release and it is working for me! Thanks for the quick fix.
Comment #13
himerus CreditAttribution: himerus commentedGreat... marking as fixed for now... I'm sure other weird scenarios might crop up where the sidebar sizing/positioning causes issue, but another issue would be probably appropriate in that case.
Comment #14
tnanek CreditAttribution: tnanek commentedThis is working for me as well, thanks!
Comment #15
liberatrJake,
I found the initial experience with Gamma pretty confusing, as far as the "sidebars combined" experience was concerned.
I tried to move all of my "sidebar first" content to "sidebar second" and it was still rendered inside the "sidebar first" region of the page.tpl.php and on the left side of the page.
Once I started pecking here in the issue queue, I got the hint that there was a theme setting for this.
Documentation? I see that you do have this listed as a feature in your handbook page.
Omega didn't seem to have the same default behavior as Gamma. Maybe you could just put a comment in the gamma.info file "First and Second Sidebars are combined by default." That way it hits me in the face when I make it the default theme.