Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
Carbonless
ZC 1.5.7c
ZCAbootstrap
OPC 2.3.9
upon clicking on checkout, I recieve the same error that Designs75 mentions in post:
I made the change to includes/classes/shipping.php per your link above, and the same error persists... I'm stummped.
Thanks to the AMAZING insight of Lat9... the issue was resolved by turning on otshipping in the admin>modules>order total>Shipping
It was off as the only "Shipping" method is Store Pickup. Once turned on, issue resolved!
THANK YOU LAT9!
Re: One-Page Checkout [Support Thread]
@lat9
Hi Cindy,
Problem:
Customer checks out w/o making an account.
When customer wishes to submit a product review then customer needs an account after all. :(
Would it be possible to let the customer to enter her/his email address + one or more of the obligatory fields entered at checkout or perhaps the order number?
Or are there other solutions perhaps?
Just removing the code that prevents submitting reviews w/o account seems a bad idea to me...:smile:
Thanks,
jpda
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
jpda
@lat9
Hi Cindy,
Problem:
Customer checks out w/o making an account.
When customer wishes to submit a product review then customer needs an account after all. :(
Would it be possible to let the customer to enter her/his email address + one or more of the obligatory fields entered at checkout or perhaps the order number?
Or are there other solutions perhaps?
Just removing the code that prevents submitting reviews w/o account seems a bad idea to me...:smile:
Thanks,
jpda
The Reviews Updated (https://www.zen-cart.com/downloads.php?do=file&id=1442) plugin enables a store to have guests write reviews.
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
lat9
Thanks for your very quick response! :)
I will try it, seems a very reliable autor :smile:
jpda
1 Attachment(s)
Re: One-Page Checkout [Support Thread]
Adding the OPC to my main site... using OPC 2.3.9 , with ZCA Bootstrap 3.2 and bs4OPC 1.02
When entering the OPC on the site, it isn't allowing the credit card fields to be displayed... using Square Payments Module 1.5
Attachment 19858
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
Carbonless
Adding the OPC to my main site... using OPC 2.3.9 , with ZCA Bootstrap 3.2 and bs4OPC 1.02
When entering the OPC on the site, it isn't allowing the credit card fields to be displayed... using
Square Payments Module 1.5
Attachment 19858
Did you copy the Square Payments module's jscript_*.js/php file to the checkout_one directory?
1 Attachment(s)
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
lat9
Did you copy the Square Payments module's jscript_*.js/php file to the checkout_one directory?
no I hadn't. I copied it to the checkout_one directory in the same folder... I now can enter the cc fields, however, I'm still getting this warning once I click on shopping cart:
Attachment 19859
1 Attachment(s)
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
Carbonless
no I hadn't. I copied it to the checkout_one directory in the same folder... I now can enter the cc fields, however, I'm still getting this warning once I click on shopping cart:
here is my setup
Attachment 19860
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
Carbonless
no I hadn't. I copied it to the checkout_one directory in the same folder... I now can enter the cc fields, however, I'm still getting this warning once I click on shopping cart:
Attachment 19859
If you enable your browser's "Developer Tools" (F12 for Windows-based browsers) and then click the Console tab, there will be messages issued by the OPC's jQuery that identify what elements are missing.
Re: One-Page Checkout [Support Thread]
Quote:
Originally Posted by
lat9
If you enable your browser's "Developer Tools" (F12 for Windows-based browsers) and then click the Console tab, there will be messages issued by the OPC's jQuery that identify what elements are missing.
ahhh.. I changed #ottotal> div:first-child to #ottotal > , removing the div tag... that removed the error