Jump to content
Latest News: (loading..)

burt

Team
  • Content count

    13,078
  • Joined

  • Last visited

  • Days Won

    468

Everything posted by burt

  1. Posted this elsewhere, but makes sense to have in this thread; At what point does a Potential customer become a Customer? after they create an account? after they actually buy something? when they sign up to a mailing list? something else That's an interesting question. Maybe shopowners should have something in their T&C explaining at what point a person becomes a customer, that wouldn't harm anything to add it in, and maybe helpful in the future should you have to prove anything to anyone. Remember also that GDPR does not apply only to customers. It applies to ANYONE who interacts with your site, it is just that most shopowners direct people to agree to GDPR T&C etc at some point after the potential customer has browsed products etc. Whichever point you determine a potential becomes a Customer... you MUST STORE the exact T&C to which a Customer signed up, why; In the future, the customer can examine the precise T&C to which he/she signed up and if necessary withdraw his consent. To show the GDPR authority in your country the exact T&C to which the customer signed up, if the customer complains to that authority. Another thing to think about is "Guest Checkout" - how do you solve the problem of the buyer giving consent per GDPR? How do you record the data? What happens if a customer says "no, I won't give Consent" - how do you record it? You can't use their email address...you don't have a customer ID. What do you do?
  2. It's pretty simple, just use common sense. Common sense tells me I need consent to re-market. How do I get that consent? Perhaps a Tickbox on create_account might be enough, linked to acceptance of T&C. In your T&C page have a paragraph about re-marketing. At what point does a person become a Customer? after they create an account? after they actually buy something? when they sign up to a mailing list? something else That's an interesting question. Maybe shopowners should have something in their T&C explaining at what point a person becomes a customer, that wouldn't harm anything to add it in, and maybe helpful in the future should you have to prove anything to anyone. Remember also that GDPR does not apply only to customers. It applies to ANYONE who interacts with your site, it is just that most shopowners direct people to agree to GDPR T&C etc at some point after the potential customer has browsed products etc. Whichever point you determine a potential becomes a Customer... you MUST STORE the exact T&C to which a Customer signed up, why; In the future, the customer can examine the precise T&C to which he/she signed up and if necessary withdraw his consent. To show the GDPR authority in your country the exact T&C to which the customer signed up, if the customer complains to that authority.
  3. Totally do-able, it is exactly as @raiwa says. Gallery 10 6 Name 20 6 Model 30 3 Price 40 3 Attributes 50 6 Buy 60 3 Reviews 70 3 Description 80 6 You are constrained by the DEPTH of the Gallery, so place a minimum height on this using CSS which would be placed in user.css @media only screen and (min-width : 768px) { div.cm-pi-gallery { min-height: 1000px; } } Change the min-height on this to better reflect your needs. You will then also need to amend tpl_ files for product_info, at the very least; remove clearfix from reviews button tpl restyle price as it would look weird as a h* Prior to the extra tpl_ change for price, you would end up with something like: Of course, how this would look in XS...is debatable, and that is why you can micromanage the layout using those tpl_ files if you so wish. My system for these modules uses only the SM layer.... however, that micro-management is where things get really complicated really quickly and hence why I did not put that level of management into Core.
  4. @KarstenBoeer If you wish to post questions in the German language, in the future please post at: https://forums.oscommerce.com/clubs/6-german-community/ I have moved this thread into the German Club.
  5. burt

    Add line breaks to comments during checkout

    $comments .= $key . ': ' . $value . PHP_EOL;
  6. burt

    28d, 2018

    Coming later on Today a couple of minor bugfixes to a couple of modules (nothing important). GDPR Testimonials GDPR Testimonial Module In the latest core update I added the ability to join Testimonial to Client as it was identifiable data (but not linked), as it is identifiable the client must be able to perform certain actions! As it is now linked, it requires one of my special GDPR modules. This module displays the Testimonials that the Client has written and allows them to do two things; Anonymize it (the blue button) Delete it (the red button) And, of course, they can port this Data using the usual "port my data" mechanism. Enjoy!
  7. Third installment of the 28d Project. I missed last year for reasons, but this year it's back. I'm running it slightly differently to previous versions, as this time there will be no option to buy each days package - that was frustratingly difficult to manage - sorry. Instead there will be a very simple "buy now" price for everything, and that will go up in price as February goes by, therefore those who can buy earlier...pay less...and those who buy later...pay more. Hit the [Follow] button in the right hand corner of this page as I shall be updating this post as the days go by. Should anyone wish to pre-buy...thank you for your consideration and support. PM me and we can arrange it. Don't know what the 28d Project is? I make code available during February (each year, usually). This is code that I have created or updated and make available for an all-in price. Had a couple of questions by PM; Edge Compatible: Yes Gold Compatible: Yes(ish), you might need to update some files to the Edge version, I will point these out in the individual "readme" for each. Certainly nothing to be worried about! PHP7 Compatible: Yes Official osCommerce Compatible: No, sorry Core Code Changes: Will be kept to an absolute minimum, you guys know I hate to change Core and I know you guys hate Core Code Changes...but sometimes, it is, unfortunately, unavoidable. Progress: I have 21 things coded and ready for finalised checking. 1 thing is being live tested by a shop. 6 or 7 things more to write; ideas would be welcomed for small to medium things Thanks for all the PMs and Feedback so far!
  8. burt

    ipv6 Support

    In addition to the above, I learned something new today - IP addresses get shortened automatically, eg 127.0.0.1 is actually 127.000.000.001 So your first example 2a01:4f8:13b:12e0:0:0:0:2 gets shortened, less than your 25 limit, all good, can be found in the geolocate DB, is actually: 2a01:4f8:13b:12e0:0000:0000:0000:0002 The second example 2607:fea8:695f:ffb1:7d67: nothing there can be shortened, so is cut off at your 25 limit...
  9. burt

    ipv6 Support

    You may need to increase the database limit for the ip_address in whos_online table. Maybe to varchar(256), that should be more than enough. https://stackoverflow.com/questions/1076714/max-length-for-client-ip-address I think your second example is not the full ipv6 ip - it is cut off at X (25?) characters, hence why you cannot find it in any ip database.
  10. A number of deleted posts in this thread have been re-instated, lets people see the whole conversation.
  11. burt

    Forum Software Update (31st July 2018)

    Quirk on the react icons, they appear twice:
  12. burt

    Mailchimp App with 3.0API

    2.5 years ago was early adoption of v3 - and a lot of what was available in v2 was not available in v3. Some things in the documentation for v3 simply did not exist in the code or did not work. Today (or at least the last time I looked), the API does not include their roll-up of GDPR, which means the API is unusable for "Joe Average" shopowners who does not want to have to delve deep into code or does not want to spend money on a developer.
  13. Two questions there, that I can answer; I believe so. Frozen is frozen, like Gold was gold. It won't change, it's a point in time. There should be no other Forks discussed at this Forum, but I let that slide if the one who forked is actively moving osC forward If they are not doing much of anything other than loading it up or trying to split the community...links get removed. Yes. It'll take time as it is done on a small part-time basis. I thank you @Tsimi for understanding that the sale of my code allows me to give more time than I normally could and as more time is given, things move faster. Thanks!
  14. What you accuse me of, never happened, other than in your own misunderstanding. When you (or anyone) jump to a conclusion (not only about this, but many other things)...the conclusion is usually incorrect. But hey, I really want to see you do well in the Admin Project, so... Good Luck!
  15. The posts from the other day across two or three threads which I had to collate into one ""un pleased" post, where you basically shit on me, other users and osCommerce - all done in public - until I collated and moved into the team discussion area. Which you then deleted, along with hundreds of other posts as part of your "cleaning up". It leaves a bad taste in the mouth to be accused of something that I never did, then to see you performing the action that you accuse me of. The action itself, no problem, just the words from the other day is a problem for me.
  16. I have no PM from you other than the one where we were discussing your brother, weeks ago. There isn't a possibility that this can be a part of Frozen for two reasons; whitehat made it very clear that he wants nothing to do with anything I am working on, in his words: "I am 100% done with you" whitehat did not fork his Repo (it is clear that you do not understand what that means, so believe me when I say he has made it difficult to merge) Let us say no more on the matter, and please stop mentioning me with regards to working with others. These people themselves need to approach me to have a frank discussion as I need to know they are not going to bale out when things get tough.
  17. For clarity, it was not me who deleted your post. And I do not know to whom you sent a Beer and never got the courtesy of a thank you & reply?
  18. Thank You T. Appreciate those words, that means a lot.
  19. Unfortunately because you did not fork there isn't a way that the two repo's can easily be merged :-\
  20. The words I got from you just a few days ago, and now again this?!? Uncool. Good luck with this Project. And as for your comment @valquiria23 - there is at least one other active Team Member so stop stirring the pot please.
  21. burt

    Form verification within a Modal

    If you get stuck or find yourself going round in circles...I can put together a hard-coded (ie, quick and ugly) example... Just let me know.
  22. burt

    Form verification within a Modal

    OK...some pointers; in your .js bind the checking to the Submit of the Form, NOT the click of the Button - this will allow the HTML5 email checking to do its thing On submit, prevent the default action of the Form and also ajax Post the email address to a different file for it to be added to the database - this can also manipulate the modal to give a "success" message For now, forget about closing the modal... - if you close it you won't be able to easily see and understand what is going on Those pointers 1 and 2 should be enough to get you at least another few yards forward.
  23. From my side, assuming that you are directing this at me, whatever people think they see and know; there are no differences. wHiTeHaT wants to do his project, so he should do it. I suspect many shopowners shall be very glad to finally see a bootstrapped admin.
  24. There is (in the addons somewhere) a manual order maker. I am not sure how it works (or if it works)... But if that could be used, that could be a way out of the mess. So long as you have the customers details and the order details. A client of mine had the same problem on monday evening. I put it down to paypal being glitchy at the time, as orders prior and since have been recorded fine (both at paypal end and at her osc shop end). I spent a bit of time manually :-\ adding in the missing order directly in phpmyadmin for her to get it sorted.
×