Responsive Classic Redesign Support thread

[nicksab]

Here is where I am at:

fresh ZC 2.1 install with clean database loaded with sample products.

Installed the template

Everything looks good until I change this setting:

Configuration > Product Listing > Columns per row > 3

As soon as i do this, the layout is back to really small pictures and columns

sample can be seen here : https://www.royal-fleur.com/belveder...dex&cPath=3_10

Not sure what s causing this at this point. I do want my product to be displayed in columns vs row

[royaldave]

Here is where I am at:

fresh ZC 2.1 install with clean database loaded with sample products.

Installed the template

Everything looks good until I change this setting:

Configuration > Product Listing > Columns per row > 3

As soon as i do this, the layout is back to really small pictures and columns

sample can be seen here : https://www.royal-fleur.com/belveder...dex&cPath=3_10

Not sure what s causing this at this point. I do want my product to be displayed in columns vs row

In Admin -> Images, what do you have in

Image - Product Listing Width
and
Image - Product Listing Height

If not already, try making Width blank and Height say 250 and see what happens?

[nicksab]

It is set to the default:

Image - Product Listing Width > 100

Image - Product Listing Height > 80

I tried your suggestion but no changes.

It is not only the product image. It also affect the description, title....it is like a column within a column

[chadlly2003]

Are you taking old pieces of code and pasting them into the new template. There are some difference I noticed in the code.

Anyway if you look at your source code you have a width of 32.5%. (see image) That is what causing your issue. (in the template this is not showing. Which means it was a change you made.)


There are only few places I found that would causing a percentage width. I would start by replacing the following files

Just download the template again and replace this file. Lets see what this does.

includes\modules\responsive_classic\product_listing.php
includes\templates\responsive_classic\common\tpl_columnar_display.php

If you still cant get it pm and we could dig a little deeper. This should be very simple to solve.

[chadlly2003]

Here is where I am at:

fresh ZC 2.1 install with clean database loaded with sample products.

Installed the template

Everything looks good until I change this setting:

Configuration > Product Listing > Columns per row > 3

As soon as i do this, the layout is back to really small pictures and columns

sample can be seen here : https://www.royal-fleur.com/belveder...dex&cPath=3_10

Not sure what s causing this at this point. I do want my product to be displayed in columns vs row

I was able to replicate your issue.

Go to your admin
Admin / Configure / Product Listing

Columns Per Row (change it to 1)

Use CSS to make your columns

Path: stylesheet_zcustom.css

