plainblack.com
Username Password
search
Bookmark and Share
View All Tickets
one over three template  (#11433)
Issue

it appears that position one should have the class of wg-top similar to one-over-two, and also following be added to the layout.css:

.oneovertwo .wg-top {
  width: 100%;
}

change to :

.oneovertwo .wg-top, .oneoverthree .wg-top {
  width: 100%;
}


though that didn't fix my problem. I didn't use the top position, or the far right of the three positions, and now the two remaining columsn are smooshed and overlapping overeachother. So I thought seeting the top position1 to be 100% would fix it.


It looks great when I'm logged in and admin is turned off, but once I log out, they overlap each other again.

Solution Summary
Comments
preaction
0
2/23/2010 5:50 pm
I am unable to reproduce this using a default style_03 site. Could you make a demo with the behavior so I can see / play with?
rogier
0
2/24/2010 3:27 am
OK, I'll look into the suggested changes. Position one should definitely have a "wg-top" class. I agree that the CSS should be consistent, but the "wg-top" style is not strictly necessary, so I'll just remove it.

I can't think of an explanation for the overlapping problem. The layout styles should be pretty bulletproof, even if there are empty columns. Like Doug said: can you make a demo or post a link or a screenshot?
rogier
0
2/24/2010 3:29 am
Doug, you may assign template bugs to me, if they are related to the new default templates.
perlDreamer
0
2/24/2010 11:48 am
Reassigning to rogier, since it's his fault anyway.
rogier
0
2/24/2010 2:42 pm
What's got into you? Is this Colins evil twin I'm speaking to? :-)
perlDreamer
0
2/24/2010 7:12 pm
Sorry.  That was a poor attempt at a joke.  It's not really your fault, you just asked that the bug is assigned to you.
rogier
4
2/25/2010 3:10 am
You know I'm only pretending to be offended, right?
perlDreamer
0
3/1/2010 12:11 pm
I thought so, but realized that if I was wrong that an apology was safer.
perlDreamer
0
4/5/2010 8:41 pm
Joking aside, has there been any progress at looking into this template?
elnino
0
4/5/2010 11:54 pm
I've attached screen shots. the far right column is only viewable by admin. so I have a admin on screen shot, admin off screenshot and a screenshot when logged out (which shows the far two left columns being overlapped.

elnino
0
4/6/2010 0:04 am
And actually, I'm finding that the adminon/off can really affect things either for the good or bad. I've now two sites that somewhat similarly:

In the templates, usually the content is in div, but when admin is on, the template embeds a table inside that div.

This RFE's site, the admin on, actually spreads the columns apart appropriately and displays them as *I* think they should when admin is off.

On another site I'm working on,  I have a custom table-based template, and the tables that "admin on" embedds is actually spreading them over WAY too far, causing the articles to overlap, and make it difficult to move assets around.

So I guess what I'm wondering about these tables of id="position#" and class="content" - they should not exceed their container's defined width, nor should they collapse less than their container's width. - and perhaps that is the bug? I'm not quite sure where these are defined.

Or perhaps class="content" should be "wg-content" or something, because I'm SURE others prone to using "content" in their own css files.

hopefully that makes sense.
rogier
0
4/7/2010 6:59 am
Quoting perlDreamer "Joking aside, has there been any progress at looking into this template?"

The "wg-top" style could be removed from layout.css, but that's not really a bug.

Elnino's problem is this: the tablecell (td) with id="contentContainer" does not have a width, nor does the table itself. This makes the td wrap its contents: it's only as wide as is necessary to contain the header (h2).

The columns in the layout are set to 32%, this means their width will be 32% of whatever the width is of the containing element. That containing element is now 227px wide (just wide enough to fit the h2, 'cause that's how tables work), so the columns are about 73px each. That's not what you want in this case, but it is how it's supposed to work.

Best solution to make the td wider is this: add width="100%" to the table. This will force the contentContainer td to use all available space.

This is not a bug in the layout template.
perlDreamer
0
4/7/2010 8:41 am
Thanks for looking into this, Rogier
rogier
0
4/7/2010 8:54 am
No problem.
Details
Ticket Status Resolved  
Rating4.0 
Submitted Byelnino 
Date Submitted2010-02-23 
Assigned To rogier  
Date Assigned2010-02-24 
Assigned ByperlDreamer 
Severity Minor (annoying, but not harmful)  
What's the bug in? WebGUI Stable  
WebGUI / WRE Version 7.7.28  
URLuse/bugs/tracker/11433
Keywords
Related Files
Ticket History
4/8/2010
10:29 AM
Resolved perlDreamer
4/7/2010
8:54 AM
Pending rogier
4/7/2010
8:42 AM
Resolved perlDreamer
4/5/2010
11:54 PM
Pending elnino
4/5/2010
8:41 PM
Feedback Requested perlDreamer
2/24/2010
11:48 AM
Assigned to rogier perlDreamer
2/24/2010
3:27 AM
Pending rogier
2/23/2010
5:50 PM
Feedback Requested DBell
2/23/2010
5:47 PM
Assigned to DBell DBell
2/23/2010
4:42 PM
Ticket created elnino
© 2012 Plain Black Corporation | All Rights Reserved