One-Page Checkout [Support Thread]

[GerriM]

First, thanks to @GerriM for granting me access to her test site so that I could investigate the issues she identified.

There are actually two underlying issues that I've identified and currently opened as issues on the OPC's GitHub repository:

Square payment inputs disappear after shipping-method change
The Square (and possibly other?) payment-method has an external jQuery script that's loaded on a full-page load, so when OPC re-loaded only the payment-selection block, that processing didn't kick in ... resulting in no input fields for the Square credit card information.

My current approach, validated by @GerriM, has its limitations. For the Square module to operate properly when the shipping method changes, it's necessary to not re-load the payment-choices block. Unfortunately, there are payment methods that are dependent on the shipping method selected (like enabling a Cash payment only when the shipping-method is store-pickup), so these payment methods absolutely require that the payment-choices' block be updated on a shipping method change.

The approach I plan to take (unless a better solution is proposed) is to add another configuration value to the One-Page Checkout Configuration, allowing a store-owner to identify payment methods that require no reload of the payment-choices' block; that setting will be initialized to identify the square method by default. What this means to store-owners utilizing OPC is that you can't have a combination of payment methods that require the block to be updated and those that require the block not to be updated.

If anyone has a better solution to the issue, I'm open to suggestions!

Taxed order-totals 'lose' their tax on payment method update.
This one was caused by the payment-method update's AJAX not initializing the order's shipping- and payment-classes prior to requesting the order-total modules to perform their calculations.

I'll be updating the OPC's GitHub in the morning with my current changes.

Your solution solved all issues for me. Thank you sooo much. You’re my hero!! OPC is a great plugin. And thanks to Dr Byte for his Square plugin assistance also.

[lat9]

I've just submitted v2.0.5 of One-Page Checkout to the Zen Cart plugins for review. This version contains changes associated with the following GitHub issues:


#133: Guest/Registered-Accounts, pre-fill Zip Code
#148: Payment change requires order-totals block update
#151: zc156 updates not fully incorporated
#152: Salutation Ms. not saved on guest-account creation
#156: Square payments input blocks disappear after shipping change
#157: Taxed order-totals 'lose' their tax on payment-method update.
#158: Correct various 'PHP Notice' issues.
#159: Partial zc156 integration; downward-compatible files only.


Please note: This version is not fully integrated with Zen Cart 1.5.6; you'll need to review the core- and template-file changes and merge the well-marked change sections into the Zen Cart 1.5.6 base. I expect to have the zc156 integration completed early next year.

This is the final release that will continue to support Zen Cart versions less than 1.5.5f, too, due to the number of changes introduced by the zc156 core.

[lat9]

I've just submitted v2.0.5 of One-Page Checkout to the Zen Cart plugins for review. This version contains changes associated with the following GitHub issues:


#133: Guest/Registered-Accounts, pre-fill Zip Code
#148: Payment change requires order-totals block update
#151: zc156 updates not fully incorporated
#152: Salutation Ms. not saved on guest-account creation
#156: Square payments input blocks disappear after shipping change
#157: Taxed order-totals 'lose' their tax on payment-method update.
#158: Correct various 'PHP Notice' issues.
#159: Partial zc156 integration; downward-compatible files only.


Please note: This version is not fully integrated with Zen Cart 1.5.6; you'll need to review the core- and template-file changes and merge the well-marked change sections into the Zen Cart 1.5.6 base. I expect to have the zc156 integration completed early next year.

This is the final release that will continue to support Zen Cart versions less than 1.5.5f, too, due to the number of changes introduced by the zc156 core.

Now available for download from the Zen Cart plugins section.

[shags38]

Hello Cindy - I would like to add some text to the PayPal image in payment selection - had a few customers 'expecting' that when they selected the paypal radio button on the payment page that it would take them immediately to PayPal (like the paypal icon on the checkout page) not realizing they need to click confirm order first which requires scrolling with a lot of white space between them (a couple have contacted me meaning a bunch of others haven't) - so in an effort to try to obviate these instances could you guide me please to where/how I can add some text to the bottom of that block, if this is possible that is - if not then no problem.

cheers, Mike
Attachment 18317

[dbltoe]

includes/modules/payment/paypalwpp.php around line 270. It's all an image from PayPal itself.

MODULE_PAYMENT_PAYPALEC_MARK_BUTTON_IMG

[shags38]

includes/modules/payment/paypalwpp.php around line 270. It's all an image from PayPal itself.

MODULE_PAYMENT_PAYPALEC_MARK_BUTTON_IMG

Many Thanks dbltoe

[GerriM]

Since I couldn't find this referenced on the ZC forum, here's some info in case it can help another not-so-experienced Zenner out there like me. Cindy, please see text in blue below re whether this affects OPC code.

An OPC javascript-like error started to appear i.e. on checkout entry, instead of the usual OPC screen, only this is displayed:

Sorry, but our expedited checkout process cannot be used. Click here to use our alternate checkout process

.
FYI, javascript errors (Firefox: F12; Console menu) displayed while SQUARE was enabled (the middle ones disappeared when SQUARE was disabled):
However, I couldn’t track the problem down & resolve this issue for ages because, just through bad luck, a server PHP version issue happened at the same time and 'muddied the waters'. But more about the PHP issue later…

My system: ZC1.5.5e; OPC v2.0.5; Template: RSB v2 modified; various payment & shipping modules including SQUARE v, Direct Bank Deposit & Australia Post Shipping Modules; lots more plugins & mods. My website: (currently under development so closed for maintenance): https://recoveredheritage.com.au/ .

First, the OPC issue + solution:
That OPC error message was caused by 2 x database entries in my zones table including an apostrophe: Côte-d'Or & Côtes-d'Armor. Internet research mentioned that one could use "a SqlParameter object to pass in values...so you don't have to worry about the apostrophes users enter in". However I did a manual work-around (replaced those apostrophes with spaces) since I'm not sure whether OPC has that functionality or if one of my other mods is interfering.

Where did the apostrophe errors come from? Back in January, after getting OPC to play well with SQUARE (with Cindy's help - thanks), I added extra countries into my zones table in the database using ZC plugins including this one. After working through ZC1.5.5 compatibility issues with the old ZC version SQL files, I did lots of testing...and thought I had nailed it . When I tested OPC the next day or so, I started getting error logs at the same time. With hind-sight being 20-20, I now know those error logs had abolutely nothing to do with the OPC issue but were, instead, to do with the PHP issue (below). But I didn't know that then so... since a site can only have one active PHP version, I headed in the wrong direction and started in on upgrading to PHP 7.2.

Now that this OPC issue is solvedI've reverted to backups and am free instead to progress towards launching the website (using PHP 7.1) while upgrading to ZC1.5.6(maybe b) locally with WAMP where I can run PHP 7.3 while testing.

And now the PHP issue:

Don't take it for granted that your hosting company will tell you when they upgrade the server PHP default version to 7.2. Mine didn't (inMotion hosting). So...if you start getting error logs out of the blue like these ones, investigate whether you can just change your site PHP version manually back to PHP 7.1 FIRST - before you assume you have to do a full PHP 7.2 upgrade like I did.

While I still had to address a few error logs even after I had reverted to Site PHP 7.1, there aren't too many so far. I think these occur when the cPanel currency cron job runs &, of course accessed the default server running PHP 7.2. (I haven't yet been able to get the SQUARE cron job to work...so fingers crossed.)

Hope this helps.