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

Thanks for pointing that out. It is incorrect in recommending just the jscript folder be carried over.

The best method for basing a template on responsive_classic is to use Clone a Template and make a clone of the responsive_classic. Then you can "adjust" to your heart's content.

There are a lot of files in other responsive_classic folders that must be present for the template just to be responsive. There are also files that are modified from template_default to add layout tags for responsive manipulation.

Case in point - in the common folder is the file main_template_vars.php. It is changed in the responsive_classic template and therefore present in the responsive_classic/common folder. The changes in the file for responsive_classic are ```
if (!isset($max_display_page_links)) $max_display_page_links = ($layoutType == 'mobile' ? MAX_DISPLAY_PAGE_LINKS_MOBILE : MAX_DISPLAY_PAGE_LINKS); if (!isset($paginateAsUL)) $paginateAsUL = $layoutType == 'mobile' || (isset($isMobile) && $isMobile) || (isset($isTablet) && $isTablet);
if (!isset($flag_disable_left)) {
$flag_disable_left = false;
}
if (!isset($flag_disable_right)) {
$flag_disable_right = false;
}

if (!class_exists('Mobile_Detect')) {
include_once(DIR_WS_CLASSES . 'Mobile_Detect.php');
}
if (!isset($detect)) $detect = new Mobile_Detect;
if (!isset($_SESSION['layoutType'])) $_SESSION['layoutType'] = 'legacy';

$display_as_mobile = ($detect->isMobile() || $detect->isTablet() || $_SESSION['layoutType'] == 'mobile' || $_SESSION['layoutType'] == 'tablet');

So, you can see, if you fail to take this file into your custom template; a major portion of the response to the environment (phone, tablet, desktop) is just not going to happen. The template will default to the template_default's file without the correct coding and not be responsive.  There are a lot more like that.

I will be working on fixing the wording of these instructions as they have not been updated in the new Zen Cart Documentation.  The wiki/faq of old is being replaced by the DOCS link you see at the top of this page.  The page to be "fixed" is <https://docs.zen-cart.com/user/template/creating_template/>

Important Links not showing on droid.

Important Links (easy pages) appear on desktop right column but do not appear on responsive android. Instead on droid it says "0" important links". HOWEVER, if I show ez pages on header as well as sidebar, then the important links will increase and appear on droid.

dbltoe:

Thanks for pointing that out. It is incorrect in recommending just the jscript folder be carried over.

The best method for basing a template on responsive_classic is to use Clone a Template and make a clone of the responsive_classic. Then you can "adjust" to your heart's content.

There are a lot of files in other responsive_classic folders that must be present for the template just to be responsive. There are also files that are modified from template_default to add layout tags for responsive manipulation.

Case in point - in the common folder is the file main_template_vars.php. It is changed in the responsive_classic template and therefore present in the responsive_classic/common folder. The changes in the file for responsive_classic are ```
if (!isset($max_display_page_links)) $max_display_page_links = ($layoutType == 'mobile' ? MAX_DISPLAY_PAGE_LINKS_MOBILE : MAX_DISPLAY_PAGE_LINKS); if (!isset($paginateAsUL)) $paginateAsUL = $layoutType == 'mobile' || (isset($isMobile) && $isMobile) || (isset($isTablet) && $isTablet);
if (!isset($flag_disable_left)) {
$flag_disable_left = false;
}
if (!isset($flag_disable_right)) {
$flag_disable_right = false;
}

if (!class_exists('Mobile_Detect')) {
include_once(DIR_WS_CLASSES . 'Mobile_Detect.php');
}
if (!isset($detect)) $detect = new Mobile_Detect;
if (!isset($_SESSION['layoutType'])) $_SESSION['layoutType'] = 'legacy';

$display_as_mobile = ($detect->isMobile() || $detect->isTablet() || $_SESSION['layoutType'] == 'mobile' || $_SESSION['layoutType'] == 'tablet');

> 
> So, you can see, if you fail to take this file into your custom template; a major portion of the response to the environment (phone, tablet, desktop) is just not going to happen. The template will default to the template_default's file without the correct coding and not be responsive.  There are a lot more like that.
> 
> I will be working on fixing the wording of these instructions as they have not been updated in the new Zen Cart Documentation.  The wiki/faq of old is being replaced by the DOCS link you see at the top of this page.  The page to be "fixed" is <https://docs.zen-cart.com/user/template/creating_template/>

Thanks

So if my custom template is a clone of, in this case, responsive_classic then the advice in the override description, see below, is no longer correct?

"Zen Cart® Upgrades

Using the override system means you don't have to worry about overwriting your custom files when an upgrade comes along, **because they are all in custom directories**."

dbltoe:

