violinman Posted October 25, 2017 Share Posted October 25, 2017 Hello, I had this same problem a few months ago but not sure how I managed to resolve it. I am using the Galaxy X skin, when a customer tries to purchase the "Secure Checkout" and the "Update Basket" buttons do not work so it is not possible to checkout and pay. Any suggestions much appreciated. Brian Quote Link to comment Share on other sites More sharing options...
Al Brookbanks Posted October 25, 2017 Share Posted October 25, 2017 Has you tried asking the developer? https://www.cubecart.com/extensions/developer/patrick-bullert Quote Link to comment Share on other sites More sharing options...
violinman Posted October 25, 2017 Author Share Posted October 25, 2017 Hello Al, I emailed him last night but no reply as yet. I hope he will respond soon. Brian Quote Link to comment Share on other sites More sharing options...
bsmither Posted October 25, 2017 Share Posted October 25, 2017 Please remind us where we may able to view your situation. Quote Link to comment Share on other sites More sharing options...
violinman Posted October 25, 2017 Author Share Posted October 25, 2017 Hello, my site is www.westcountryviolins.com If you want to test what happens when you go through adding an item to the cart you can use any item or this test item: https://www.westcountryviolins.com/wcv-test-payment.html Brian Quote Link to comment Share on other sites More sharing options...
bsmither Posted October 25, 2017 Share Posted October 25, 2017 View Basket: Using that particular product, I cannot make any changes (e.g., quantity), so updating the basket is pointless. But clicking that button does post the form and I get a new page returned. Checkout (_a=confirm): I get the form to fill in my name and address. Is this where the problem manifests itself? Do you have CubeCart requiring a response to a Captcha? Do have CubeCart requiring the customer to check a box for "Agree to a Terms & Conditions" checkbox? Neither the captcha nor the T&C checkbox is shown. Which will block the checkout sequence if required. Quote Link to comment Share on other sites More sharing options...
violinman Posted October 25, 2017 Author Share Posted October 25, 2017 That is the initial basket page, if you progress to the next page (2 Checkout at the top) where you add contact details and address this is the page where neither of the two buttons work so you cannot move onto the final stage which is to the payment page. Brian Quote Link to comment Share on other sites More sharing options...
bsmither Posted October 25, 2017 Share Posted October 25, 2017 (edited) Do you have CubeCart requiring a response to a Captcha? Do you have CubeCart requiring the customer to check a box for "Agree to Terms & Conditions" checkbox? Neither the captcha nor the T&C checkbox is shown. Which will block the checkout sequence if required. Edited October 25, 2017 by bsmither Quote Link to comment Share on other sites More sharing options...
violinman Posted October 25, 2017 Author Share Posted October 25, 2017 Captcha is not required, interesting point about Terms & Conditions though, I would have removed that at some point a few months ago but maybe it is still required! Where would I disable that requirement? I don't think it is a toggle in admin anywhere. I appreciate your thoughts, the "Terms & Conditions" is certainly worth considering. Brian Quote Link to comment Share on other sites More sharing options...
bsmither Posted October 25, 2017 Share Posted October 25, 2017 (edited) There are two aspects: javascript-powered 'required' validation, and CubeCart 'data-present' validation. Since the page is not submitting, the problem is with the rules found in the file 3.cubecart.validate.js. What I am not sure, but makes sense - sort of - is that if there is a rule that a field is required, but the field does not exist, then is the rule still enforced? For example, line 163: username: { required: true, email: true }, This field is hidden if the "Already Registered? Login" is not activated. So, if something is hidden, or not even present, the rule for it has to be ignored - that just makes sense (I hope). So, I'm reviewing the rules and matching them up with fields that may not be showing, but are not hidden either. I also see this near the HTML for the Checkout button: <input type="hidden" name="proceed" value="1"><input type="hidden" name="proceed" value="1"><input type="hidden" name="proceed" value="1"></form> I do not know if three of these inputs will confuse anything. That is added via javascript when the button is clicked. So it can't confuse anything. Edited November 6, 2018 by bsmither Quote Link to comment Share on other sites More sharing options...
bsmither Posted October 25, 2017 Share Posted October 25, 2017 Well, the form checks out as valid - that is, when it has all fields filled in with valid data. So that just leaves why the button won't submit. Quote Link to comment Share on other sites More sharing options...
violinman Posted October 25, 2017 Author Share Posted October 25, 2017 I am sort of following you, I get impression that you are still considering the possibilities. I understand your thinking around the rules but it may be that the field such as Terms & Conditions had been commented out by me which is not the same as disabling it. Brian Quote Link to comment Share on other sites More sharing options...
bsmither Posted October 25, 2017 Share Posted October 25, 2017 If a field is in a comment, then absolutely nothing is going to find/see it. Quote Link to comment Share on other sites More sharing options...
bsmither Posted October 25, 2017 Share Posted October 25, 2017 I've done all that I can think of doing - not having this skin myself. Hopefully the skin programmer will get in touch, or you find a backup and compare what you did earlier. Quote Link to comment Share on other sites More sharing options...
violinman Posted October 26, 2017 Author Share Posted October 26, 2017 One last thought, I did change my site to SSL around the time when it was last working. Could that have any bearing on the matter? Brian Quote Link to comment Share on other sites More sharing options...
bsmither Posted October 26, 2017 Share Posted October 26, 2017 (edited) It might. If the browser determines the SSL certificate does not match the domain, or if the "path" of the cookie does not match the path of the website (such as path=cube), then the browser will not allow a form to submit. But I see nothing wrong with the cookie. Edited October 26, 2017 by bsmither Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.