45
« on: October 06, 2017, 02:38:42 AM »
Hi, this is the 2nd response I have ever received from you.
In the 1st one, you helped me modify the block_templates table to permit placement of the "menu" block into header_bottom section. That modification became the foundation for my particular style of AbanteCart. It ultimately resulted in a clean approach to responsive navbar and an alternative consideration of categories. It was very helpful in building my streamlined approach to ecommerce, where the homepage is shopping.
I'm continuing to modify AC to remove extraneous pages from the checkout sequence. Less clicks, less pages, less everything.
So thanks for your 2nd response.
It didn't help.
In Developer Tools, I have one project. It is my template extension. It is a clone of default.
If I open that project (my template), I can see 4 buttons to do stuff, but none of them relate to layouts. There is no method for adding a layout.
In Developer Tools, I can start a new project. There are 7 available types of new projects, but none are "layouts".
Furthermore, I do not recognize the wisdom of creating a new extension for a layout for a different extension. I don't recognize the architectural relationship capability of that suggestion. Do I really need a layout extension to add a layout to a different extension? If so, how is it done?
Bottom line - I don't see how Developer Tools is used to create a new layout. I looked. I read. I opened everything. I don't see it.
So I looked at the underlying "values" of your proposal, and I compared them to Maxter's instructions.
By following Maxter, I inserted a new layout in the layouts table.
And I inserted a new layout-to-page relationship in the pages_layouts table.
And I inserted a new page in the pages table, but it isn't really a new page, it's just a more granular or precise specification of an existing page.
Then I inserted all of the new layout elements into the layout.xml file for the template extension. I gave the proper name, controller, and name-CDATA values to this new section of layout.xml. It's just a copy of the Checkout Pages section, but with changed name and controller values.
I looked at install.php for my extension. The code you referenced above is already in that file.
I cleared cache for Configuration and Layouts & Blocks.
The new layout appeared in my menu of layouts for my extension, but the new layout did not change the target page, and furthermore, the new layout was empty.
I think that I accomplished all the "values" mentioned in your response, but I did it by following Maxter's instructions, and I couldn't find anything in Developer Tools to improve or augment those "values" or the outcome.
So I have 2 probs:
1 - my new layout exists, but it is empty.
2 - my page ignored the new layout.
I think it best to solve them in order.
Big picture: there are a lot of checkout pages in AC. A lot.
Some of them are redundant.
Too many clicks, just to finish. Amazon created 1-click checkout for a reason. People wanna be done.
My goal is to shrink the checkout process to bare essentials. Faster. Less clicks.
My success depends on my ability to use different layouts for different checkout pages.
Maybe my needs are less important than the global need. Maybe having all checkout pages based on the same single layout is sub-optimal. Maybe all AC users could benefit from having access to a choice of more than 1 layout for all the checkout pages.
Thanks.