Jump to content
Latest News: (loading..)


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by 14steve14

  1. On the 25th May 2018 the updated General Data Protection Regulations comes into force. Well who knew anything about that. It would appear that the EU has or is about to change the way that people collect and store others data. This apparently supersedes the Data Protection Act in the UK. It has also been mentioned that when we leave the EU we will still need to comply with the regulations as the EU has made it worldwide somehow. Has any store owner seen a sensible easy to understand website that explains how this may affect store owners, or like me have you never heard about this until now.
  2. can oscommerce do digital downloads?

    I was told a long time ago that SDS was no longer needed. The hole that was there had been closed apparently. I didnt use any of the additional features such as group downloads so wasnt too bothered by that. I have never had any problems with the BS version as far as I am aware.
  3. Updated Stripe payment module

    I use Stripe as a payment method on my site and notice that the payment module itself has not been updated since 2014. The module works fine as it is so there is nothing to worry about. Stripe have updated their API recently and I was wondering if oscommerce was ever going to update this module.
  4. GDPR modules Thinking about GDPR some more and looking at some of the modules Gary has created, I was thinking about the contact us form. Should there be a box warning or consent check box on that page as the name, email and possibly phone number could be kept for future contact. The same sort of thing with the product notification page. Not too sure both pages have been set up to allow modules to be added to them, but should something be done just to cover business owners.
  5. Updated Stripe payment module

    You may be better off starting a new topic rather than asking a question that is not related to the original post.
  6. This may be in the wrong place, if so hopefully someone will move it. I have a shop with over 4000 products listed. Some of those products are now discontinued and wont be replaced. Some of them have been on the site for years, and may have links to them in the search engines. Should I delete them off the site and forget all about it, or should I do something else. Some of them also have an equivalent item from another supplier. My thoughts are to 1. Manually keep the product pages, but to put a notice at the top of the page that the product is no longer stocked. Then direct the customer to click a button on the page that will take them to the main or sub category that the products were in. That button is already on product pages. 2. Create a redirect somehow that will redirect any customer to the replacement items of the main category. My thoughts are that this may cause confusion unless there is a message as to why the redirection. 3. Move all the discontinued products to their own discontinued category, set the stock levels to zero, show the product and remove the add to cart button. My store checks stock and removes out of stock items from the site until they are back in stock. (May be this should be changed to). 4. Just remove the product and forget all about it. What do others do, or what do others suggest their clients do. Are there any good addons available. I had a look and there are some that will show a product as discontinued but all need core code changes which I dont really want to do. May be I should have thought of this before Gary finished his 28 days of code.
  7. What Gary has coded allows the store owner to chose a similar product from another manufacturer and it puts the link in to a button in the discontinued warning message. If the customer reads it he can click the link and will see the recommended product. There is also the usual cross sells on the product that may interest the customer. If a product is just deleted I take it Google will eventually stop trying to look for it, but what about deleting the product and SEO. Is that affected. When a product goes out of stock and is no longer visible Google records it as a 404 or something and that gets corrected when the item is back in stock. If a customer searches in Google and clicks on a link that goes nowhere it really annoys, but the same would happen if the product was removed and still searchable in Google. I am also thinking of creating a new discontinued category that is not visable on the site but will still allow products to kept there. Its funny how everyone has a different opinion and there seems to be nothing that is the right way to do it. Its the same with a quick search on Google. So many different ways, but nothing 100% positive and correct. Google says keep them on the site.
  8. Redirects with a message to say something that can be changed would be great. A way of creating a redirect sounds really easy to. After looking at some of the other addons, this all seems too simple.
  9. I sort of hoped that you would come up with something. You seem to make everything sound simple. I recently stopped selling a range of tools by one supplier and this sort of got me to thinking about all those 404s being reported in webmaster tools or what ever its called today. A search on line came up with lots of ideas, but nothing really definite, hence my question. I currently have your 'out of stock' module, that I have installed on the site, but have not got turned on. I also have your 'View complete range' button on the product pages so something could be done with what I have, but it would be nice to have something that works a lot better. On you this years 28 days of code I didnt seem to receive a copy of the files for bonus day two. Could you send another copy. Cheers.
  10. I had so many problems with customers and recaptcha, this is what I did. Not had a complaint since and really easy to code.
  11. Why not add a module that would allow people to sign up to your newletter rather than keep the information of someone who does not want you to have it, or they would use a proper checkout, where the option is available.
  12. If you like the template on that page you linked to, buy it and support @burt and the on going progress of the BS version.
  13. I bought a house off plan once and that was a great bargain. I did the same with the 28days of code this year. I dont spend so long on these forums these days, and thought it would be a great way to support the only truly good version of oscommerce. I was thinking of becoming a lifelong ambassador of oscomerce but didnt think it value for money as nothing is happening with the official version. I do still use osc and am planning an upgrade of my current BS store to the latest version, but now may leave it until its changed BS versions. We will have to wait and see. Garys code is always good, and I have never had any serious problems with any I have used or had Gary code specially.
  14. From the webinar I took part in, it seems that you need to get explicit consent to store the data. When getting that consent you have to link to your privacy policy which should detail what you will do with that data once you have it, and how you will protect it. You don't need to ask for consent every time as they have already agreed to how you use it. One idea that was agreed that could eliminate some confusion for customers is to have pop up boxes when a customers clicks on say the email box when creating an account with a short bit of text as to why you need to give that information.The box would then disappear when they start typing assuming that they read it. What was stressed as being very important was storing the date that consent was given, which oscommerce could do as it records the date that the account was created. As long as there is a checkbox on that page then all should be fine. There will be a lot more confusion to come yet. It will be good to see what some of the larger websites do.
  15. Gary. If you emailed every one of them and they all asked for proof of your identity before they will let you know you would regret contacting them all. It would also waste your time.
  16. @MrPhil its not a case of just moving to the US or somewhere else. It affects everyone that sells to customers in the EU. Moving to the states means you would still need to comply, though how it will be policed and enforced I have no idea. Gary beat me to it. Its another EU fudge up if you ask me. I can see what they are meaning to do, but in true EU fashion they make it too complicated. Just including data that has already been collected made it almost unworkable. If I have to get confirmation from all my customers before I can once again store their data, I will be spending so much time deleting stuff, that nothing else will be done. @ArtcoInc As Gary says that will need to be mentioned in the privacy policy for the site.
  17. You need to let your customers know that you pass on their information to outside sources and need their permission to do so. So not only should it be in your privacy policy, you will also need a tickbox to confirm that you can share it. On the create account page you will also need a tickboc to say that a customers has read and understood not only your t&cs but also the privacy policy. Or thats how I read the regulations.
  18. There is an EU site all about these regulations here https://www.eugdpr.org/eugdpr.org.html. Have a read, there is a lot to take in. GDPR has actually been in place for almost 2 years now, its only now that the final time limit to implement it that its come to people attention. Remember that its up to everyone as a business to find out about law changes that apply to their business. The hardest part I think to comply with will be to make sure that the person that is asking to have their data removed, is actually the person the data is about. I have been told that one form of photo ID and a utility bill to prove the address should be enough. I cant see many people that will like sending that to businesses. Which is why I believe that gary's idea of a page to see what data peoplea re keeping is a good idea. Let people delete their own data as they should be the only person that should know the password required to get to the data.
  19. GDPR is more about what you do with peoples personal data. You have to tell people why you need their data and what you will do with the data. As I see it a guest checkout can be used as long as you let people know what of their data you will keep and why. If you dont keep and store any of their data just let them know that you will only keep info for invoicing and tax reasons. Saying that I may be totally wrong but may be it should be looked into. I would
  20. Hasnt Gary @burt just released something like this in his 28 days of code.
  21. Progress Update

    Two months have passed since the initial posting. Is there any more news as it seems to have gone quiet again.
  22. Whilst it may not be what you are looking for but Google Analytics have lots of information including things like browser and operating system. Hopefully you have agged the code to your site already. If not you should.
  23. If you feel that transferring your data from one version to the other is too complicated, then pay someone to do it. Thats what I did and it was no where near as expensive as I thought it would be. It was also done quickly so the store was not down for long.
  24. Upgrading osCommerce 2.2 RC2a to PHP 5.6

    Its up to you what version you use. Do you want something that is responsive and has new addons being made for it, or do you want something that is old fashioned and very few new addons being made for. If you want modern use the community bootstrap version from Github. If you want old fashioned use the official outdated version available from here. In my view the decision is really easy and something should be done to remove the confusion you are having. Its a shame that those in charge seem to make promises and do nothing which is frustrating, but its their bat and their ball and they can do what they like.
  25. I took part in my webinar on Friday and here are some of the main points that were raised. Apart from what has already been mentioned by some, the main points worthy of getting a mention here are:- 1. You need to keep info about when someone gives consent. Things like the date will suffice, so that if questioned you can show when the consent was given. 2. Apart from usual personal data that everyone considered, there is also things like forum nicknames, facebook and twitter names, which are all considered personal identifiable data. 3. Have to remove data when asked and can no longer charge to give customer all their info when asked under subject data requests. Days given to produce this information have also beed reduced. 4. The most surprising one, and the one that may be the hardest to sort out. Any personal identifying data already collected also has to comply. 5. There was some suggestion that some sites are already using tooltip type features when customers fill out any identity data on web forms. So when filling out say the email address on the account creation page, a tooltip pops us and explains why the information is needed. 6. A rewrite of most terms and conditions, privacy policies and cookie policies are needed to account for the new rules and regulations. 7. Agreement to terms and conditions, and also privacy policy should be given somewhere on the site most suggested when creating an account. If you use a guest checkout you need to do similar. 8. You also have to let people know what information you will keep even if asked to remove all data as some has to be kept for legal reasons like tax, accounting and VAT, but once the time limit is up on these you must delete the data. So deleting something like invoice or VAT records after 6 years if you had been asked to delete all personal data for a customer. 9. Should you find out about a data breach not only do you have to inform the ICO, you also have to inform all of your customers whose data you are keeping. Some large UK companies have already been find in accordance to older legislation after a data breach because they had not immediately informed their customers whose data was affected. Those fines will be increased in the future. Most of this has been in British law for a while now, but everyone has until 25th May to fully comply. There are loads of good videos on youtube to watch if people want to. This apparently is only the beginning of a set of major changes that will take place over the next year or so, but some may be changed due to Brexit. Its being done to bring the same features, rules and regulation to all EU countries and anyone that collects any data about any EU citizen.