Leaderboard

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.

@the.rampage.rado I never use Advanced Stock Management in the shop; I believe it’s a feature that causes nothing but problems and offers no benefits whatsoever. So I haven’t tested "split orders" with ASM. Yes, different carriers must be configured for the products for "split orders" to take place. Yes, with the module I’ve attached, you can change the carriers for individual sub-orders in "split orders" mode. And, as a point of interest, a Prestashop fork called PhenixSuite has fixed this.

https://mship.no running in catalog mode, migrated from Prestashop 1.6-24. Running Debian Trixie. NGINX / HTTP/3

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

restarting apache2 maybe?

Together with uploading the software also generates the derived images (123-small.jpg, 123-large.jpg, etc). This often takes more time than the uploading itself. So you should check which image types you have enabled. Maybe you can reduce their number.