One-Page Checkout [Support Thread]

[lat9]

The latest github download works a treat for me, especially for a payment module like eWay.

Made some tweaks such as pre-selecting eWay as payment method and added a few bits and pieces which are only relevant for one of my stores. All good!

But found another little 'boo-boo':

In the file includes/templates/template_default/templates/tpl_checkout_one_confirmation_default.php the $editShippingButtonLink takes me back to the home page instead to the address book for editing the shipping address in the order.

It looks like that $editShippingButtonLink does not carry from the previous page.

So in the file includes/modules/pages/checkout_one_confirmation/header_php.php below line 95 I added

$editShippingButtonLink = zen_href_link (FILENAME_CHECKOUT_SHIPPING_ADDRESS, '', 'SSL');

and that did the trick for me.

Thanks, Frank, I had a feeling that I was going to need to get those "edit-button-link" values set when the on-page confirmation is displayed. I'll get that noted/updated as well.

[RixStix]

Question?

Does Auth.net AIM mean it has only been tested & functional with AIM?
Does that mean it has not been tested or known to not function with Auth.net SIM?

I don't want to go down a path of known headache unnecessarily.
ZC1.5.4

Not ready to go down the ZC1.5.5a road.

[lat9]

Question?

Does Auth.net AIM mean it has only been tested & functional with AIM?
Does that mean it has not been tested or known to not function with Auth.net SIM?

I don't want to go down a path of known headache unnecessarily.
ZC1.5.4

Not ready to go down the ZC1.5.5a road.

Rick, the plugin "should" work just fine with Auth.net SIM. Since the A.net AIM implementation accepts credit-card-data-onsite, my thought was that that method was going to be (one of) the edge cases.

One-Page Checkout's default installation overwrites only one core-file (/includes/classes/message_stack.php) and can be turned on/off with a single configuration click. If you've got a test-site for your store, you could "drop" the files into that file-system to do a validation.

The plugin has been verified on ZC 1.5.4, with those additional core-/template-file overwrites.

[RixStix]

Thanks Cindy.

We switched from AIM to SIM because the latest PCI version moved from SAQ-c to SAQ-d which is a significantly more onerous.

[lat9]

Thanks, Frank, I had a feeling that I was going to need to get those "edit-button-link" values set when the on-page confirmation is displayed. I'll get that noted/updated as well.

That update is now available from the plugin's GitHub repository.

[rapidfinancia1]

How do you install/turn this module on, or it it already on once you upload it?

[frank18]

How do you install/turn this module on, or it it already on once you upload it?

Installation details are in the docs which comes with this module. To activate / deactivate it you do that in Admin > Configuration > One-Page Checkout Settings > Enable One-Page Checkout? - set to True or False (also described in the docs).

[ink]

-------

[ink]

Installation details are in the docs which comes with this module. To activate / deactivate it you do that in Admin > Configuration > One-Page Checkout Settings > Enable One-Page Checkout? - set to True or False (also described in the docs).

I installed a fresh website and selected the responsive template, uploaded the Checkout one page and I get the same Jscript error and it doesnt work. Tried deleting min file in jscript folder whats wrong?

index.php?main_page=checkout_shipping:22 A parser-blocking, cross site (i.e. different eTLD+1) script, https://code.jquery.com/jquery-3.4.0.min.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message. See https://www.chromestatus.com/feature/5718547946799104 for more details.


Just thought, I did install Paypal is that not compatible?
PHP Version: 7.2.31 (Zend: 3.2.0)
Zen Cart 1.5.6c
Database Patch Level: 1.5.6

[lat9]

That console message is associated with the template's rendering (normally in the /common/html_header.php) and has nothing to do with OPC.

When you say that it doesn't work, what is it and how does it not work?