Jump to content
Latest News: (loading..)

azpro

Members
  • Content count

    161
  • Joined

  • Last visited

  • Days Won

    4

azpro last won the day on October 5 2016

azpro had the most liked content!

1 Follower

Profile Information

  • Real Name
    Arjan
  • Gender
    Male
  • Location
    Amsterdam
  1. Quick and dirty fix because I did not look at the code here discussed - But probably you just need a clearfix div to separate button and roll-menu. So put before your roll-menu: <div class="clearfix"></div>
  2. Progress Update

    Just to clarify ... MIA means "Missing in Action" ... So nobody knows ...
  3. Did you get it from Github? Please read this thread :
  4. I hope you started with the latest community version 2.3.4.1 CE also known as FROZEN. You can find it here: https://github.com/gburton/Responsive-osCommerce Cheers!
  5. @raiwa @John W I was thinking about this. To me it seems this doesn't need Structered Data since the content / products of recently viewed is only visible for the website customer/visitor. Google or whatever bot should / could not "see" it ... Am I right? Thoughts?
  6. Couldn't that be invoked in an update function in the proposed cookie class? Everytime a new module with getCookieStuff is installed it could do a ONE-TIME check and then update database INSTALLED ... I think i is worth the effort since speed is essential
  7. PHP Version 5.5.9-1ubuntu4.24 Off course ... did not think of that! The opt-out build in cookieconsent3 - if you set Compliance type to "type": "opt-out" See https://cookieconsent.insites.com/documentation/disabling-cookies/
  8. @tgely Another thing ... the cookie of Cookieconsent https://cookieconsent.insites.com/download/ which is cookieconsent_status I want to set as strict ... but the code now only differs between Functional and Strict ... I would say this cookie must allways be set by a website visitor (deny/dismiss/allow) but he should not be able to delete - so it must be strict (??). Furthermore I would like to add the OPT-OUT function ... but I don't understand how to implement. That is to say .. the way it should be handled depends on the full functionality of you app.
  9. @tgely @wHiTeHaT Better aproach in my opinion! I don't like to extend / change the osc_template.php .... I would really prefer a separate Cookie class
  10. For var $_expiration = 365*24*60*60; I had to change it to below - otherwise cookie lifetime is not properly set: var $_expiration = 31536000; //365*24*60*60; // one year The cookie oscConsent is set as [\"True|ht_grid_list_view\"] If I read out cookie in Firefox - privacy it reads content as %5B%22True%7Cht_grid_list_view%22%5D Is that okay or is it a mixup of json_encode ?
  11. @tgely I have got it working - but in classes/osc_template.php line 23 gives an error: var $_expiration = 365*24*60*60; probably should be : var $_expiration = '365*24*60*60'; Did not yet test fully .. but I have the feeling there is a slowdown in pageload. Even when footer module cm_cookie_consent is DISABLED ... Is that possible? Furthermore ... For consistency reasons .. Wouldn't it be better to have a separate class file for the cookie adjustments now done in osc_template.php ?
  12. Really?? It is all blowing my mind this GDPR
  13. Thanks! I will give it a try .. But I think it needs wrapping up in a complete addon with documentation .... Maybe @frankl could help here.
×