Leaton

Woocommerce has a big issue with their database set-up actually especially for large stores as the index keys are not set properly which really affect loading time if you have certain ‘custom’ fields (read: any product attribute and such is put in the same database table as the main product info etc etc making loading times increase tremendously), this is not basic knowledge for mainstream shop owners as it’s only to be found and read about on Github and then we’re not even speaking about wanting a multi language shop which creates so many more entries. From what I’ve read this is something very hard to now fix as it would break the core for people updating from an earlier version and basically any plug-in built for woocommerce.

The reason I see it as being a bug is that it should be a shipping status that can be easily dissabled or editted without editting core files or using extra modules. I think that would make a lot more sense.

Hi Andy, the solution is to edit the files as noted by wakabayashi - it seems it was still not recognized as being a bug after all this time but take in account that with any update you might lose the edit so it's best to do it as an override as noted by doclucas

You're looking at the ebay module, the Amazon one seems to lose compability at 2.0.0 version

No, but we stopped using TB a while ago because of some external partner we use dropping PS 1.6 support, we moved to woocommerce which has been a pain as the size of our shop is just too much for it to handle, so now looking at different solutions. But sadly did not keep a backup of the modules as I always just assume they're lifetime and accessible for re-download at any time, lesson learned I guess! Haha.

Yeah I noticed that yesterday. I guess if they don't maintain the module for 1.6 or thirtybees there's not much point.

Thanks for the info, bit annoyed that I bought the module through the thirtybees marketplace in January 2020 and now can’t download or use it anymore. Should have bought straight from Prestalia

Was this module removed from the marketplace?!

Best is to get bug fixes into core. Which requires a fairly clear description of what the actual problem is, together with the changed files in an issue report. Sorry for reviving this old thread, just wanted to add my 2 cents. In my opinion this is a bug as the in_transit status and e-mail are hard coded instead of being an actual order status (that could then easily be disabled) with attached e-mail. So what happens is at the moment you add a tracking number it sends the in_transit e-mail to your customers, when you change the shipping status to ´sent´ it then sends the shipped status e-mail. This means customers get 2 e-mails in a row where the in_transit e-mail is then useless.