vallka

Thank you very much for this, datakick, this is exactly what I wanted to hear. I'll put this fix in my (from now on called "NiaraGel") theme, hope you'll do the same :)

This is exactly what I wanted to say. Fixing one bug has introduced yet another bug, what is absolutely normal in any software development. This new-introduced bug needs to be fixed in its turn, it's a normal working process. BTW again. In my live Prestashop-1.7 based shop I'm using a free service named https://imagekit.io/ It takes ALL the headache of managing various sizes and formats of images and even free you from saving them on your system. I like it very much. Didn't actually measure the performance, seems to be quite ok. Anyone interested? :)

Of course it is very easy to fix on a local base, of course I have change the name of the theme immediately. Just wanted to point you to a bug in your product, it's very easy to fix if you know where the name is generated. You can replace the space with _ as already implemented, as I understand, in image file names. Or just use theme folder name instead of name here - chances are much less likely that anyone will use space in linux system directory name. And BTW, working with Prestashop before, I do not remember that theme name has been use in these thumbnails names, just filenames with various suffixes... so probably this is a bug added by ThirtyBees

I made a copy of "Niara" theme and name it... "Niara Gel" (with a space). Regenerated images for products (didn't try anything else) include Theme Name, and the space inside the name has not be replaced with "_" or anything else. Thus srcset attributes became invalid (with space inside) and images are not showing on the homepage

I personally fear node.js and trying to avoid using it at all costs. The alternative is a command-line 'sass' tool, advised by ChatGPT: >The simplest Sass compiler is likely the command-line tool called "sass." It can be installed via the command line and is used to convert Sass files (with the .sass or .scss file extension) to CSS files. For example, to convert a file called "styles.scss" to "styles.css", you would run the command "sass styles.scss styles.css". It is also possible to use it in watch mode to automatically update the css file whenever the sass file changes. >You can use the --output or -o option to specify the directory where the CSS files should be generated. For example, if you want to output the CSS files to a directory called "css" that is located in the parent directory of your Sass files, you can use the following command: >sass --output ../css input.scss:output.css This helped me a lot! Thanks ChatGPT! And there is even better solution (as for myself) Live Sass Compiler for VSCode: https://marketplace.visualstudio.com/items?itemName=ritwickdey.live-sass Fortunately for me, TB do not mess up with putting all javascripts together, so no reason to worry about them. They just work as they are :) Not as in PS1.7

It doesn't matter for me, I did it my own way.... A way better I think 🙂 https://www.vallka.com/blog/prestashop-and-imagekit/ Any comments on my implementation? This one should be easily repeated on TB... PS There are a lot of things Prestashop doesn't support..(yet or for good) Bulk actions on Products in BO, for example... We badly badly needed this as our shop contains hundreds of similar products. I did it my own way, I like my implementation. Unfortunately for others the backend is written on Django as I started to hate PHP after a few innovations some years ago, namely Composer and other related stuff... 🙂

Yes, I'm planning to do this sooner or later. Apparently the task won't be easy (I mean migrating all or some of our custom stuff), but worth trying Thank you for your reply.

Hi everybody here. Just recently discovered TB... and got such a deja vu... We have migrated our PS website from 1.6 to 1.7 in 2018 and it was such a pain and disappointment... But we have survived. And at that time I really had the idea to fork PS and start my own version based oh PS 1.6.... never happened of cause, but you did it :) Congrats! So now I'm aware of TB and could it be a good idea to migrate 'back" from PS 1.7.8.2? I'm an experienced developer, now I know a lot of PS details, fixed a few bugs here and there... Our main problem is - yes, you guess it - it is impossible to get anything from PS team. All my requests were un-answered, all my fixes and correction rejected (well, apart from a very little one (https://github.com/PrestaShop/productcomments/pull/124) Unresolved issues are (some of them I have fixed for myself using overrides): Impossible to use mobile_detect in module templates (Front office) (ok in theme templates but doesn't work in module templates (https://github.com/PrestaShop/PrestaShop/issues/21661)) Problems with PayPal and Laybuy in Safari (and most probably elsewhere) due to the old bug in Safari browser with cookie header "SameSite" Inconsistent calculation if %% discounts in orders. It has radically changed from PS 1.6 to 1.7 - and it causes severe problems with some payment providers like Klarna or Laybuy (https://dev.to/vallka/laybuy-against-prestashop-193l) - these payment modules are not aware of the change and simply refuse to work with %% discounts! For more then 3 years now!!! Same or similar issues with discount figures and delivery costs in invoices, the numbers are still inconsistent in some cases Some bugs are never fixed in payment modules like Stripe and Klarna for years. These modules are not developed by PS so I don't even know who to address these... Multiple bugs in multi-store implementation, never fixed. In fact, I decided to use two separate sites - it's better. I think the multi-store feature is not worth using, it is inconsistent and often misleading Really useless statistics. I ended up writing my own statistics using Python, pandas, Plotly, and Django. Inconsistent tax rules (or I still cannot figure out how to use this feature?) Extremely mobile-un-friendly design of both front and back office, and really difficult to do anything with it (partly due to issue 1) (and just to mention here - such a mess of using Smarty/Symfony/Twig/whatever templating systems... never know where to look for a particular template, especially in BO) Overall bad design on database level... Just to mention duplicated data in ps_product and ps_product_shop and similar pairs of tables. Maybe repeating myself, but IMHO multi-store functionality simply cannot be used in the form it is designed now. But even worse - if I don't use multi-store, the data are still duplicated!!! In general, bugs come and go, go and come back :) never know what to expect when you are upgrading PS. ... and so on... Is ThirtyBees better than PS at least in some of these issues? Is it worth considering? And I would gladly participate in core or module development myself, if allowed :) Thank you for reading :) Valentine aka "vallka" https://www.vallka.com/ https://www.gellifique.co.uk/en/ https://www.gellifique.eu/es/