hairydog

Let's see if I can make it work first! I'm wondering if I have simply misunderstood how Options work. Is there a document that describes it in more detail than the Help does?

When comparing the page sizes, I've noticeded that the Options don't work on the Foundation skin either - so maybe the skin isn't to blame after all. I'll try the {debug] idea and see what is happening. I can't see that the time to first byte can be very high if my template on the same page on the same server has finished rendering in 0.7 seconds. The page is 800KB. That's why it takes 4.6 seconds to render: something I want to fix. Last time I tried this, a year or two back, I gave up. But I thought I'd try again. If I ever get a skinny skin working, I could make a generic version to share.

For a start, I want to avoid "responsive" code. It is easy to achieve a design that is good on desktop, tablet and mobile just with a few lines of CSS. I don't want to have to call javascript libraries to render a page. I want as few queries as possible. I want the code to be clean, small and elegant. To give an idea of the difference I'm looking at, with my current test site, the Test Product page with the untouched Foundation skin, is 814.05kB and takes 4.645 seconds to load in Firefox with caches disabled. The same page, using my version of a v5 skin (which is not finished yet), is 32.05kB and loads in 753 miliseconds.

I'm making a second attempt at getting the page weight down. I appreciate that the developers of CC don't think this matters as much as I do. What I want to do is use a lightweight version of a CC5 skin with an up-to-date CC6 setup. Mostly, this seems to work, but far from completely. Product options are the current stumbling block. I found a reference to updating script.js at about line 430, but the script.js I found has only 40 lines of code. Is there anywhere that I can find a list of what is needed in a CC5 skin running on CC6? If so, where is it?

I decided to go slightly further. Added - as a zone then updated the templates to say something like this. <input type="hidden" name="billing[state]" id="state-list" value="-" /> Seems to work.

The Pricing tab of the Product Admin page has a "Tax Included" checkbox, which seems to determine whether the price entered is inc or exc of tax. That seems OK, but if it had two more checkboxes, one "Show prices including tax" and the other "Show prices without tax" that would make the system a lot more flexible. You chould choose between showing no price for a product, the tax-exc price, the tax-inc price, or both exc and inc prices.