One-Page Checkout [Support Thread]

@LightBrown, there were a bunch of changes going from 1.0.5 to 1.2.0; make sure that you're using the 1.2.0 version as your "base" when you move those blocks around. I'll send you a PM with my direct email so you can email me your changes for review.

soxophoneplayer:

Is there a (not complicated) way to switch the default shipping alternative selected by OPC either from the most expensive to the least expensive, or (better yet) default to whichever option the customer selected on the shopping cart page?

In the shopping cart the alternative estimates are presented from most to least expensive, but the least expensive is auto-selected as default for the customer. They can, of course, select a more expensive option.

But on the OPC page, the most expensive option is selected as default, regardless of the option the customer selected on the shopping cart page. The customer can change the option on the checkout page and the total cost will be auto adjusted, but my concern is that a customer will select choice A on the cart page, then gloss over it (Oh I already did that I don't need to pay attention to it) on the checkout page.

Sample from shopping cart page (fake customer):

Sample from OPC page:

zc 1.5.5a, Responsive Sheffield Blue 2.0, Canada Post, One Page Checkout, many other mods.

Is there any reason why I shouldn't trigger a "default" $checked radio button (for shipping or payment) by putting this:

<script>
document.getElementById('ship-storepickup-storepickup0').checked = true;
</script>

...at the end of my includes/templates/YOUR_TEMPLATE/templates/tpl_checkout_one_default.php file?

wolfderby:

Is there any reason why I shouldn't trigger a "default" $checked radio button (for shipping or payment) by putting this:

> ...at the end of my includes/templates/YOUR_TEMPLATE/templates/tpl_checkout_one_default.php file?
While that change might cause the radio button (as well as the currently selected one!) to *display * as selected, it doesn't trigger any event to cause the storepickup to be recognized as the customer's choice.

lat9:

While that change might cause the radio button (as well as the currently selected one!) to *display * as selected, it doesn't trigger any event to cause the storepickup to be recognized as the customer's choice.

Thanks a pretty good reason! haha Any suggestion on getting a "default" selection to load automatically?

lat9:

@tmpinsnty, Did you copy the file /includes/modules/pages/checkout_payment/jscript_payeezy.php to /includes/modules/pages/checkout_one?

I've just downloaded the payment module and it looks like that might be the missing bit.

So I have Payeezy v0941b installed and One_Page_checkout 1.2.0 installed. Originally I was getting a Payeezy error that a Token was missing. I copied the jscript_payeezy.php to the /includes/modules/pages/checkout_one/ directory. I no longer get the Token error, I just get declines, but I do not believe the actual transaction is reaching out to First Data since I am not getting a decline report from them (I get email alerts on declines). If I turn One Page Checkout off the transaction completes normally. Any suggestions ?
Tony

@tonyreynolds, do you have this installed on a site I could access? If you don't want to post that information, you can always send me a Private Message.

I like the one page checkout. Very lean and mean, but I am missing a possibility to have an order confirmation page. This is needed in some countries so customers can review their order before making it definitive.

Design75:

I like the one page checkout. Very lean and mean, but I am missing a possibility to have an order confirmation page. This is needed in some countries so customers can review their order before making it definitive.
That's been a "concern" of mine, too. I'm going to make the payment-method "exclusions" list a configuration setting, so that you can specify that the payment methods that your store(s) use require confirmation.

:clap: thanks Cindy> lat9:

That's been a "concern" of mine, too. I'm going to make the payment-method "exclusions" list a configuration setting, so that you can specify that the payment methods that your store(s) use require confirmation.

lat9:

While that change might cause the radio button (as well as the currently selected one!) to *display * as selected, it doesn't trigger any event to cause the storepickup to be recognized as the customer's choice.

ended up changing logic around includes/classes/shipping.php line 206 to the following so that in-store pickup shipping method could be selected by default for the shipping method by the cheapest() function when called in header_php.php

      for ($i=0; $i<$size; $i++) {
        if (is_array($cheapest)) {
			if ($rates[$i]['cost'] < $cheapest['cost']) {
				$cheapest = $rates[$i];
			}  
        } else {
            $cheapest = $rates[$i];
        }

hopefully this is a little better than my javascript vanity that didn't do anything. (:

I'm getting "close" to a relatively major update (v1.3.0). That version:

• Implements the standardization of the checkout flow described in this posting: https://www.zen-cart.com/showthread.php?222458-One-Page-Checkout-Interoperability-Guidelines
• Moves the "review-required" payment-module list to a configurable item, enabling store's that require order-confirmation to meet that requirement.
• Adds a configuration setting (default enabled) to allow a store to control whether/not the "Shipping Address, same as Billing?" is displayed.
• Recognizes that some payment modules require confirmation, displaying a "Review" button instead of "Confirm" if such a payment-module is selected.
• Adds comments around significant sections in the checkout_one page's template, making it easier for store-owners to re-arrange the sections.
  As of this posting, the most recent version is v1.3.0-beta2 on the plugin's GitHub repository: https://github.com/lat9/one_page_checkout/releases.

I've validated the operation under FireFox, IE-11 and Chrome with various payment methods (Payeezy, Braintree, PayPal variations) but don't have developer account access to others.

If anyone has time to grab the beta and test with your favorite payment methods, I'd appreciate it! Please report back both successes and failures.

Note: This release affects any template-override version that you might have made to the tpl_checkout_one_default.php file, so you'll need to merge any customizations that you've made.

n.b. I think that the newly-released Square payment processing will work, but I'm having difficulties establishing a developer account.

lat9:

I'm getting "close" to a relatively major update (v1.3.0). That version:

• Implements the standardization of the checkout flow described in this posting: https://www.zen-cart.com/showthread.php?222458-One-Page-Checkout-Interoperability-Guidelines

• Moves the "review-required" payment-module list to a configurable item, enabling store's that require order-confirmation to meet that requirement.

• Adds a configuration setting (default enabled) to allow a store to control whether/not the "Shipping Address, same as Billing?" is displayed.

• Recognizes that some payment modules require confirmation, displaying a "Review" button instead of "Confirm" if such a payment-module is selected.

• Adds comments around significant sections in the checkout_one page's template, making it easier for store-owners to re-arrange the sections.

As of this posting, the most recent version is v1.3.0-beta2 on the plugin's GitHub repository: https://github.com/lat9/one_page_checkout/releases.

I've validated the operation under FireFox, IE-11 and Chrome with various payment methods (Payeezy, Braintree, PayPal variations) but don't have developer account access to others.

If anyone has time to grab the beta and test with your favorite payment methods, I'd appreciate it! Please report back both successes and failures.

Note: This release affects any template-override version that you might have made to the tpl_checkout_one_default.php file, so you'll need to merge any customizations that you've made.

n.b. I think that the newly-released Square payment processing will work, but I'm having difficulties establishing a developer account.

Tested 1.3.0 beta2 on a local dev site with PayPal, Direct Bank Deposit and eWay Rapid, Billing same as Shipping enabled / disabled and can happily report that all works as intended. Well done again !!!

Thanks, Frank, especially the eWay report (I'd apparently let my development site go too long without access). I've got some documentation to do, but expect to have v1.3.0 released in the next few days (unless there's a major burp).

I've just created OPC v1.3.0-beta4, available for download from the plugin's GitHub repository.

That version includes template-related changes, so if you've customized a version for your store be sure to compare against the template_default directory within the plugin's distribution. The changes from v1.3.0-beta2 can be seen here.

Since 1.3.0 is a fairly intense update, I'll hold off for a couple of days before stripping the beta off the release ... just in case someone finds another issue!

Happy 4th to all!

In admin I am getting this error> The One-Page Checkout plugin has been disabled. The file "/includes/templates/(my template name)/jscript/jscript_framework.php" is required for the plugin's proper operation..
Am I missing something? if yes, then what? I cannot find what is missing even doing a compare/merge.

@adb34, the message is telling you that a ***storefront ***file (jscript_framework.php) is missing from your template directory. The file is shipped in the OPC zip-file under the /includes/templates/YOUR_TEMPLATE/jscript directory.

Now things are getting strange. The file is in the jscript directory. After I checked this the error went.

@adb34, the error went ... where?

lat9:

@adb34, the error went ... where?

The error is no longer there

It could have been a "staging" issue. If you didn't upload all the plugin's files (both admin and storefront) before accessing the admin, it's likely that you would receive that message.