One-Page Checkout [Support Thread]

The issue that @meksicus identified is due to the way that OPC (currently) manages the order's progress-to-submittal, since the full checkout_one page isn't re-rendered on a "simple" change to the shipping method.

Because of that, the changes that s/he made to disable the **cash **payment-method when the shipping-method chosen was **flat **aren't being told of any change in shipping until the order is initially submitted. Once the order's submitted, the checks on the checkout_one_confirmation page kick in and the customer is redirected back to the main order-entry page.

I'll need to think on this some and have opened an issue on the OPC's GitHub repository to track any changes: https://github.com/lat9/one_page_checkout/issues/127

I am trying this with the bootstrap template and really appreciate all of the work you have put into it, thanks so much for sharing this! Do you think it would make more sense from a user's POV to keep all of the input windows in the same place on the page so they don't have to scroll down to do the next inputs? If you don't agree, can you please tell me if it's doable and where I would look to edit the current behavior?

@lankeeyankee, are you suggesting some kind of "auto-tabbing" or just a different layout of the information?

I mean when I am on the checkout page, guest checkout in this example, I fill in the contact info window and click save changes. It then opens the billing address window which on my 17" laptop is mostly "below the fold" and I have to scroll down the page to fill it in. It's just a small user experience adjustment if we can keep the modal boxes height-centered in the viewport on initial render no matter where they are on the page, or maybe cursor -centered if that is possible.

I know I can just tab through the fields and it will keep scrolling the window up, but I think it might look better/be more "don't make me think" if it was all in view.

I have partially solved this, by moving the labels in front of the inputs> lankeeyankee:

I mean when I am on the checkout page, guest checkout in this example, I fill in the contact info window and click save changes. It then opens the billing address window which on my 17" laptop is mostly "below the fold" and I have to scroll down the page to fill it in. It's just a small user experience adjustment if we can keep the modal boxes height-centered in the viewport on initial render no matter where they are on the page, or maybe cursor -centered if that is possible.

I know I can just tab through the fields and it will keep scrolling the window up, but I think it might look better/be more "don't make me think" if it was all in view.

@lankeeyankee and @Design75, thanks for the update. That gives me "focus"!

lankeeyankee:

I mean when I am on the checkout page, guest checkout in this example, I fill in the contact info window and click save changes. It then opens the billing address window which on my 17" laptop is mostly "below the fold" and I have to scroll down the page to fill it in. It's just a small user experience adjustment if we can keep the modal boxes height-centered in the viewport on initial render no matter where they are on the page, or maybe cursor -centered if that is possible.

I know I can just tab through the fields and it will keep scrolling the window up, but I think it might look better/be more "don't make me think" if it was all in view.

Could use jquery

$(window).load(function(){
    $('html, body').animate({
        scrollTop: $('.opc-view .card-header').offset().top
    }, 'slow');
});

This of course would assume your using the ZCA Bootstrap Template with OPC overrides.

rbarbour:

Could use jquery

$(window).load(function(){
$('html, body').animate({
scrollTop: $('.opc-view .card-header').offset().top
}, 'slow');
});

> 
> This of course would assume your using the ZCA Bootstrap Template with OPC overrides.
Nice one, thanks a lot! Works perfectly (with ZCABST and OPC). I put it in includes/modules/pages/checkout_one/jscript_main.php.

lankeeyankee:

Nice one, thanks a lot! Works perfectly (with ZCABST and OPC). I put it in includes/modules/pages/checkout_one/jscript_main.php.
Please note that the change above could cause issues when updating OPC, since the overall change that I'm looking at involves a similar jQuery change but imbedded in its loaded jquery module.

I can confirm that so far with initial testing, OPC works with Ceon Advanced Shipper (woohoo!!)

lat9:

Please note that the change above could cause issues when updating OPC, since the overall change that I'm looking at involves a similar jQuery change but imbedded in its loaded jquery module.

Cindy,

Didn't mean to overstep here, just offering a suggestion not a fix.

rbarbour:

Cindy,

Didn't mean to overstep here, just offering a suggestion not a fix.
You didn't overstep, as I mentioned above I'll plan on a variant of your suggestion as the full-up fix.

