the.rampage.rado

Please, update your shop to the latest version. If this does not solve the issue you should find some access logs, investigate if something is changed and gives access to somebody, etc. As a start - use code updater to compare against 1.4 official and check every file it finds that is different.

Hope this helps: https://github.com/thirtybees/thirtybees/pull/2132

It would be perfect, but it needs a lot of work.

Thank you for the detailed explanation, Petr! I did not see that the old behaviour is moved in the old pack. I will test it now. You said you fixed the pack not depleting the product quantity bug when configured, right? Regarding the second approach, I think I get it now - we select first the attributes in the said combination and then we configure the applicable products for the said combination. Adding them one by one. Then add second combination, and repeat. I will experiment with it. For now one bug I see with the old behaviour (normal pack and virtual attribute) is that it does not calculate the available quantity for the pack based on the product availability: Also, do we consider if the product is 0 (or has negative stock due to previous preorders) but is WOO: Allow orders - does the pack treat this as an orderable state for the pack also?

Did you try the module and the options it gives you? In general if you migrated from Warehouse you will see that Niara is far less configurable.

Could somebody that have already updated or tested the new implementation give me some guidance on how to use the new feature? The old implementation was quite intuitive. I can't understand how to implement the new approach. I have to select Packs with combinations, don't save and directly go to Combinations -> New combination and add my products, but then what? In the same time I have to add attributes, but how? Quite unintuitive. My use case is packs of products with combinations, only 1 product per combination, but with sizes. Like 5x or 10x balls packs. Later, I would like to use it to make packs of sporting kits (shirt and pants) - with 2 attributes - color and size. But how? I even tried asking the bot - it was unable to give me detailed description I can follow... 😞

You got a PM.

Be extra careful when removing image formats here as every theme creates what is needed during install. Regarding speeding up image generation - if you're generating your images during manual product creation the only way is to increase the speed of your server (buy better VPS/server). If you are annoyed that image creation times out/is slow during product import - simply don't create the thumbnails during the import but later in a dedicated tab while you do other work. The image section got nice rewrite by @wakabayashi but in the end it has to regenerate the files. Also - don't use jpg, it's 2026. Switch at least to webp, avif is even better if your server/php version supports it. BEFORE you switch the image format and regenerate all images - make sure that your theme can work with the new formats. Take inspiration from Niara and see how you can pass the file extension dynamically. Backup, make the change, then regenerate all thumbnails (Images -> Reset status -> Regenerate all). This will not speed up your generation time but will speed your FO performance and speed score if you approach the quality conservatively.

I basically told Codex to use this and that local repo of Warehouse, upgrade FA to 7.2, use the shims and not make any changes to the actual usage of the font in the theme so I can check if the shim layer works. After I saw that the new icons are loading with the old code calling them (FA3 and 4) I asked it to inspect all the theme files and module and swap the code for the new formatting. The old font files light stay for the initial testing and you will have to put the new FO files where they are expected to be (I beleive in 7.2 they must be in /webfonts folder under theme's /css folder). After that the bot will merge the big global.css file with all the glyph mappings in the FA source css (necessary if you don't want to have an additional call to another css), this adds around 11k lines of css. The only issue I think I had was in FO -> My profile section one of the icons was not rendering properly so I had to change it to similar one in the new package. In total, around 2 hours with all the testing

Warehouse is not made by Sunnytoo. Regarding the php8 support - I managed to make it run on 8.3 with ChatGPT and Codex lately. Minor fixes but... Even managed to update it's FontAwesome to 7.2 with shim for modules and native usage.

Nice. It's always good to run your store to the most current version as there are plenty of bugs fixed and many security flaws too.

So you fixed the error by updating the store to the latest version?

OK, that's right but this issue could 99% be solved by an LLM in like less than 5 minutes. I don't see why there are small merchants that don't pay for some of them to help with such tiny tasks.

Open the error, copy it and give it to the model. Give the model context to work with (I use Codex locally, create a local repository and work in it, it makes all the changes, you have to FTP the files to your test server and check if the fixes work). If you work with ChatGPT or other model where you can't give direct access to a repo you can paste also the php code from the file that is at fault. Usua,lly those fixes are very easy (bringing new php compatibility to the code).

I'm about to release my vibe-coded one, but it's perfect that we have an official one from you guys! Can't wait for the link, so I can test it.

Codex or ChatGPT will fix this in one prompt.

This is the idea of this community.

Which page is that? Homepage? Can you open your BO?

This issue is caused by bots that try to delete already empty cart they create I think.

Sorry, my initial answer was not 100% correct. It is not removed in 1.6 as it is, of course, part of the themes. In Niara it was removed with https://github.com/thirtybees/niara/commit/3ab40e7ae52e0c495a2b67f09131996fb6ed65ea (absolutely the same in the Community theme). If your theme still use it you can approach the issue in a different way:

Delete the line. There is no need for this anymore. Or update to 1.6 stable. Where this is removed.

I took few days off.... 😉

Do you have proposal how to fix this 'bug'? I believe it's architecture change that breaks compatibility with many things.

Yes, now drop the spam 🙂

I hope I have something to show in the recent days.