Responsive Classic (built in to Zen Cart v1.5.5) [Support Thread]

[lat9]

I'm trying to configure the Responsive Classic template to have only a left sidebox. I've got the layout settings set to
- Globally disable the right sidebox
- Set the left sidebox width to 175px

When I display a page, the following widths are shown using FireBug:
- #contentMainWrapper ... 1427
- .col175 ....................... 158 + 6 (margin)
- .col795 ....................... 7 (margin) + 1121

That's a total of 1292 being consumed by the content -- where did the other 135 pixels "go". I see an unwanted line of background color on the righthand side of the display.

[lat9]

It gets weirder. On the less-populated pages, I'm seeing my .col795 section's width is 653.

[dbltoe]

csslint also throws warnings on "ID selectors" WOW and for "CSS3 not supported in IE6 or IE7" REALLY

@dbltoe, tools great but anyone that doesn't understand my above comment will spend endless hours trying to fix something that's not broken.

Couldn't agree more. Not for the faint of heart. You have to reach a point between working and perfect that you can live with.

[dbltoe]

template_default

stylesheet.css

CSS lint found 0 errors and 201 warnings

The majority are for the use of "ID Selectors" maybe I'm stuck in an era that just doesn't get the "needs" or "complaints" of today's Zen Cart Community.

In this case, I couldn't disagree more. Us "old" guys may have to make a few more stops on the road trip than we did in our youth but, we get there just as well. What's interesting is the ID Selectors are suggested by the inspector in Chrome.
I hope that I'm keeping my mind active by constantly challenging my thinking. The community owes you and Anne a great deal of respect. There is always going to be those people who won't fish for themselves and the "what have you done for me lately" crowd. If they p|&& you off one day and not the next, then it's you that decides to be that way. I think you can just keep thinkin'; "No Thanks, I'd Rather Be Happy!" I know we're happy to have you.

[dbltoe]

Working on a method to initially perform a quick color change with the responsive_classic template. zip currently available at our test site of netzencommerceDOTcom. First category on the left. Remember, this is a work in progress.

[rbarbour]

I'm trying to configure the Responsive Classic template to have only a left sidebox. I've got the layout settings set to
- Globally disable the right sidebox
- Set the left sidebox width to 175px

When I display a page, the following widths are shown using FireBug:
- #contentMainWrapper ... 1427
- .col175 ....................... 158 + 6 (margin)
- .col795 ....................... 7 (margin) + 1121

That's a total of 1292 being consumed by the content -- where did the other 135 pixels "go". I see an unwanted line of background color on the righthand side of the display.

It gets weirder. On the less-populated pages, I'm seeing my .col795 section's width is 653.

I'm not spending to much time explaining because frankly It's getting old (no offense) Cindy.

This was changed in 2.0 of the DIY Package

2.) 2.0 adds 98 new (px & %) column calculations.
3.) 2.0 adds side column width flexibility in (10px increments).
4.) 2.0 allows ADMIN controlled side column widths using the existing ZC stock Column Width - Left and Column Width - Right configurations

Adding a width of 175 is creating col175 which doesn't exist because it's not an increment of 10

Change your 175 to 170 or 180.

Last Post

[lat9]

I'm trying to configure the Responsive Classic template to have only a left sidebox. I've got the layout settings set to
- Globally disable the right sidebox
- Set the left sidebox width to 175px

When I display a page, the following widths are shown using FireBug:
- #contentMainWrapper ... 1427
- .col175 ....................... 158 + 6 (margin)
- .col795 ....................... 7 (margin) + 1121

That's a total of 1292 being consumed by the content -- where did the other 135 pixels "go". I see an unwanted line of background color on the righthand side of the display.

It turns out that the site's previous setting (Left Sidebox Width = 175px) confused the heck out of the responsive handling since the .col175 didn't have any styling within the responsive.css file.

Changing the site's settings to 150px for that sidebox width made everything "happy".

That leads to the question: Are the built-in column widths documented anywhere (besides inspecting the responsive.css file)?

[dbltoe]

It gets weirder. On the less-populated pages, I'm seeing my .col795 section's width is 653.

setting up a test to look at it now. Are you moving all boxes to the left or only a select few?

[dbltoe]

Right now working on what the contentMainWrapper does with various screen sizes. The call .onerow-fluid is apparently the controller but a battle is going on between the stylesheet.css, responsive.css and responsive_default.css.

With a 768-1500 screen size, the stylesheet.css sets padding to 0, the responsive.css sets margin to auto !important, and the responsive_default.css sets the width at 100% !important.

With a screen size over 1500, the stylesheet.css set padding to 0, the responsive.css sets margin to auto!important, and the responsive_default.css has no width listing. When the customer's screen goes over 1500, it displays "dead space" on the left and right of the screen.

Adding

.onerow-fluid {width:100% !important;} 

to the min-width: 1500px call around line 411 of the responsive_default.css. Otherwise the .onerow-fluid around line 57 in the stylesheet.css overrides the width to 75%.

Just wanted to confirm that this didn't munge something elsewhere.
THANX

[lindasdd]

When I switch to the 'out of the box' version of this template, it doesn't center properly.

It is as though the whole center wrapper (impacted by .onerow-fluid) is set up as float:left inside its container rather than margin:0 auto.

Is that normal? If so...why?

(local install so no link to site possible)

Edit: Upon further investigation it appears to be because .col670 has an attribute of width:68.2594% when ideally it should be 100%

Or is it set at 68% for a reason.