One-Page Checkout [Support Thread]

[carlwhat]

Thanks very much to lat9 for her highly-responsive support over this. I'd never have figured it out myself. It seems that OPC is not currently compatible with Braintree and other Javascript-based payment methods.

I'll be keeping an eye on OPC developments :)

hmmm...

is OPC not compatible with braintree? or is braintree not compatible with OPC?

braintree was last updated almost 3 years ago.

square webpay is a javascript based payment method. it is compatible with OPC.

i should know. i coded it.

[carlwhat]

in looking at the braintree zc code, i would now even argue that this payment module is NOT a javascript based payment method.

in addition, it looks to be based on braintree sdk 3.4.0 which was deprecated on 3/2022; and unsupported as of 3/2023.

the latest braintree php sdk was released 2 weeks ago, and is version 6.16.0.

[BillJ]

in looking at the braintree zc code, i would now even argue that this payment module is NOT a javascript based payment method.

in addition, it looks to be based on braintree sdk 3.4.0 which was deprecated on 3/2022; and unsupported as of 3/2023.

the latest braintree php sdk was released 2 weeks ago, and is version 6.16.0.

Despite (mistakenly) saying otherwise earlier, I'm using Braintree Payments 2.2.7 downloaded from the Numinix web-site, released September 2023 and usind SDK 6.9.1. A lot of the Braintree API revolves around the client, with some server involvement.

[lat9]

hmmm...

is OPC not compatible with braintree? or is braintree not compatible with OPC?

braintree was last updated almost 3 years ago.

square webpay is a javascript based payment method. it is compatible with OPC.

i should know. i coded it.

Right, some payment-module developers pay attention to their module's interaction with OPC; others, not so much!

[BillJ]

Right, some payment-module developers pay attention to their module's interaction with OPC; others, not so much!

Perhaps when OPC becomes part of the Zen Cart core then their hand will be forced since if it is incompatible with OPC then it is incompatible with Zen Cart. Until then we have two third-party modules for Zen Cart that are incompatible with each other.

However... :)
@lat9, what is it that OPC is expecting to happen that the Square Webpay module is doing but the Braintree module isn't doing? I'd have a go at updating the Braintree module if I knew what that was.

[OJ_SIMON]

I have ZC v1.5.8a and One-Page Checkout V 2.4.6
I'm getting this error:

[02-Feb-2024 18:37:43 UTC] PHP Notice:  Country with countries_id = 223 is either disabled or does not exist. in /home/xxx/xxx/public_html/includes/functions/html_output.php on line 896

223 is US and 222 is the UK and I only have uk active in admin and it is only happening on index.php?main_page=checkout_one
so is there a hard coded use of countries_id = 223 in the script as I have looked and can not see

[OJ_SIMON]

I ended up just enabling US and the error has fixed and also I'm not getting anymore errors yet.

[carlwhat]

I have ZC v1.5.8a and One-Page Checkout V 2.4.6
I'm getting this error:

[02-Feb-2024 18:37:43 UTC] PHP Notice:  Country with countries_id = 223 is either disabled or does not exist. in /home/xxx/xxx/public_html/includes/functions/html_output.php on line 896

223 is US and 222 is the UK and I only have uk active in admin and it is only happening on index.php?main_page=checkout_one
so is there a hard coded use of countries_id = 223 in the script as I have looked and can not see

a lot of assumptions going on here...

none of which look to be true... i could be wrong...

did you look at the code? specifically where the error is?

that looks to be where your problem probably is.

from your admin -> configuration -> customer details -> Create Account Default Country ID

what is that set to? default is 223; you probably want it at 222. then you can disable the US once again.

so i do not think that this issue is OPC related nor do i think that 223 was hard coded. but both configuration keys, STORE_COUNTRY and SHOW_CREATE_ACCOUNT_DEFAULT_COUNTRY, need to be set to 222.

best.

[simon1066]

ZC v1.5.8a
OPC v2.4.6

On my create account (registered) page I have the compulsory privacy checkbox enabled and, unlike the newsletter checkbox, it does not remain checked upon page reload.

This would normally not be an issue except that I am now adding a reCaptcha to this page and if it is missed by the customer - it will cause a reload and clearing of the privacy checkbox, which may then be subsequently missed potentially causing yet another refresh and customer frustration.

I would like the privacy checkbox to remain checked on page reload. For a registered account the code is

\includes\templates\MY_TEMPLATE\templates\tpl_create_account_register.php

<?php 
    echo zen_draw_checkbox_field('privacy_conditions', '1', false, 'id="privacy"');
?>
<label class="checkboxLabel" for="privacy"><?php echo TEXT_PRIVACY_CONDITIONS_CONFIRM;?></label>

\includes\modules\pages\create_account\header_php_create_account_register.php

    if (DISPLAY_PRIVACY_CONDITIONS === 'true') {
        if (!(isset($_POST['privacy_conditions']) && $_POST['privacy_conditions'] === '1')) {
            $error = true;
            $messageStack->add('create_account', ERROR_PRIVACY_STATEMENT_NOT_ACCEPTED, 'error');
        }
    } 

This obviously also occurs if it is a create account (full) page.

[lat9]

ZC v1.5.8a
OPC v2.4.6

On my create account (registered) page I have the compulsory privacy checkbox enabled and, unlike the newsletter checkbox, it does not remain checked upon page reload.

This would normally not be an issue except that I am now adding a reCaptcha to this page and if it is missed by the customer - it will cause a reload and clearing of the privacy checkbox, which may then be subsequently missed potentially causing yet another refresh and customer frustration.

I would like the privacy checkbox to remain checked on page reload. For a registered account the code is

\includes\templates\MY_TEMPLATE\templates\tpl_create_account_register.php

<?php 
    echo zen_draw_checkbox_field('privacy_conditions', '1', false, 'id="privacy"');
?>
<label class="checkboxLabel" for="privacy"><?php echo TEXT_PRIVACY_CONDITIONS_CONFIRM;?></label>

\includes\modules\pages\create_account\header_php_create_account_register.php

    if (DISPLAY_PRIVACY_CONDITIONS === 'true') {
        if (!(isset($_POST['privacy_conditions']) && $_POST['privacy_conditions'] === '1')) {
            $error = true;
            $messageStack->add('create_account', ERROR_PRIVACY_STATEMENT_NOT_ACCEPTED, 'error');
        }
    } 

This obviously also occurs if it is a create account (full) page.

Yep, that's just mimicking the behavior of the default tpl_modules_create_account.php. You can change that behavior by the following change:

<?php 
    echo zen_draw_checkbox_field('privacy_conditions', '1', isset($_POST['privacy_conditions']), 'id="privacy"');
?>
<label class="checkboxLabel" for="privacy"><?php echo TEXT_PRIVACY_CONDITIONS_CONFIRM;?></label>