Thanks for pointing that out. It is incorrect in recommending just the jscript folder be carried over.

Please make the changes you feel are required to

https://docs.zen-cart.com/user/template/creating_template/#building-out-your-template

marton_1:

Thanks

So if my custom template is a clone of, in this case, responsive_classic then the advice in the override description, see below, is no longer correct?

"Zen Cart® Upgrades

Using the override system means you don't have to worry about overwriting your custom files when an upgrade comes along, because they are all in custom directories."
Currently, there are only three templates that would be overwritten with an upgrade. Classic, Template_Default, and Responsive_Classic. That's why we recommend to all that the first step they take in dealing with templates is to clone Responsive_Classic to their own.

Its color stylesheet is a bear to work with simply because it was taken one step to far in minimization. If you wanted to change a color in one of those dang column headers, you'd change colors all over the place. That's why we came up with the Color Change Mod. Even then, there are concerns with 1.5.7 that we are working on at the moment.

swguy:

Please make the changes you feel are required to

https://docs.zen-cart.com/user/template/creating_template/#building-out-your-templateAlready on it. But, in my head, I'm hearing Mark Twain talk about the pig.

Hello all,
I'm in the process of doing a dry run upgrade from my current store (1.5.5f) to the newer 1.5.6c version. I installed a fresh version of 1.5.6c using the webhost auto installer -- then created an empty database and imported all the data from my 1.5.5f system to that dB. I modified the 1.5.6c configure.php files to work with the new dB and used /zc_install to perform the dB upgrade. I changed to the responsive_classic template. How does the mobile menu choose the options when rendering the slide-out menu? Is there a way to choose what options are available for the mobile menu?? The development site can be seen at: tro jan boats dot net slash jingle

==================

Server Host: ns212.webmasters.com (51.81.138.96)
Database: bcushman_zen156c
Server OS: Linux 4.19.0-10-amd64
Server Date: 09/29/2020 16:28:01
Server Up Time: 16:28:01 up 47 days, 6:45, 1 user, load average: 0.28, 0.33, 0.43
HTTP Server: Apache/2.4.38 (Debian)
PHP Version: 7.3.19-1~deb10u1 (Zend: 3.3.19)
PHP File Uploads: On
Upload Max Size: 200M
PHP Memory Limit: 128M
POST Max Size: 200M
Database Engine: MySQL 5.5.5-10.3.23-MariaDB-0+deb10u1
Database Host: localhost (127.0.0.1)
Database Date: 09/29/2020 16:28:01
Database Data Size: 13,687 kB
Database Index Size: 1,705 kB
MySQL Slow Query Log Status: On
MySQL Slow Query Log File: ns212-slow.log
MySQL Mode: STRICT_TRANS_TABLES, ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER, NO_ENGINE_SUBSTITUTION

Zen Cart 1.5.6c
Database Patch Level: 1.5.6
v1.5.6c [2020-09-26 11:48:55] (Version Update 1.5.5->1.5.6c)
v1.5.5f [2018-03-13 16:44:27] (Version Update 1.5.4->1.5.5f)
v1.5.4 [2018-03-13 16:44:01] (Version Update 1.5.3->1.5.4)
v1.5.3 [2018-03-13 16:44:01] (Version Update 1.5.2->1.5.3)
v1.5.2 [2018-03-13 16:44:01] (Version Update 1.5.1->1.5.2)
v1.5.1 [2018-03-13 16:44:00] (Version Update 1.5.0->1.5.1)
v1.5.0 [2012-06-28 15:56:29] (Version Update 1.3.9->1.5.0)
v1.3.9h [2012-06-28 15:56:28] (Version Update 1.3.8->1.3.9h)
v1.3.8 [2010-01-02 16:47:08] (Fresh Installation)
v1.3.8 [2010-01-02 16:47:08] (Fresh Installation)

TrojanDon:

I installed a fresh version of 1.5.6c using the webhost auto installer
This is NOT the recommended method for doing this. First, you'll be behind on a lot of improvements in 1.5.7. Second, the "auto-installers" often have missing files. Especially those you'll need to upgrade your database.

This file controls what appears:
includes/templates/responsive_classic/templates/tpl_modules_mobile_menu.php

dbltoe:

This is NOT the recommended method for doing this. First, you'll be behind on a lot of improvements in 1.5.7. Second, the "auto-installers" often have missing files. Especially those you'll need to upgrade your database.

True that 1.5.7 is the latest, but some plugins (even heavily used ones like COWOA, Dual pricing, etc.) have not yet been upgraded to 1.5.7.

marton_1:

Thanks

So if my custom template is a clone of, in this case, responsive_classic then the advice in the override description, see below, is no longer correct?

