Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

cienislaw

Members
  • Content Count

    46
  • Joined

  • Last visited

  • Days Won

    2

cienislaw last won the day on August 14

cienislaw had the most liked content!

Community Reputation

17 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. https://store.thirtybees.com/shop-modules/front-office/cookiebot there is nothing on the module page mentioning Prestashop in any version.
  2. there are modules/templates for that, so we could clean up those too.
  3. did you changed links pointing to dev site to normal site?
  4. non-square images are already allowed, but I assume you were thinking about images not following set ratio to fit them with padding? the hard rules implemented now are ok - you can't give a finger because ppl will ask for whole palm. yeah, image handling could be improved in a few ways. preprocessing for start, which will determine if image really needs resize/recompress. but for now there is a bunch of things to do first, so maybe later;-)
  5. image processing should be straight forward process. IMO WebP is the way to go, if we like it or not. it gives good quality/size ratio. I didn't look into compressor settings yet, but there are few which can help with file size beside quality setting accessible via BO. WebP can do lossy, can do lossless, it even can do transparency, so right preselection of settings to source image properties is a key to achieve good quality/size combo. ps. compression to size is ok when you do it one by one with visual confirmation of result, not for batch processing of hundreds of images.
  6. just my 10 cents - provide HQ images (JPEG 100 or PNG) and play with compression settings. yes, ideal scenario would be if there is a check if source image has a right size for example 1600px, then skip that one if possible (depends on compression format).
  7. but those are not warnings but errors - is there a solution to this? im trying to properly modify Niara theme and seeing a bunch of errors doesn't help the process. ok, I've educated myself and indeed those errors can be ignored (assuming that JS code in repo is working in 101%), but would be nice to have build process error and warning free (low priority).
  8. I have only default main category for CMS pages, which are used for informational purposes. And webpage with main category has only a list of links to those CMS pages without any useful info. Is there a quick way to dissable/hide this page?
  9. thirtybees Newsletter modules does only two things - collects subscribers emails and send them voucher code. nothing less, nothing more. if you want full 'newsletter' fuctionality ie. collect, create and send mailing, you need to invest in service as Mailchimp or Sendinblue (free plans exist) or dedicated module which does everything on site, but then you need also reliable e-mail server to send mailing (check your host parameters). There is something like phpList - selfhosted mailing solution, but getting it to work on level as paid services requires some work.
  10. there is no such option but if you really need it, you can always add it to the core/theme and share with community.
  11. any chance to see the working shop?;-)
  12. you have to change logic in module which provide table of products to display in frontend.
  13. I was playing with Zones (trying to add abroad delivery) and decided to add new zone for Poland only (by default its in Europe), and a few Europe X zones based on delivery prices. And strange error occurred - vistor was seeing prices without tax. After some digging and checking I found out it was cookie related - one customer and my self too had old cookies, which were forcing TB to view prices without tax. I should have a copy of the cookies on another machine, so I could do some digging but the bug should be easy to replicate. do something in store as visitor; add new Zone; move country from old Zone to new; get back to store and see how prices are displayed. It's quite a problem to explain it to a customer, so some kind of cookie invalidation should have place when even one country is move between Zones. As a backup I've added tax ex/incl labels form AdvancedEU module and changed frontoffice cookie lifetime to 1h from default 480h.
  14. there is another global free shipping switch in Preferences (the same menu as Carriers) - put 0 in both price and weight to disable it.
×
×
  • Create New...