Messages

Resize your logo image to the size of image you want to see.  Name it logo-sm.png, or whatever, then go to the PP_Express extension, remove the existing logo image, then add the new small image. 

For experts and Devs, it must be a cakewalk...

Why must it?

There is no cookie-cutter solution for what you ask.  There is no Admin button that accomplishes what you seek.  This is custom work.

You will have to change the code in a few files. 

So you will either have to learn which files require changes, and then learn which code to change, or you will have to pay a contractor to do it for you. 

If you feel like learning, go to https://github.com/abantecart/abantecart-src/tree/master/public_html, and enter "easy zoom" in the search box at the top of the page.  This will provide a starting point for disabling easy zoom in AC files. 

If you feel like hiring a contractor, look on freelancer or use the PPS option here:   http://www.abantecart.com/contact-us

Hi, I have seen your posts on this topic. 

I'm no expert, but I think it is possible that you underestimate the complexity of this mod.   

Assuming that your customization work is being performed on a template extension, the following file will allow you to change the order of elements on the GS1 page:
/extensions/templatename/storefront/view/templatename/pages/checkout/guest_step_1.tpl. 

In that file, you will find blocks of code that relate to shipping address and billing address.  If you copy and paste the shipping block above the billing block, that would be the 1st step in reaching your goal. 

But then things get tricky. 

You will have to determine where and how the radio button function works in that file, and whether another file is also involved, and if so, how to carry your change through both files. 

Then you will have to consider the role of the related controller file:
/storefront/controller/pages/checkout/guest_step_1.php. 

The controller file will also have blocks of code that perform GS1 functions, and any change to the tpl file will likely require a corresponding change in the php file.

And vice versa.

Lastly, there is the matter of credit card checkout success. 

My AC site uses the Stripe extension.  A successful checkout requires that the customer enter a card number, exp date, and code, but not a billing address.  Card verification typically includes address and zip, so AC is apparently delivering the previously entered billing address data autonomously. 

Your mod will require that you ensure no interruptions to that process. 

Typically, ecommerce transactions are structured on the assumption that goods are shipped to billing address of the buyer.  The exception occurs when a buyer specifies that the goods be shipped elsewhere.  In the credit card processing industry, this exception is always a flag.  That's just how it works.

IMO - you may be overestimating the value of switching the structure of GS1, and underestimating the complexity of doing so.

Anyone?

[/storefront/controller/pages/checkout/guest_step_3.php]

This is what I tried:

/storefront/controller/pages/checkout/guest_step_3.php

On line 76, insert this:

Code Select Expand

if ($this->request->is_POST()){
                    $this->session->data['comment'] = $this->request->post['comment'];
                    $this->extensions->hk_ProcessData($this);
        }

On line 165, insert this:

Code Select Expand

$form = new AForm();
$form->setForm(array ('form_name' => 'guest'));
$this->data['form']['form_open'] = $form->getFieldHtml(
array (
    'type'   => 'form',
                    'name'   => 'guest',
                    'action' => $action,
                    'csrf' => true
                )
        );

$this->data['form']['comment'] = $form->getFieldHtml(
array (
'type'  => 'textarea',
'name'  => 'comment',
'value' => $this->data['comment'],
'attr'  => ' rows="3" style="width: 99%" '));

/storefront/controller/pages/checkout/guest_step_2

Remove (comment out) line 114 and lines 411-417. 

////mytemplate/pages/checkout/confirm.tpl

On line 70, insert this:

Code Select Expand

<div class="ted"><h4 class="heading4"><?php echo $text_comment_dave; ?></h4></div>

<div class="registerbox">
<div class="content">
<?php echo $form['comment']; ?>
</div>
</div>

////mytemplate/pages/checkout/guest_step_2.tpl

Remove (comment out) the heading, registerbox, and form-comment from guest_step_2.

Outcome:

The Order Comments box is now located on GS3-Confirm page, but it doesn't work. 
The customer comments are not transmitted to AC system.  They cannot be viewed anywhere, they don't exist.

Can you help? 

Thanks.

This error disappeared while i was working on other parts of the site.  I sort of forgot about it. 

Follow-up - my other site work required clearing cache.  The error disappeared.  Maybe cache was the solution.  Thx.

