Responsive Sheffield Blue v2.0

[jpda]

Hi Anne
When I viewed it last night it showed 2 on my screen and on my ipad, which is why I suggested the change.

So I went to your demo this morning and it also showed 2. Then I realized that I am on a new computer with a much larger screen and only using 2/3 of the viewing area. So maybe it is SUPPPOSED to go to 2 columns at a certain width to avoid too close buttons? Still, 2/3s of my large screen still seems large enough to view 3 columns. When changing the 45% to 30% (or even deleting it all together), it works. But I'm also aware that it may make other parts "NOT" work, so I'm trying to figure out why it is needed at all (the 45% that is).

Thanks
Linda

Hi Linda,
Changing 45% to 30% (lines 387 and 413) works but it will mess up the footer layout (if left column is on).
These settings in responsive_default.css overrule the computed setting $cols in "\includes\modules\responsive_sheffield_blue\product_listing.php", resulting in 32.5% (mostly). Thus deleting them in responsive_default.css will have the same effect as changing them to 32.5% in the .css.

This template has Flexible Footer Menu v1_1 built in which tries to divide the footer according to the number of columns in the footer, which IMHO seems to cause the confict. Version 1_2 and the multi-lingual version use a different way to divide the footer in columns. I did not yet try to remove v1_1 and replace by v1_2.

@Anne: Any plans to use Flexible Footer Menu v1_2 or ML in a future release? Or is there a quick fix available?

Cheers,

jpda

[jpda]

"overrule the computed setting $cols "

Sorry, this: "overrule the computed setting $cols " should be: "overrule the computed setting $col_width"

[lruskauff]

Thanks for the explanation.

[jpda]

Hi Linda,
Changing 45% to 30% (lines 387 and 413) works but it will mess up the footer layout (if left column is on).
These settings in responsive_default.css overrule the computed setting $col_width in "\includes\modules\responsive_sheffield_blue\product_listing.php", resulting in 32.5% (mostly). Thus deleting them in responsive_default.css will have the same effect as changing them to 32.5% in the .css.

This template has Flexible Footer Menu v1_1 built in which tries to divide the footer according to the number of columns in the footer, which IMHO seems to cause the confict. Version 1_2 and the multi-lingual version use a different way to divide the footer in columns. I did not yet try to remove v1_1 and replace by v1_2.

@Anne: Any plans to use Flexible Footer Menu v1_2 or ML in a future release? Or is there a quick fix available?

Cheers,

jpda

Sorry, I need to correct myself: "but it will mess up the footer layout (if left column is on)" Not true! I made a stupid typo in a stylesheet file!

@Anne: Sorry, no quick fix needed!

Cheers,

jpda