Leaderboard

Hi all We've been at work behind the scenes to bring you a new release of TB. An official announcement should be made within the next week or so, with all the details etc. This update brings a new, official TB version of the PayPal module (using the latest PayPal APIs etc) - certified by PayPal. I've let the guys know about the message you've been getting - as far as I understand, the update should bring your module up-to-date with the latest version. We will keep you posted. @Smile @datakick

Yes, we have decided to deprecate the old paypal module. We thought about creating a new major version of paypal module, but decided to go with a brand-new module, so if any one of you guys wanted to keep using the old one, you could. The new module will be released shortly. It's based on latest paypal API. At the beginning it will not contain as many features as the old one, it just focuses on accepting payments reliably. In the future, we will implement other features like refunds etc, if there is a demand for it. Feel free to use old version of the module for now. Just know that it's been officially deprecated, and we will not invest any time into it.

Fixing the Niara template: https://github.com/thirtybees/niara/pull/100

@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