Hi, thanks.  That's what I thought. 

My question was: why is the </form> tag missing in storefront/view/default/template/pages/checkout/confirm.tpl ?

See line 37. 

I just submitted my first ever 'Issue' on github.  :-)

Am i officially a coder now?  Is there a club or anything?  Do I get a t-shirt?

1.2.11

storefront/view/default/template/pages/checkout/guest_step_2.tpl          line 149 = </form>

Is this a closing tag?  What does it close?  Does it close line 28?



Look at storefront/view/default/template/pages/checkout/confirm.tpl.

There is no </form> tag.

Should there be a </form> tag in this file?

Just asking.  You know I'm not a coder. 

Thx.

IMO - there are too many clicks and too many pages in the checkout sequence. 

Amazon's concept of "One Click Checkout" is now an old concept.  They made it for a reason.  Customers want to be done. 

This is what my customers see:
Cart - GS1 - GS2 - GS3 - Success.   
Cart - paypal - GS2 - GS3 - Success. 

GS2 is redundant.  Move Comments to GS3.  Payment selection has already been made, it does not need to be made again.  Eliminate GS2. 

I'm not saying that AC needs 1-click checkout, but I think it can be faster and cleaner. 

I think it would be easy to eliminate GS2. 

Hey, I got it!

To add a new custom layout for a checkout page, use phpMyAdmin to edit four tables in your database:

1 - add the new layout to the _layouts table.

2 - add a new page to the _pages table.  This won't be an actual new page, but rather a more granular specification of an existing page.  In default AC, all checkout pages except the Cart page share the same layout.  In the _pages table, you will see 2 rows for checkouts pages:
a - pages/checkout
b - pages/checkout/cart
The system applies the Checkout Pages layout to all checkout pages except the Cart page, because the cart page is defined more precisely to use the pages/checkout/cart layout. 
Your goal in step 2 is to add a a 3rd row, a more specifically-defined page.  So you pick a new page_id number and use a more specific controller name.  In my case, it was pages/checkout/guest-step-1.

3 - edit the _pages_layouts table to add a new association between the new page with the new layout. 

4 - edit the _block_layouts table.  What this table does is associate various blocks with a layout.  Sort the table by layout_id.  You will then multiple rows for each layout, each row associating a block with that layout.  You made a new layout, but it will be empty until you associate various blocks.  The easiest way to do this is to pick another known layout in that table, click every box in every row of the layout, then scroll to page bottom and click Copy.  This will open a new view where you are editing every block assignment for the known layout.  Change every layout_id value from the value for the known layout to the value for your new layout, then click Go button to save.  Basically, this will clone the known layout into your new layout. 

Close phpMyAdmin.

Open your template layout.xml file in an editor.  Find the section of code for the Checkout Pages layout.  Copy everything from the <layout> tag thru the </layout> tag.  Paste that content at the bottom of the file.  Then edit the 2 <name> values you will see at the top of the pasted section.  Change them from "Checkout Pages" to whatever name you used for layout_name in the _layouts table.  Also edit the <controller> line to match the controller value you specified in the _pages table.  Save and close. 

Clear cache.

That's it.  You will now see your new Layout in Admin, and you can set it however you like. 

Thanks to Maxter and AC for bringing me far enough along so that I could recognize the missing piece: the _block_layouts table.

Hi, thanks again for your help. 

I made the change you suggested to install.php, and then cleared all cache, but it did not work. 

My new Layout "GS1 Layout" appears in the Layouts dropdown menu for both the default and joe templates, but it is empty regardless of template selected.  (It has a "Content Area", but no other blocks or sections.)

Food for thought:  I am using a template extension.  It was a clone of default.  I used Admin to modify all of the available layouts for my extension. 
Before today, I have never edited the install.php file in my extension folder root.
Until today, the ALayoutManager value was always 'default'. 
My site works.  My layout modifications work.  My template extension works. 
Everything works despite the difference between template_id value 'joe' in layout.xml and the ALayoutManager value 'default' in install.php. 

Changing the ALayoutmanager value from 'default' to 'joe' did not affect any part of my site, and it did not populate the new GS1 Layout with the fields or blocks specified in the layout.xml file. 

