Re: One-Page Checkout [Support Thread]
I can see that the form elements are disabled by activating a layer over them. This is done on page load depending, ultimately, on the OnePageCheckout class attribute $billtoAddressChangeable. However, I can't see where this is ever set to true. And even if I try initialising it to true in the constructor, the layer is still not activated.
Re: One-Page Checkout [Support Thread]
@BillJ, check the browser's console-log (F12 for developer tools on most modern browsers) to see if anything is amiss in jQuery-land.
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
lat9
@BillJ, check the browser's console-log (F12 for developer tools on most modern browsers) to see if anything is amiss in jQuery-land.
Thanks, Cindy. I've been using developer mode quite a bit and that's how I found the layer wasn't active on my site while it is on yours.
What in particular should I look for with jQuery? As far as I can tell I'm using the default jQuery that comes with the 1.5.7c distribution but then again everything else looks OK too so there's clearly something wrong that I'm not seeing yet :)
Re: One-Page Checkout [Support Thread]
On the console I see:
Code:
setFormSubmitButton, payment-module: null jquery.checkout_one.min.js?1622987705:5
Showing "confirm" jquery.checkout_one.min.js?1622987705:5
Setting orderConfirmed (0), submitter (null) jquery.checkout_one.min.js?1622987705:5
jQuery version: 3.5.1
Re: One-Page Checkout [Support Thread]
One thing I have just noticed, on the checkout page there briefly appears a red box with the JS_ERROR_OPC_NOT_ENABLED message ("Our expedited checkout process is temporarily unavailable", etc.). It disappears quickly and I don't always see it. I don't know if that is expected. I don't see it on the demo site.
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
BillJ
One thing I have just noticed, on the checkout page there briefly appears a red box with the JS_ERROR_OPC_NOT_ENABLED message ("Our expedited checkout process is temporarily unavailable", etc.). It disappears quickly and I don't always see it. I don't know if that is expected. I don't see it on the demo site.
I've also noticed this. I initially thought it was caused by a delay in the loading of javascript files, I made sure the min versions of OPC javascript were loaded and also disabled other scripts running on my site. I did wonder whether it was a server performance issue, but it occurs on my dev site (slower) as well as my live.
I was never able to pinpoint the cause for the brief warning message.
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
simon1066
I've also noticed this.
Thanks, Simon. It probably isn't connected with my issue, then. I don't mind it happening as it is very brief but I just wondered if it might be a clue.
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
BillJ
Thanks, Simon. It probably isn't connected with my issue, then. I don't mind it happening as it is very brief but I just wondered if it might be a clue.
Yes, if there is a bunch of latency in the checkout_one page's loading (css/javascript) you'll see that message temporarily until the OPC's jQuery gets loaded to 'hide' that message.
@BillJ, would you either post a link to the site or send me via PM?
Re: One-Page Checkout [Support Thread]
Thanks - I've PM'd you the link since the supgraded site isn't live yet.
Re: One-Page Checkout [Support Thread]
@BillJ, thanks for that. While the inclusion of the "Shipping, same as billing" checkbox is as expected (I do need to update that demo site), the inclusion of the blocks other than the shopping-cart (i.e. current products) list should not be displayed until the addresses have been validated. I'll open an issue on the OPC GitHub repository to track the change(s) required.