"Zen Cart® Upgrades

Using the override system means you don't have to worry about overwriting your custom files when an upgrade comes along, because they are all in custom directories."

This is partially correct. Your customizations won't get overwritten, but as Zen-Cart upgrades your custom template might break due to changes in some of the default Zen-Cart functionality and/or changes in code that can be used for the upgraded versions of PHP,etc.

ZC 157b Mobile issues - Full version is fine, but finding the following in the mobile

1. I use the blank_sidebox mod in the left column on the full size version of our site. On the mobile, it appears at the top, just below the header along with the links in it. It doesn't belong there.

2. Pressing the Hamburger icon the menu appears (of course) and there are a few things undesirable or incorrect:
   A. It's nice to have a count of the number of categories, subcategories and sub-sub categories, but not so nice not to have a count of the products in those categories, if for no other reason, to see that there are products in the category. It seems a numerical indication just of the categories isn't informative from a customers perspective, however if the last stage of sub categories indicted how many products were there the customer would know there are products and can select the category to view them. As it is, a customer needs to select the sub-sub category to find out if there's anything in it.

   B. The Information sidebox is disable on our site and I have moved the links to the footer section. However, on the mobile the Information sidebox shows up, with the links not in the order in which they are organized should I enable the sidebox on the full page.

   C. Also in the Information sidebox displayed on mobile, the Page 2, Page 3 and Page 4 links appear at the bottom of the box when they shouldn't - they're just blank, native pages as came in the package.

   D. I use the Important Links sidebox on the right hand side of the full version and it has content links in it. On the mobile version, The Important Links sidebox appears at the bottom of the menu and there's no links in it.

   I may be updating this post as the issues get ironed out for others that may arise.
   https://www.thercrv.com

2.A - The categories_ul_generator doesn't build counts of products, so that number isn't available to the menu.
2. B,C,D - See /includes/templates/YOUR_VERSION_OF_responsive_classic/templates/tpl_modules_mobile_menu.php

DrByte:

2.A - The categories_ul_generator doesn't build counts of products, so that number isn't available to the menu.
2. B,C,D - See /includes/templates/YOUR_VERSION_OF_responsive_classic/templates/tpl_modules_mobile_menu.php

Cool! Took care of B and C easy enough.

As for a, is there a way to just turn the numbers off? They have no real value or use except for the admin to have a quick look at how many categories there are so he/she can say "I have x amount of categories and .....well, I don't know how many products there are... But I have x amount of categories". Customers don't care about that, their interest, if any at all, would be more toward how many products there are and since that seems to be difficult to achieve they might as well just be taken off.

I still have an important tasks of getting that blank_sidebox (mine is the Rants and Raves if you look at it) off of the page and into the menu
and
Figuring out how to get the links to show up in the "Important Links" of the menu, can't seem to decipher how the (what I assume is) $var_linkslist works to do that. I guess my PHP for Dummy's reference books didn't count on such a dummy coming upon something like that.

Well, maybe for d there's a clue

echo '<li><a href="' . $var_linksList[$i]['link'] . '">' . $var_linksList[$i]['name'] . '</a></li>' . "\n"
Might I be off track in thinking perhaps I replace the ['link'] with whatever the link and ['name'] with that in the full version, then duplicate this for every link in it? Hummmmmm

DrByte:

2.A - The categories_ul_generator doesn't build counts of products, so that number isn't available to the menu.
2. B,C,D - See /includes/templates/YOUR_VERSION_OF_responsive_classic/templates/tpl_modules_mobile_menu.php

It looks like I'm also off on an adventure to dissect the includes/classes/categories_ul_generator.php to figure out how to remove the numbers.

TheGrimReaper:

It looks like I'm also off on an adventure to dissect the includes/classes/categories_ul_generator.php to figure out how to remove the numbers.
Change Configuration :: My Store :: Show Category Counts to false.

Yes ma'am, but again what works for the full version, which is awesome, doesn't work for the alleged "responsive" mobile, which is not very friendly, not well supported and doesn't care what happens on the full version.

Just a side note: I don't use the Information box on the desktop, thus the problem doesn't show up. The mobile version forces it in there.

Well, DrByte...I got the email with your question, but see it isn't here anymore and yes...when lat9 pointed me that direction I turned it off but the mobile didn't respond in kind.

We're trying to get the mobile version of a very good template to behave because I'm a stubborn old man that doesn't give up easily and I'm not willing to give up on it...yet.

Now the doc(umentation) just put a new twist on the numbers thingy -"Key: SHOW_COUNTS
Path: Configuration > My Store
Description: Count recursively how many products are in each category, when I thought you said it doesn't count products. What'd I miss?