Shipping Estimator not working in responsive_classic

It works in classic but not in responsive_classic

Please explain what "not working" means... what is presented? What is missing? What are settings that can reproduce the issue? Right now an issue is expected to occur if responsive_classic is chosen as the template, but fresh install? Anything added/modified? Etc...

mc12345678:

Please explain what "not working" means... what is presented? What is missing? What are settings that can reproduce the issue? Right now an issue is expected to occur if responsive_classic is chosen as the template, but fresh install? Anything added/modified? Etc...

Fresh Install; When you click on Shipping Estimator in responsive classic it does nothing at all. It works in classic though.

tmccaff:

Fresh Install; When you click on Shipping Estimator in responsive classic it does nothing at all. It works in classic though.
Is this a sidebox option to which you are referring?

What product was attempted to be in the cart?

What sequence was used to generate the issue? Was the template first set to responsive, it failed the first time, then immediately changed to classic and worked, what shipping module(s) are active/installed?

I changed it now to classic and it works. Default shipping methods fresh install. When you add to cart and click on shipping estimator it does nothing in responsive_classic. Tried both on Edge and Chrome. In Classic it works

Maybe this will help; here is my link to my store add product and click on Shipping Estimate nothing happens. I noticed though its not in https but http.

https://giftboundgifts.com/index.php?main_page=products_all

Shopping cart Page fails html validation with several errors. Use of the popup button would require the page to validate so that the javascript could execute properly. The first error occurs at the logo where the dimensions are identified as say 192px instead of 192 px, but there likely is something more involved. Would almost suggest comparing the html output from 1.5.6 to 1.5.5 to see if/where the differences might be. Likely a file updated in one wasn't updated in the other...

Ok what files should I be looking at?

tmccaff:

Ok what files should I be looking at?

Well would also go back to the linked page... The button to add product to the cart didn't work either and that page fails validation.

Currently would suggest looking for:

br class="banner-padding>

and trying to fix that by adding an additional double-quote (") at the end of banner-padding. My desktop computer was able to figure out what was going on, but my mobile device wouldn't let me add a product to the cart from this area. Not sure if it relates more to the below or to the above.

It would also help if the site were properly setup to support all https:

Right now, the customer lands on a page that is https:, but all the links in the site are basically set to go to an http: location which nearly completely defeats the purpose of being on a page that is https: to begin with. From my desktop when I attempt to add a product to the cart from the All products page, I am advised that my information will be transmitted insecurely and if I wish to proceed.

It looks like (before your site went or was taken down) that you are/were missing the following file: includes/templates/responsive_classic/jscript/popupWindows.js

There was a javascript error of the function popupWindow not being defined. It is, however, defined in that file.

Comes down to what appears to be differences in includes/templates/responsive_classic/common/html_header.php and the same file for the template_default directory.

There is a move afoot to make the loading/identification of common css and javascript more "centralized" rather than being controlled so independently in each template. As a result, code that was say in includes/modules/pages/shopping_cart has been moved to the jscript directory for the template and the above file is intended to load the necessary jscript/jquery as well as css to support the template. Well, the ZC 1.5.6 version of the responsive_classic template was just moved over on the 12th of January and though some changes have been applied, not all things that would be expected to bring it up to speed with the development that has been ongoing with the default template.

In other words, while this issue for example is a result of that merge, it is only but one "symptom" of the current status/condition. Almost any javascript related operation is likely to be affected until the files are loaded and/or made available for use preferably without cluttering the work that has been done to try to streamline this process by moving so much out of the template files and into module files.

Thanks. I guess I will go back to 1.5.5f till I figure this out. Once 1.6 is release I will upgrade. Thanks