Jump to content

Al Brookbanks

Staff
  • Posts

    6,638
  • Joined

  • Last visited

  • Days Won

    123

Everything posted by Al Brookbanks

  1. You should still get an SSL certificate for secure padlocked pages. If your web hosting company are not greedy opportunists it should be free. LetsEncrypt: https://letsencrypt.org
  2. They are not entered on your page. That's the beauty of Stripe. They look like they are but if you look at the source code you'll see they are not self hosted input fields. On those grounds its just as secure.
  3. I'll have to make some tests around addresses when I can. The PayPal integration is certified by PayPal UK. They asked us to remove the PayPal payment method from the list. If you want it to show the PayPal "mark" then you can edit the modules/plugins/PayPal_Pro/hooks/class.cubecart.display_gateways.php file. Remove the conditions like; if(!in_array($_GET['_a'], array('basket', 'checkout', 'confirm'))) {
  4. 6.2 has the ability to make state optional or disabled which will improve the checkout experience for Express Checkout. I'd suggest using Express Checkout instead of PayPal Standard. Please note that PayPal Express Checkout will not return a billing address unless they have specifically enabled this on your account. This is not a coding fault in CubeCart. I have spoken to the guys at PayPal about this some months ago. https://developer.paypal.com/docs/classic/api/merchant/GetExpressCheckoutDetails_API_Operation_NVP/#address-type-fields
  5. We are excited announce the release of CubeCart 6.2 which sports a number of fabulous new features. Maintenance release 6.1.15 is also available for those who are not ready or are not keen to make use of the new features. Massive thanks to all those who have tested and reported any 6.2 bugs. What's New in 6.2? Incremental order numbers (with dynamic prefix/suffix). #636 Tools to help with GDPR. #1892, #354 * Automatically minified and compressed HTML, CSS & JS. #1905 * Checkout state/county can be required, optional or disabled. #1870 * Invoice template editor tool. #1904 Caching improvements. #1536 Product category added to Google Analytics for eCommerce. #1859 * Order summary to show "guide" currency used. #1913 Ability to show hide site document titles. #1907 * Email log to show fail reason. #1899 Email configuration test to work prior to save. #1894 reCaptcha added to newsletter signup. #1891 * Colours added to admin control panel order statuses. #1888 Introduction of "Safe Mode". #892 Product dimensions (width, height & depth). #828 * Changed admin URL emailed on setup (if changed). #1314 "Continue Shopping" added to cart at all times. #1381 * Search redirect to product detail page for single result. #1427 Auto delete captured card details when order status changes from pending. #1886 Upgrade Instructions: https://support.cubecart.com/Knowledgebase/Article/View/228/43/how-do-i-upgrade-from-cubecart-v6-to-latest-v6 Download: CubeCart-6.2.0.zip Download: CubeCart-6.1.15.zip 6.2 Release Notes - Please Read!! * These features will require skin updates if you do not use the default "Foundation" skin from the 6.2 release. This release has a clear cache on demand tool which significantly optimises the caching system and lowers server load. This means that inventory or configuration changes made in the admin control panel will not be reflected on the front end of the store until the "Clear Cache" button is clicked. This can be found at the top right hand side of every page of the admin control panel. We very much appreciate that this may be seen as an unwelcome new feature but the technical significance is worthy. Unless you have a critical change to make we suggest clearing the cache habitually at the end of each admin session. If the cache is not cleared it may take up to 24 hours for your changes to show. To help comply with GDPR CubeCart 6.2 now has "double opt-in" for email marketing signup and a tool to create a report of all customer data based on an email address. This can be found in the "Customer" section of the admin control panel under the "GDPR Report" tab. A customer can be "forgotten" by deleting their account, newsletter subscription, review(s) and any orders they may have placed. Please note that it may be a legal obligation to keep their order data on file if you have an existing financial contract. The GDPR report can be disclosed to your customer printed or saved as a PDF and/or used to help remove their data from the system. To be GDPR compliant please be sure to have a suitable privacy policy which should contain other such information such as what each site cookie does. Further information and support may be available from your local "Information Commissioner" such as the ICO (in the UK). GDPR is still a very confused and misunderstood subject of which there is no one solution for every business. We will prioritise further development to help compliance based on your feedback if merchants feel they still need extra tools.
  6. The same rules will apply. I'd recommend seeking assistance from your local data protection officer or lawyers. I expect the government have a department specifically for this. In the UK it's called ICO. Information commissioner office https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/
  7. Every business is different and we are not able to make a one fit solution for all. There are some tools to help with GDPR coming out in 6.2 but you'll need to look at your business as a whole. The ICO in the UK is the best resource for UK organisations.
  8. We now have the first released candidate for CubeCart 6.2.0. Please refer to the original announcement for more detailed information about 6.2. Many thanks to all those who have tested the 6.2 branch of CubeCart and reported any issues. Unless any serious bugs are found in RC1 then 6.2.0 final will be available on Tuesday 24th April. Download: CubeCart-6.2.0-rc1.zip Download: CubeCart-6.2.0-rc2.zip (Release candidate 2)
  9. Yup... https://foundation.zurb.com/sites/docs/v/5.5.3/components/reveal.html
  10. It's inclusive of the managed support plans. https://www.cubecart.com/technical-support
  11. Yes we can do that for you and make sure the PHP configuration is compatible (ZipArchive, mbstring etc)... Done this many, many, many times. Look forward to working with you soon.
  12. I think its quite a convoluted way. If we did this for you on the managed support plan we would; Take a full backup. "Diff" against the same version to pull out an exact report of code changes. Apply these code changes to 6.2.14. Upgrade using the customised package. I've done this many times. It's very time consuming but we do it at no extra cost to a regular upgrade. 6.0.6 has security holes so hopefully they have been patched. If not then you need to check that it hasn't been hacked. If it has then it needs to be cleansed. There is a support article about how to do that. A classic hacked store may be running code snippets you don't know about. These can be viewed in the "Manage Hooks" section in the "Code Snippets" tab.
  13. Just remove any insecure absolute URL's from source code. Your browser inspector tool will help but there are also online tools like https://www.whynopadlock.com/
  14. Server update maybe? I don't think CubeCart will change anything. Saying that it may try to change the chmod value of the images/source folder.
  15. So you should be able to do this then. I don't know if this would work but you could try creating a new linux user with its own group. e.g. imgsrc:imgsrc with a home directory at /home/imgsrc Then move all the images there and add each of your cPanel accounts to the "imgsrc" group and give all the account a symlink form their /home/{user}/public_html/images/source folder to /home/imgsrc. You might be able to take this further and symlink the images/cache folder to save more disk space. This is all theory and may not work at all but sounds doable.
  16. Totally understand how you can't duplicate 40,000 images. I'm sure it can be done with specific group memberships but you probably need your own VPS.
  17. Makes sense. Can't say I blame them. Stuck between a rock and a hard place here... I suppose the only solution is to put all sites on one cPanel account if you want to use symlinks. However if one gets hacked they all get hacked. Maybe you do need to mirror or rsync the images/source folder. I don't blame the hosting company for making this change. It's best for the greater good.
  18. Nothing wrong with the release.... instructions here:
  19. Because the skin isn't compatible I expect. Does it work with default foundation skin? If so you haven't updated the skin properly.
  20. btw site updated as normal That's not relevant. It's all skin level code.
  21. Really? Are you sure you have uploaded to the correct place?
  22. It's trying to load reCaptcha v1. Have you replaced/uploaded the required files? It doesn't look like it.
  23. I haven't seen any other stores with problems from the latest update. Nothing has actually changed our end. Google has enforced the changes not us. Can you turn it on?
  24. This is why you need to be your own host. Maybe they have jailed the cPanel accounts or made security changes. To be fair to them symlinking across accounts could be dangerous.
×
×
  • Create New...