Jump to content
Latest News: (loading..)

burt

Team
  • Content count

    13,092
  • Joined

  • Last visited

  • Days Won

    477

Everything posted by burt

  1. Here's what I want to get done to set the Community Version to a "Final" release; 1a. Modularisation of index COMPLETE Title Standardise Module Name and Template Name (each) 1b. Modularisation of index_nested COMPLETE Title Standardise Module Name and Template Name (each) 1c. Modularisation of index_products COMPLETE @BrockleyJohn has coded, thank you Title Description Products 2. Modularisation of product_info COMPLETE Strip Schema Schema Buttons Date Info Options Description Gallery Price Name Model Not Found Message Standardise Module Name and Template Name (each) 3. Bootstrap v4 CANCELLED Updating full shopside to BSv4 4. php7.0 COMPLETE Updating full shopside and full adminside to be 7.0 compliant. 5. getContent calls DISCUSSION Discussion needed 6. Hook calls COMPLETE @raiwa has coded, thank you Auto Register Hook for each page What I don't have plans for, so will not happen; Everything else Why go "Final" Too many shopowners and developers wanting a fixed release; almost all feedback tells me rolling updates are not welcome. After "Final" No further changes will be made. Date for "Final" I was hoping to get it done by the end of this Month, but that is not going to happen. Sorry Folks, it'll be as and when I have time.
  2. Dead? It's at a place I am mostly happy with; php7, a bit modular, responsive etc. Good Luck to all Shopowners.
  3. MATC

    I'd say in two places; create_account.php a. records the customer signed up on X date at X time and that he says he has read your Terms/Privacy policies b. It also appears that best practice is to store the exact terms/privacy that the client signed up to. checkout_confirmation.php a. records the customer giving her permission for you to possibly divulge some of her details to external companies - payment processor, mail delivery, perhaps other things ? For #2 I say checkout_confirmation as that is the last page in the checkout procedure prior to the order being placed - I think we all agree that consent must come before the order is placed. I place it on that page also because by the time this page is reached...buyer has already made the buying decision so 1 extra tickbox here is not a deal breaker..
  4. Thank you to all for testing. This code is now in 2341CE (aka Frozen).
  5. Any responsive site now has another advantage over a non-responsive site.
  6. @14steve14 Obviously with a backup done first!! This first query is the "Master Blaster"... delete from customers where customers_id not in (select customers_id from orders) and customers_newsletter = 0 that will remove all customers that have never made an order AND are not a subscriber. You then need to clean out other tables, and we know that any ID that does not exist in the customers table, should not exist anywhere else; delete from action_recorder where user_id NOT IN (select customers_id from customers); delete from address_book where customers_id NOT IN (select customers_id from customers); delete from customers_basket where customers_id NOT IN (select customers_id from customers); delete from customers_basket_attributes where customers_id NOT IN (select customers_id from customers); delete from customers_info where customers_info_id NOT IN (select customers_id from customers); delete from products_notifications where customers_id NOT IN (select customers_id from customers); delete from whos_online where customer_id NOT IN (select customers_id from customers); delete from reviews where customer_id NOT IN (select customers_id from customers); delete from reviews_description where reviews_id NOT IN (select reviews_id from reviews); And that should do it. But all of this is UNTESTED...
  7. Good catch, yes I think it does. I'm still going to remove it though, one less thing to load each page.
  8. Thank you all for testing. Another bonus to this new system is that the page loads faster as it does not need to pull in this file; https://github.com/gburton/Responsive-osCommerce/blob/master/ext/jquery/cookie.js This is only a small file, admittedly. But it is an extra request that has to be performed. 1 less request = faster page.
  9. The main reason I would like to use this new code is to dump this Cookie that the grid_list uses. If we can dump that Cookie, shopowners may no longer have to ask people to accept Cookies as all the Cookies in the Edge download are then absolutely required for it to perform its primary function => allow shoppers to buy your stuff. Please feel free to have your say on that.
  10. http://template.me.uk/234bs3/products_new.php or http://template.me.uk/234bs3/index.php?cPath=3_10
  11. http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm EU Legislation On Cookies (I have highlighted the relevant parts for osCommerce, by *my* understanding); BLAH BLAH ... some cookies are exempt from this requirement. Consent is not required if the cookie is: used for the sole purpose of carrying out the transmission of a communication, and strictly necessary in order for the provider of an information society service explicitly required by the user to provide that service. Cookies clearly exempt from consent according to the EU advisory body on data protection include; user‑input cookies (session-id) such as first‑party cookies to keep track of the user's input when filling online forms, shopping carts, etc., for the duration of a session or persistent cookies limited to a few hours in some cases authentication cookies, to identify the user once he has logged in, for the duration of a session user‑centric security cookies, used to detect authentication abuses, for a limited persistent duration multimedia content player cookies, used to store technical data to play back video or audio content, for the duration of a session load‑balancing cookies, for the duration of session user‑interface customisation cookies such as language or font preferences, for the duration of a session (or slightly longer) third‑party social plug‑in content‑sharing cookies, for logged‑in members of a social network. So, we can clearly (by *my* understanding) not have to do anything about cookie acceptance for; please_accept_for_session aka "cookie test" oscSid As both of these Cookies; do not include any personal data are absolutely required by the software for the software to function Anyone else like to add more thoughts? Other NOT ESSENTIAL Cookies If shopowner has other cookies on board....that DO have personal info (eg Analytics passing IP Address) or ARE not required by the software to perform its function (sell stuff)...then shopowner must get permission for these cookies. There is ONE cookie in Edge that shopowner MUST get permission for as it is a Cookie that is useless to the softwares primary function: the cookie in the ht_grid_list module. If I can get rid of that Cookie, we are good to go (in my opinion).
  12. That has always been the case (very brief show of list) if grid is selected, even with the old list/grid thing. No ?
  13. Price should be set to $99999999999999.00 in this case. Where is the problem? So long as you check that the input here is a number, you are good to go; filter_var($input, FILTER_VALIDATE_FLOAT) Note that this is good for "0" prices as well, and should also allow fractional prices; 9.99 You maybe allowing fractional prices as it is much easier to spend 9.99 than it is to spend 10 (mentally).
  14. Example site of (more or less) 2.3.4 with Bootstrap 3. http://template.me.uk/234bs3/index.php Please point out any areas that you feel need attention. Thanks Gold Download: https://github.com/gburton/osCommerce-234-bootstrap/archive/v2.3.4-GOLD.zip EDGE: Gold + Extra Commits such as bugfixes: https://github.com/gburton/osCommerce-234-bootstrap/archive/master.zip
  15. URLs for SEO have been irrelevant for a long time. To suggest that this code goes into Edge...make me raise my eyebrow.
  16. There maybe just a couple more tiny changes, but certainly I am very close to declaring "Frozen". It won't be Final as I wasn't able to get to a place where I am happy to state "Final". But after I declare Frozen, there will be nothing more. Frozen is, in effect, Final. It is time to "Let It Go".
  17. Are we sure about this as I am receiving 4/5 emails per day from different sites (including those I have opted out of marketing).
  18. 28d, 2018

    Here is the next piece of the GDPR jigsaw puzzle. If you add up Article 20 and Recital 68...you (shopowner) have to give your customers a way to download their data. Good luck doing that - what a timesink - you are going to have to collate all of the customers data, create a file, tell them where it is, help them to download it etc. Bah, let's do all that automatically. Port My Data Module Clicking the Button allows the customer to download all of their data. Admin Side. Just turn it on. Once I get it fully tested in a live scenario, it'll go out to all and certainly prior to the 25th.
  19. Remove all not-essential Cookies from osCommerce. How many not-essential cookies are there ? If the shopowner then wants to use other not-essential cookies (eg Analytics), let the Analytics coders take care of it.
  20. Split Topic so that it does not get buried and you have a place to continue getting help away from the main thread.
  21. Disappointing to hear that some Developers are still not supportive. I can guess who the one was who said "would not use it as 2.3 has everything required"
  22. Time to fight back?
×