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

[lat9]

Kind of, sort of ... not exactly.

Seriously, I've got the template portions broken out so that I could pre-stage the template in some older Zen Cart installations, but haven't really been keeping up. I'll get a GitHub repository started (using 1.5.5e-3 as the change-basis), then with the community's help on identifying the changes we can get this template up-to-date.

OK, I've got the responsive_classic files (and support functions) pulled out from the Zen Cart 1.5.5e distribution and available on GitHub here: https://github.com/lat9/zen_responsive_classic

I haven't been keeping a change-list for the plugin's files thus far, so any changes needed will need to be (re-)identified, either here in the support thread or via a GitHub issue on the template's repository.

[shags38]

OK, I've got the responsive_classic files (and support functions) pulled out from the Zen Cart 1.5.5e distribution and available on GitHub here: https://github.com/lat9/zen_responsive_classic

I haven't been keeping a change-list for the plugin's files thus far, so any changes needed will need to be (re-)identified, either here in the support thread or via a GitHub issue on the template's repository.

Thanks for that lat9 - much appreciated.

cheers, Mike

[shags38]

OK, I've got the responsive_classic files (and support functions) pulled out from the Zen Cart 1.5.5e distribution and available on GitHub here: https://github.com/lat9/zen_responsive_classic

I haven't been keeping a change-list for the plugin's files thus far, so any changes needed will need to be (re-)identified, either here in the support thread or via a GitHub issue on the template's repository.

So Cindy - dumb question - I have held off upgrading my sites (from 1.5.1) due to lack of confidence in template(s) performance/suitability - now with your post above I am now going to give the upgrading a shot - so after upgrading do I then upload your includes files into /includes folder and overwrite as necessary?

thanks for your help.
cheers, Mike

[lat9]

So Cindy - dumb question - I have held off upgrading my sites (from 1.5.1) due to lack of confidence in template(s) performance/suitability - now with your post above I am now going to give the upgrading a shot - so after upgrading do I then upload your includes files into /includes folder and overwrite as necessary?

thanks for your help.
cheers, Mike

Mike, not a dumb question. The GitHub repository represents the files (and associated file-structure) for this template, as shipped within the Zen Cart 1.5.5 distributions and can be used in a couple of ways:

1. You're running ZC 1.5.4 (I wouldn't suggest installing the template on an earlier ZC version) and want to "kick the tires" before upgrading.
2. You're running a variant of ZC 1.5.5 and want to capture all the currently-known changes to the template.

In either case, you'd just "drop" the template changes in (there's a .SQL install script for the pre-1.5.5 installations) and then either clone that template or merge the template's current changes into your customized version.

Please note that at this point in time, the GitHub repository represents the v1.5.5e version of the template files.

[shags38]

Mike, not a dumb question. The GitHub repository represents the files (and associated file-structure) for this template, as shipped within the Zen Cart 1.5.5 distributions and can be used in a couple of ways:

1. You're running ZC 1.5.4 (I wouldn't suggest installing the template on an earlier ZC version) and want to "kick the tires" before upgrading.
2. You're running a variant of ZC 1.5.5 and want to capture all the currently-known changes to the template.

In either case, you'd just "drop" the template changes in (there's a .SQL install script for the pre-1.5.5 installations) and then either clone that template or merge the template's current changes into your customized version.

Please note that at this point in time, the GitHub repository represents the v1.5.5e version of the template files.

Hello Cindy - many thanks for your detailed response, I appreciate it. I'm not a developer so sometimes I struggle with terminologies/processes etc - had no idea what GitHub or a repository was about prior to your explanation - in layman's terms I assume what you have created is in essence a 'plug in' version of the template?

Again many thanks,
cheers, Mike

[lat9]

Hello Cindy - many thanks for your detailed response, I appreciate it. I'm not a developer so sometimes I struggle with terminologies/processes etc - had no idea what GitHub or a repository was about prior to your explanation - in layman's terms I assume what you have created is in essence a 'plug in' version of the template?

Again many thanks,
cheers, Mike

Mike, your assumption is correct.

[idtags]

Classic look Attachment 17051 Responsive template Attachment 17052

Hello, I just discovered responsive template and tried it.
It looks good and is passing Google mobile requirements.
I used before custom version of Classic template and it took me years to tweak to the look shown on first attachment.
Second Image shows current "out of box" look.
Is there anywhere description of Step by Step customization?
Where to start to customize Responsive template?
Is it actually customize able, like classic with custom folder for each section?
Can be anything done on admin Panel?

Any link pointing to begining of the process will be greatly appreciated.

Than you.

[dbltoe]

No particular laid out steps. It is a golden opportunity to learn using web developer extensions for your browser to experiment with your stylesheet(s).
A couple of things I would do first before diving in. Get the mod that better facilitates color changes for responsive_classic and install it. https://www.zen-cart.com/downloads.php?do=file&id=2088.
After it's installed and before you make any other changes, use the clone template mod to clone it to a new name for your store. Try to pick a clone name without the underscore. https://www.zen-cart.com/downloads.php?do=file&id=2087
Now, any changes to the new template can easily be found/removed/repaired using the old template and its clone.

For those of you wondering about underscores in URLs, Google, WooRank, and StackOverFlow all suggest dashes versus underscores.

[DrByte]

use the clone template mod to clone it to a new name for your store. Try to pick a clone name without the underscore.

For those of you wondering about underscores in URLs, Google, WooRank, and StackOverFlow all suggest dashes versus underscores.

Um ... the name of the template directory never appears in the URL for SEO purposes. So using an underscore in the name of your template folder is unrelated to SEO.

[dbltoe]

My original thought as well. Still woorank and a few others are commenting on not only the "main_page" but items in the page source as well. Every day is another humbling experience.

Reasoning seems to be that links are confusing when underlined.