ZC v1.5.5f
PHP 7.1.9
Mods: css_js_loader (I've tried with this disabled), DPU, SBA, CEON URI

Following up on my posts a couple of pages back, a reinstall of OPC 2.0 and I'm still having problems. I'll clarify again now that I know a bit more.

I have removed/disabled all shipping and payment modules except cod payment and per item shipping. I have no Zones.

For a Full Account Checkout (multiple stored addresses) I don't see the drop down list for selecting a different shipping address. I am however able to edit and save the default shipping address and the jscript that allows this is working.

If I edit the address and click 'Cancel' the drop down list appears.

If I delete the following code from tpl_modules_opc_shipping_address.php, the list appears and all seems to work well - selecting, changing, saving etc.

$opc_disable_address_change = $editShippingButtonLink;

The code that creates a list in tpl_modules_opc_address_block.php says:

'If the address can be changed and an account-bearing customer has previously-defined addresses, create a dropdown list from which they can select.'

I can change the address, manually, so I can't figure out why the dropdown list is not appearing.

Things I've tried,

disabled all javascript other than that needed to run OPC on the checkout page.
switched to Classic template
changed PHP versions
checked for browser console errors
enabled OPC debug - although I'm not sure what I should be looking for.

@simon1066, what happens if you change the line you identified to read

$opc_disable_address_change = [B]![/B]$editShippingButtonLink;

You're a star! I had tried a couple of similar changes but not that one.

Thank you.

simon1066:

You're a star! I had tried a couple of similar changes but not that one.

Thank you.
I'll get that issue noted on GitHub. Its correction will be included in the 2.0.1 release of One-Page Checkout.

LOST IN V 2.0

Was working fine before the upgrade from 1.5 but now I have two problems .
First the Enable One-Page Checkout? true false setting on the configuration - doesnt work !

I get the correct "The One-Page Checkout plugin was successfully upgraded from [] to [2.0.0 (2018-04-27)]." message Enable One-Page Checkout?OPC does not kick in and there is no apparent difference between checkout sequence with either setting - I have reloaded it three times.
I tried dropping back to the previous version 1.5.0 which does work. Am I just being really stupid and missing something ??

Second editing the confirmation email (I want to miss out a few Divs) now seems to have no effect
Surely that hasnt gone to a new file ?

Not very urgent - 1.5 does all i require - but I am puzzled!

shayne:

LOST IN V 2.0

Was working fine before the upgrade from 1.5 but now I have two problems .
First the Enable One-Page Checkout? true false setting on the configuration - doesnt work !

I get the correct "The One-Page Checkout plugin was successfully upgraded from [] to [2.0.0 (2018-04-27)]." message Enable One-Page Checkout?OPC does not kick in and there is no apparent difference between checkout sequence with either setting - I have reloaded it three times.
I tried dropping back to the previous version 1.5.0 which does work. Am I just being really stupid and missing something ??

Second editing the confirmation email (I want to miss out a few Divs) now seems to have no effect
Surely that hasnt gone to a new file ?

Not very urgent - 1.5 does all i require - but I am puzzled!
What, specifically, do you mean when you say that OPC does not "kick in"?
Have you verified that OPC is, in fact, enabled through its configuration?
Did you make any template-override customizations to OPC 1.5? Many of the templates changed significantly going from 1.5 to 2.0.

Your question regarding confirmation email is outside of the OPC's changes and would be best asked outside of this support thread.

First - yes indeed the Confirmation Email I would expect to be totally a different issue - but the problem did/does go along with the change from 1.5 to 2 - so I mentioned it. But it seems we can just put that to one side.

However I have a working install ZC 1.5.5f using responsive classic which works fine with OPC1.5.
Indeed there are a number of changes I have made but nothing I can see which would be SO basic as to just stop OPC dead.

I have a full backup code and DB which I am using as reference - done BEFORE the original 1.5 OPC install .

I install 1.5 - all works as expected

Starting from the same point I install OPC 2.

I get the confirmation message - "The One-Page Checkout plugin was successfully upgraded from [] to [2.0.0 (2018-04-27)].
I set Enable One-Page Checkout? to true.
So far exactly as 1.5
BUT the Checkout sequence remains as standard !

So wheel off somewhere - I am a bit suspicious that I may have problem with template definition but cant see where.

So the simple question is - if the OPC says it is installed and the switch is set to true - what would stop the OPC firing and the standard one running??

I am IT guy of tens of years of experience - but could I just check precisely what you mean when you talk about merging files just in case your definition is not the same as mine - i am using WinMerge.

I have a file " The old ONE " from ZC I have a file "the new one" from the OPCInstall
They are different .
By Merge do you mean
Retain all the old code but overwrite any differences including additions from the New or
Aditionally dump any parts of the old code which do not exist in the new
or do I simply replace the old with the new?
May seem obvious but always good to check !

If no one can give me a pointer then I shall do an install from base ZC and add OPC 2 from scratch

@shayne, the "brains" of the One-Page Checkout is /includes/classes/OnePageCheckout.php, working in conjunction with /includes/classes/observers/class.checkout_one_observer.php. If either of those are "damaged" (especially the observer-class), then the page-to-page handling won't kick in.