One-Page Checkout [Support Thread]

[frank18]

I've created an issue on GitHub to track this change for the upcoming v1.0.12 release. The solution to the order-totals duplication is available on GitHub at this time.

Please note that a change to the checkout_one_confirmation page's template is required, so watch for that on a update if you've created a template-override for your store.

Thanks Cindy, 1.0.12beta2 works a treat.

Cheers / Frank

[lat9]

Thanks Cindy, 1.0.12beta2 works a treat.

Cheers / Frank

Thanks for the update, Frank, that you concur the issue is now resolved!

As a side-note, I've tweaked the plugin's next version to 1.1.0 (currently 1.1.0-beta1 on GitHub) as I've updated the plugin's configuration settings to allow a "conditional" enabling by customer_id. That way, store-owners that have shipping, payment or order-total modules (or templates) that haven't yet been found to work with the One-Page Checkout can install the plugin but enable it only for specific customers during a validation period.

[lat9]

Never mind, found the answer (Gateway Processing Services Module (3-step redirect)) in your previous post. I'm thinking that this payment method might need to be added to the OPC's "confirmation-required" list.

@designguy, would you mind trying the following change? Edit /includes/modules/pages/checkout_one_confirmation/header_php.php, find the following section:

// -----
// There are some payment methods (like eWay) that "replace" the confirmation form via the HTML they return on
// the "process_button" payment-class function.  Rather than hard-code the list in code, below, the following
// constant will be updated as additional payment-methods that make use of that interface are identified.
//
if (!defined ('CHECKOUT_ONE_CONFIRMATION_REQUIRED')) {
    define ('CHECKOUT_ONE_CONFIRMATION_REQUIRED', 'eway_rapid,stripepay');
}

and change that to

// -----
// There are some payment methods (like eWay) that "replace" the confirmation form via the HTML they return on
// the "process_button" payment-class function.  Rather than hard-code the list in code, below, the following
// constant will be updated as additional payment-methods that make use of that interface are identified.
//
if (!defined ('CHECKOUT_ONE_CONFIRMATION_REQUIRED')) {
    define ('CHECKOUT_ONE_CONFIRMATION_REQUIRED', 'eway_rapid,stripepay,gps');
}

That forces the OPC's confirmation page to display for the GPS payment method. Does that correct the issue on your store?

I'll have to set up a test store and try it out. I'll let you know how it goes. Although my first thought is that it is more the gateway's API than the confirmation just because the gateway itself seems to be expecting the information to come at it in 3 stages.

@designguy, I'm going to go with my gut on this one and add the gps payment method to the list of payments that require the confirmation page. That update will be in the forthcoming v1.1.0 release of the One-Page Checkout.

[lat9]

I've just submitted v1.1.0 of One-Page Checkout to the Zen Cart plugins for review; I'll post back once it's available there.

That release contains updates to address the following issues (identified by their GitHub issue number):

#76: Add confirmation required for Gateway Processing Services Module (3-step redirect)
#74: Update configuration to add "conditional" enablement
#73: Correct duplicate order-total values on the confirmation page
#72: Correct checkout-loop when an order's currency symbol includes htmlentities, e.g. `£`
#71: Correct shipping cost not updated when additional products are added to an order.

[lat9]

v1.1.0 is now available for download.

[mydanilo]

Love the one page checkout. Works great. Now I need to combine it with COWOA. Did not have any luck. Using 1.5.5d with Winchester Responsive template. Does anyone have a working site with both modules merged? I would love to learn in what order you went about. Merging all these files got way out of hand for me.

[LightBrown]

Does anyone have a working site with both modules merged?

I can confirm that COWOA and OPC can work together. We do have quite a bit of custom code though, and I can't really recall how much I had to do to get OPC to work with COWOA, but it doesn't seem like it was too much.

Use a development copy of your site and just work through your problems one at a time.

[lat9]

I can confirm that COWOA and OPC can work together. We do have quite a bit of custom code though, and I can't really recall how much I had to do to get OPC to work with COWOA, but it doesn't seem like it was too much.

Use a development copy of your site and just work through your problems one at a time.

Thanks for that update, @LightBrown. Which version of COWOA did you use for the integration?

[mydanilo]

Following up on COWOA with One Page Checkout. Had to use my templates includes\templates\MY_TEMPLATE\common\tpl_header.php AND tpl_main_page.php otherwise template breaks as reported before.

The next edits were done so the order steps does not display as we use OPC.

no_account.php

Removed the following

define('HEADING_TITLE', 'Step 1 of 5 - Billing Information');

replaced with

define('HEADING_TITLE', 'Billing Information');

tpl_no_account_default.php

removed

<!-- bof Order Steps (tableless) -->
    <div id="order_steps">
            <div class="order_steps_text">
			
			<span id="active_step_text_COWOA"><i class="fa fa-file-text-o"></i><br /><?php echo TEXT_ORDER_STEPS_BILLING; ?></span><span class="order_steps_text1_COWOA"><i class="fa fa-truck"></i><br /><?php echo TEXT_ORDER_STEPS_1; ?></span><span class="order_steps_text2_COWOA"><i class="fa fa-credit-card"></i><br /><?php echo TEXT_ORDER_STEPS_2; ?></span><span class="order_steps_text3_COWOA"><i class="fa  fa-pencil-square"></i><br /><?php echo TEXT_ORDER_STEPS_3; ?></span><span class="order_steps_text4_COWOA"><i class="fa fa-check"></i><br /><?php echo TEXT_ORDER_STEPS_4; ?></span>
            </div>
            <div class="order_steps_line_2">
		  <span class="progressbar_active_COWOA">&nbsp;</span>
                <span class="progressbar_inactive_COWOA">&nbsp;</span><span class="progressbar_inactive_COWOA">&nbsp;</span><span class="progressbar_inactive_COWOA">&nbsp;</span><span class="progressbar_inactive_COWOA">&nbsp;</span>
            </div>
    </div>
<!-- eof Order Steps (tableless) -->

did not use the admin\incudes\stylesheet.css as it would break my admin display. Not sure why tho.

I moved some stuff around in tpl_login_cowoa_default.php as I did not like the layout of the page. But that is just personal and had nothing to do with functionality.

[RixStix]

Hi Cindy,

OPC ver 1.1.0
OPC doesn't work worth a flip if you forget to copy the plugin's ajax.php file

Checkout using auth.net SIM completes with myDEBUG generated
Checkout using PPEC from shopping cart screen completes but generates 2 myDEBUG files and myDEBUG_OPC file.
Checkout by selecting PP in the Payment Methods on checkout screen completes but generates 5 myDEBUG and myDEBUG_OPC file.

Looks like multiple myDEBUG_OPC instances are combined into a single file instead of a separate file for each instance?

The myDEBUG files are greek to me and I can send them to you.

Suggestions? I call myself stepping through the install several times. That's how I caught the missed ajax.php file.
TNX
Rick
=====================================

The RED banner "Your order's details have changed. Please review the current values and re-submit." is annoying when submitting the payment the first time using the prefilled defaults, selecting payment method and only clicking the SUBMIT button.

ZC 1.5.4
Westminster_New template

I have shipping modules in service that are not in the OPC readme and a commercial OT mod with 2 variants installed.
Credit card payment is auth.net SIM (not listed in the OPC readme).

shipping:
USPS
Fedex
freeshipper
freeoptions x 2
storepickup

order_total:
discount coupon
group pricing
low order (installed but disabled)
prowebs optionone
prowebs optiontwo
quantity discount
shipping
subtotal
tax
total

payment:
auth.net SIM
PayPal EC
Check/money order installed but disabled
auth.net AIM installed but disabled