Jump to content

keat

Member
  • Posts

    1,571
  • Joined

  • Last visited

  • Days Won

    25

Everything posted by keat

  1. It works. For clarity to save scrolling through the trial and error: In classes\cubecart.class find: foreach ($GLOBALS['hooks']->load('class.cubecart.construct.confirm') as $hook) include $hook; below this add: // t&c if (!$GLOBALS['config']->get('config', 'disable_checkout_terms') && ($GLOBALS['db']->select('CubeCart_documents', false, array('doc_terms' => '0')) !== false) && !isset($_POST['terms_agree'])) { $GLOBALS['gui']->setError($GLOBALS['language']->account['error_terms_agree']); $errors['terms_agree'] = true; } $GLOBALS['smarty']->assign('TERMS_CONDITIONS', (!$GLOBALS['config']->get('config', 'disable_checkout_terms') && (($terms = $GLOBALS['db']->select('CubeCart_documents', false, array('doc_terms' => '1'))) !== false)) ? $GLOBALS['seo']->buildURL('doc', $terms[0]['doc_id'], '&') : false); if (isset($_POST['terms_agree']) && $_POST['terms_agree']==1) {$this->_basket['terms_agree'] = true;} $GLOBALS['smarty']->assign('TERMS_CONDITIONS_CHECKED', (isset($this->_basket['terms_agree']) && $this->_basket['terms_agree']) ? 'checked="checked"' : '' ); // end t&c Using the mican skin, in templates/content.checkout.confirm.php Find: <option value="{$address.address_id}" {$address.selected}>{$address.description} - {$address.first_name} {$address.last_name}, {$address.line1}, {$address.postcode}</option> {/foreach} </select> </p> {/if} below this add: {if $TERMS_CONDITIONS} <div><label for="reg_terms">&nbsp;</label><span><input type="checkbox" id="reg_terms" name="terms_agree" value="1" {$TERMS_CONDITIONS_CHECKED} /> <a href="{$TERMS_CONDITIONS}" target="_blank">{$LANG.account.register_terms_agree}</a></span></div> {/if}
  2. With the code added to cubecart.class and the new code above added to content.confirm.php, the check box appears, the hyperlink also takes me to the correct page. However, I can still progress to checkout without completing the checkbox.
  3. As I'm logged in as a user at the time, is something maybe halting the triggering of this ?
  4. keat

    gdpr

    On the subject of consent. I'm still waiting for Google, Ebay, Facebook, Twitter, Microsoft and any other huge corporate I've had dealings with to physically ask me for my consent to be contacted. I've had lots of communications from them, but not a single one asking for me to complete a check form saying that I consent. or, Tesco, Asda, B&Q, ScrewFix, ........................ CubeCart
  5. I'm taking advice from BSmither reagrding having T&C's compulsary during the checkout process. It's proving to a bit tricky, but hopefully getting somewhere. Maybe you might want to keep an eye on that thread. Regarding a Privacy Policy, you can copy mine and take from it what you need. As a small company, we can't afford the services of a legal team to dot every I and cross every T, so I can't vouch for it's legality. https://www.beal.org.uk/privacy-policy.html However, this was handed to me by a GDPR practitioner, so i'm confident that it should satisfy. In the general discussion side of the forum is a thread about GDPR, it would be nice to get other peoples views and interpretations of GDPR..
  6. I'm confused. In content.checkout.confirm.php I see: {if $TERMS_CONDITIONS} <div><label for="reg_terms">&nbsp;</label><span><input type="checkbox" id="reg_terms" name="terms_agree" value="1" {$TERMS_CONDITIONS_CHECKED} /> <a href="{$TERMS_CONDITIONS}" target="_blank">{$LANG.account.register_terms_agree}</a></span></div> {/if} But when I view the page source I see no reference to terms other than the site links which appear at the bottom of the page. I don't see the checkbox anywhere.
  7. Probably in skins/foundation/templates/main.php Somewhere around line 50 find the command which triggers the search box, i'm using a custom search box, so mine is named differently. it's probably called {$SEARCH} or {$SEARCH BOX} move this to somewhere around line 80 ish, underneath where it says <div class="sidebar" id="sidebar_right"> I'll see if I can figure out how to change the size, this will probably be in a css file.
  8. You'll probably have to make these changes in the skin files. If you tell us which skin you use, i'm sure someone will point you in the right direction.
  9. keat

    gdpr

    I doubt very much that the ICO will do anything, there's so much woolyness and mis-interpretation that many companies will fail. We can only do what we can do to satisfy that we appear to be doing.
  10. $TERMS_CONDITIONS Origin: "Smarty object" Value "https://www.xxxxxxxx.co.uk/terms-conditions.html" $TERMS_CONDITIONS_CHECKED Origin: "Smarty object" Value "" Do I need to add anything to content.checkout.php to make it appear. All I have at the moment is the edit to cubecart.class
  11. I now no longer get the white screen. However, I don't see the t&C's checkbox either. PHP Version 7.0.30 by the way
  12. keat

    gdpr

    Debate So the mixed up interpretations continue. Today we received an email with a pdf attachment explaining GDPR and that the company requires our consent. It went along the lines.. "if we don't hear back from you, we will assume that we have your consent" I can argue, if you don't hear back from me, that we never received the communication, therefore you don't have my consent. Secondly, it was addressed to 'Dear Supplier' and then 'Dear Sir/Madam' Dear supplier or sir/madam is not personal identifiable data, so therefore in my eyes does not constitute GDPR protectional data.
  13. error log inside the cart shows [Exception] /home/xxxxxxx/public_html/classes/cubecart.class.php:910 - syntax error, unexpected ';', expecting ',' or ')' If I modify the end of the last line to : ''); I get this. [Exception] /home/xxxxxxxx/public_html/classes/cubecart.class.php:906 - Call to a member function assign() on string Although i don't understand PHP so it would be no surprise that i did wrong.
  14. I still get a blank screen.
  15. I tried adding the lines to cubecart.class.php, but the page seems to hang with just a white screen. No errors are produced in error.log. I then went up to the suggestion above that comment and added: {if true || $TERMS_CONDITIONS} <div class="right"><span id="error_terms_agree"><input type="checkbox" id="reg_terms" name="terms_agree" value="1" rel="error_terms_agree"><label for="reg_terms">{$LANG.account.register_terms_agree_link|replace:'%s':"{$STORE_URL}/friendly_path_to_t&c_doc.html"}</label></span></div> {/if} to content.checkout.php. I can now get the link to open T&C's, but can still proceed to checkout without having to check the agree button.
  16. Guys I could really do with this to comply with GDPR, so if anyone could shed any light how I would enforce T&C's with each order, i'd very much appreciate any help. At least until i can consider any CC software updates. Adding <div class="right"><span id="error_terms_agree"><input type="checkbox" id="reg_terms" name="terms_agree" value="1" {$TERMS_CONDITIONS_CHECKED} rel="error_terms_agree"><label for="reg_terms">{$LANG.account.register_terms_agree_link|replace:'%s':{$TERMS_CONDITIONS}}</label></span></div> to contecnt.checkout.php half does the job,. I just could do with some help making the checkbox enforceable and a link to my T&C's pages working. If this means encoding the actual URL it will suffice.
  17. I found this thread. If I add: {if $TERMS_CONDITIONS} <div class="right"><span id="error_terms_agree"><input type="checkbox" id="reg_terms" name="terms_agree" value="1" {$TERMS_CONDITIONS_CHECKED} rel="error_terms_agree"><label for="reg_terms">{$LANG.account.register_terms_agree_link|replace:'%s':{$TERMS_CONDITIONS}}</label></span></div> {/if} to content.checkout.php, nothing appears. I remove the two 'If statements, and now the box appears. However, I can proceed without checking the box and when I click on the hyperlink for T&C's it loops me back to the confirm page. www.latexglovesonline.co.uk
  18. Further to this, I received another email this morning stating that the test endpoints are now ready. However, the email also mentions: As well as removing support for older TLS ciphers, we need to increase the length of the key for ciphers that use Diffie-Hellman keys from 1,024 to 2,048 bits in order to ensure a higher level of cryptographic protection. Merchants will need to ensure their integrations can support this key length. Although we can monitor which TLS ciphers merchants are using, we have no way of knowing who will be able to support the increased DH key length so merchants are strongly advised to use our test endpoint to confirm they can support the increased key length before that time. On the 9th May 2018, during our regular maintenance window, we will broadcast for ONE HOUR using an increased Diffie-Hellman 2,048-bit key size. This will help us to identify merchants who are not compliant, and proactively allow us to notify you ahead of the full switch-over on 6th June. Is this going to affect the gateway module at all.
  19. Wil Do you have ftp access. or maybe Cpanel/Plesk file manager access. Take a look in the root of your store, make a note of the admin folder name and the adminxxx.php file name. Make sure that these are entered correctly in global.inc.php when these are confirmed correct in global.inc.php, try logging in to https://www.classicbm.com/admin_whatever-its-called.php I tried logging in to https://www.classicbm.com/admin_TSYdCZ.php and it's coming back a 404 error, which would indicate to me that admin_TSYdCZ.php does not exist.
  20. I don't have any other snippet on that web site.
  21. I already looked in there and it shows 'Binary - Do Not Edit' and then all I get is a browse button which wants to open a local file.
  22. 6.1.7 on both sites i tried.
  23. Could there be something missing from the php code ? If I add the code as it is, then code sort of becomes corrupted, the code area fills with alpha numerical data. Thinking it may be missing an end statement, I added } ?> to the end, and this then causes a white screen. Tried this on another site, and again, the data becomes corrupted when I make the save.
×
×
  • Create New...