@media (min-width: 768px) {
  .tabTable {
    text-align: left;

}

change to

@media (min-width: 768px) {
  .tabTable {
    text-align: left;
    display: grid;
    gap:1rem
    grid-template-columns:1fr 1fr;    <!-- Use 1fr to add a column -->

}

[chadlly2003]

If you want to use the backend instead of changing the css you can just go to

Go to your admin
Admin / Configure / Product Listing

Columns Per Row (change it to 2)



/includes/modules/responsive_classic/product_listing.php

find this line 402

$style = ' style="width:' . $col_width . '%;"';

replace with

$style = ' style="width:' . $col_width . '"';

and to enlarge image just go the the stylesheet_zcustom.css

line 2684

find

@media (min-width: 768px) {
  .list-image img {
    float: left;
    margin-bottom: 0px;
    width: 80px;
  }

and change the width to your desired size

[dbltoe]

<personalOpinion>

I fear this project is going to be a continuing problem child. Based solely on what I am seeing so far, here are my concerns.

Standard configuration settings seem to have been replaced by hard-coding settings of initial core files.

Suggestions to set the standard configuration to one setting and modify the setting in CSS (even if it is the override) are going to result in more than the normal confusion with the new user. For the originator, many hours will be spent assisting with things that should be done in the basic configurations.

There are few in this forum who better understand the amount of work that's been put into this project than I. The documents, plugins, and forum assistance are light years ahead of the days after the break from osCommerce.

Unfortunately, my original enthusiasm for this redesign has dimmed with each indication that changes will require more than just a simple override.

I remember my early days of Zen Cart and the mindset at the time of "just do this in this file" rather than take the time to learn where the basic configuration was set. The first few upgrades were H E double hockey sticks.

Like others, I tried a commercial template or two only to find that the creators could often care less about their product breaking when a standard ZC config was changed. Also, I find myself still finding a config setting I hadn't used before or missed in my search.

lat9's Zen Cart Overrides Cheatsheet was an eye-opener for many of us and the first real step to my maintenance methods today. Even with that invaluable information, I found I still had to be careful not to "step on the toes" of the basic config.

Unfortunately, it appears that this project may be going a step beyond a simple override to change the location of items on a page to bypassing settings installed in the basic database settings.

From the original 1.2.x and PHP 4.4, to the soon to be released 2.2.0 and PHP 8.4, the focus has been on creating a quality product complete with great features that would be easily operated out of the box. January will be 22 years that I have used and supported ZC. I'm proud to have contibuted in what way I could and try my best to not screw up when giving insight/advice.

I would love to put my personal seal of approval on this redesign. And, if I were not concerned with the possible confusion and unusual need to result to file or stylesheet overrides, I certainly would. I've long felt that the old template_default needed a replacement.

Unfortunately, I keep hearing "one step forward and two steps back" playing in my mind. I fear a well-minded effort may become more of an effort to maintain.

I wish it weren't so and hope we can get back to a point that avoids excessive overrides and core file edits.

</personalOpinion>

[nicksab]

If you want to use the backend instead of changing the css you can just go to

Go to your admin
Admin / Configure / Product Listing

Columns Per Row (change it to 2)



/includes/modules/responsive_classic/product_listing.php

find this line 402

$style = ' style="width:' . $col_width . '%;"';

replace with

$style = ' style="width:' . $col_width . '"';

and to enlarge image just go the the stylesheet_zcustom.css

line 2684

find

@media (min-width: 768px) {
  .list-image img {
    float: left;
    margin-bottom: 0px;
    width: 80px;
  }

and change the width to your desired size

Thank you chadly.

I thought it was my own doing by messing up the template files but as mentioned, I had the same issue with a clean copy of all files.

I really appreciate your help by providing a fix.

I will give it a try and report back if needed.

[chadlly2003]

<personalOpinion>

I fear this project is going to be a continuing problem child. Based solely on what I am seeing so far, here are my concerns.

Standard configuration settings seem to have been replaced by hard-coding settings of initial core files.

Suggestions to set the standard configuration to one setting and modify the setting in CSS (even if it is the override) are going to result in more than the normal confusion with the new user. For the originator, many hours will be spent assisting with things that should be done in the basic configurations.

There are few in this forum who better understand the amount of work that's been put into this project than I. The documents, plugins, and forum assistance are light years ahead of the days after the break from osCommerce.

Unfortunately, my original enthusiasm for this redesign has dimmed with each indication that changes will require more than just a simple override.

I remember my early days of Zen Cart and the mindset at the time of "just do this in this file" rather than take the time to learn where the basic configuration was set. The first few upgrades were H E double hockey sticks.

Like others, I tried a commercial template or two only to find that the creators could often care less about their product breaking when a standard ZC config was changed. Also, I find myself still finding a config setting I hadn't used before or missed in my search.

lat9's Zen Cart Overrides Cheatsheet was an eye-opener for many of us and the first real step to my maintenance methods today. Even with that invaluable information, I found I still had to be careful not to "step on the toes" of the basic config.

Unfortunately, it appears that this project may be going a step beyond a simple override to change the location of items on a page to bypassing settings installed in the basic database settings.

From the original 1.2.x and PHP 4.4, to the soon to be released 2.2.0 and PHP 8.4, the focus has been on creating a quality product complete with great features that would be easily operated out of the box. January will be 22 years that I have used and supported ZC. I'm proud to have contibuted in what way I could and try my best to not screw up when giving insight/advice.

I would love to put my personal seal of approval on this redesign. And, if I were not concerned with the possible confusion and unusual need to result to file or stylesheet overrides, I certainly would. I've long felt that the old template_default needed a replacement.

Unfortunately, I keep hearing "one step forward and two steps back" playing in my mind. I fear a well-minded effort may become more of an effort to maintain.

I wish it weren't so and hope we can get back to a point that avoids excessive overrides and core file edits.

</personalOpinion>

This is version 1, and my main goal right now is to gather feedback and identify any issues that come up. Since this is a brand-new template, some rough edges are to be expected.

I've taken note of your feedback and will work on an updated version. The changes should be quick—just a few minor CSS adjustments. Since the core framework is already in place, adapting the site to support backend features should be relatively straightforward. Most of it already complete.

I think the most challenging part is getting the responsive elements to behave consistently. In my experience, most templates require some CSS or HTML tweaks to achieve the exact look you're after, and this one is no different.

[carlwhat]

This is version 1, and my main goal right now is to gather feedback and identify any issues that come up. Since this is a brand-new template, some rough edges are to be expected.

I've taken note of your feedback and will work on an updated version. The changes should be quick—just a few minor CSS adjustments. Since the core framework is already in place, adapting the site to support backend features should be relatively straightforward. Most of it already complete.

I think the most challenging part is getting the responsive elements to behave consistently. In my experience, most templates require some CSS or HTML tweaks to achieve the exact look you're after, and this one is no different.

IMO, @chadlly2003, i applaud your work here and encourage you to continue on with it.

unfortunately there are too few people working to support this project, and those that do should be encouraged as opposed to criticized.

having another supported template is AWESOME.

my only critique would be that in true silicon valley style, there is never a version 1; start with version 2!

best.