So I'm still trying to solve the 1st problem.  I can edit the tables to create a new layout, and I can specify the components of the new layout in layout.xml, but when I open the new layout in Admin, it is empty. 

Thanks for helping me solve this. 

The log has a few miscellaneous warnings, but nothing related to layout.xml or anything else related to layouts.

Yes, cache cleared. 

Admin page debug is identical for Checkout Pages layout vs new GS1 Layout. 

Thanks for help. 

If a new layout is inserted into layouts table, and defined in layout.xml, and visible in admin dropdown menu of layouts, why is the layout empty? 

Here is the layout.xml snippet:

Code Select Expand


    <layout>
    <name>GS1 Layout</name>
    <template_id>joe</template_id>
    <type>Active</type>
    <pages>
      <page>
        <controller>pages/checkout/guest_step_1</controller>
        <page_descriptions>
          <page_description>
            <language>english</language>
            <name><![CDATA[GS1 Layout]]></name>
          </page_description>
        </page_descriptions>
      </page>
    </pages>
    <blocks>
      <block>
        <block_txt_id>header</block_txt_id>
        <status>1</status>
        <position>10</position>
        <block>
          <block_txt_id>customer</block_txt_id>
          <status>1</status>
          <position>20</position>
        </block>
        <block>
          <block_txt_id>menu</block_txt_id>
          <status>1</status>
          <position>30</position>
        </block>
        <block>
          <block_txt_id>search</block_txt_id>
          <status>1</status>
          <position>40</position>
        </block>
        <block>
          <block_txt_id>language</block_txt_id>
          <status>1</status>
          <position>50</position>
        </block>
        <block>
          <block_txt_id>currency</block_txt_id>
          <status>1</status>
          <position>60</position>
        </block>
        <block>
          <block_txt_id>cart</block_txt_id>
          <status>1</status>
          <position>70</position>
        </block>
      </block>
      <block>
        <block_txt_id>header_bottom</block_txt_id>
        <status>1</status>
        <position>20</position>
        <block>
          <block_txt_id>category</block_txt_id>
          <status>1</status>
          <position>10</position>
        </block>
        <block>
          <block_txt_id>breadcrumbs</block_txt_id>
          <status>1</status>
          <position>20</position>
        </block>
      </block>
      <block>
        <block_txt_id>column_left</block_txt_id>
        <status>0</status>
        <position>30</position>
      </block>
      <block>
        <block_txt_id>content_top</block_txt_id>
        <status>1</status>
        <position>40</position>
      </block>
      <block>
        <block_txt_id>content_bottom</block_txt_id>
        <status>1</status>
        <position>50</position>
      </block>
      <block>
        <block_txt_id>content_bottom</block_txt_id>
        <status>1</status>
        <position>50</position>
      </block>
      <block>
        <block_txt_id>column_right</block_txt_id>
        <status>1</status>
        <position>60</position>
        <block>
          <block_txt_id>order_summary</block_txt_id>
          <status>1</status>
          <position>10</position>
        </block>
      </block>
      <block>
        <block_txt_id>footer_top</block_txt_id>
        <status>1</status>
        <position>70</position>
      </block>
      <block>
        <block_txt_id>footer</block_txt_id>
        <status>1</status>
        <position>80</position>
        <block>
          <block_txt_id>newsletter_signup</block_txt_id>
          <status>1</status>
          <position>40</position>
        </block>
        <block>
          <block_txt_id>content</block_txt_id>
          <status>1</status>
          <position>50</position>
        </block>
        <block>
          <block_txt_id>credit_cards</block_txt_id>
          <status>1</status>
          <position>70</position>
        </block>
        <block>
          <block_txt_id>donate</block_txt_id>
          <status>1</status>
          <position>80</position>
        </block>
      </block>
    </blocks>
  </layout>


This is my entire install.php from same folder:

Code Select Expand

<?php

if (! defined ( 'DIR_CORE' )) {
header ( 'Location: static_pages/' );
}

$file = DIR_EXT . '/joe/layout.xml';
$layout = new ALayoutManager('default');
$layout->loadXml(array('file' => $file));


Can anyone explain why the layout is empty?

Thx. 

[is]

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.