the.rampage.rado

Big Pharma does not give 5 cents about your site. Probably some "eastern European" or Chinese hackers are probing you. In order to try and heal high usage you can try the free tier of Cloudflare and if they try to hit your BO page rename the folder and install and enable recaptcha module for all input forms. And don't forget to update to the latest TB edge version (many major and medium security hacks were fixed since the last official version).

No, my shops have all the goods in my warehouse so I don't need supplier lists. I can see this helpful for dropshipping retailers. But in the same time the customer sees 2 orders with the same number, pretty confusing. Probably this order splitting should be made differently, even if they expect 2 orders from 2 warehouses. I had it like that because when I started my first shop I had ASM on and all products where there. As years progressed I saw few bugs (that I don't even remember now) and started clicking 'enter manually' on each new product. Now ASM is disabled and life is better. Or at least until datakick don't release his warehousing module and I see some cool features that I need (then it life would be better 😄 ).

For me this happens if I have products that use ASM and that don't in the same order.

I'm not sure you can use TB (or PS in that matter) as true email client. IMAP is used as email protocol only. If you send an email through TB's BO then you will have to continue the email chain in a separate email client.

When you click on refund this is the last order status you have to set in this scenario. Some other payment methods (modules) might not restock but in this case you would not have to put Canceled after Refunded. Also this might help in quick analysis of the order s in BO - how many refunded, canceled, etc orders you have divided in different end statuses.

Currently you can't but this was something I wanted to see also as I started recently using multistore again and sometimes errors happen. 🙂 This might be a nice addition.

Before you start with Woo update this shop to edge channel and make everything working. 1.3 is good but edge is much much better AND MORE SECURE! 😉

Welcome to the forum! IMHO TB is far better option than PS8, Woo or Magento if you're just starting. It scales well, there are plenty of modules available (both free and paid) and if some of the themes from TB does not work 'design-wise' for you there are many PS1.6 themes that will work just fine (few simple tweaks by any php dev here and there in order to make them php8 ready) and you're good to go. OS is fine but supporting the project is vital for it's future development. So if you choose TB and you fall in love with it down the road please consider supporting the developers that keep the core bugfree and running on the latest server software. Cheers!

Nice, I would like to test it and then buy it just to fix that. 🙂

Will this speed up the last step in the order?

Try smtp.gmail.com and the proper port for SSL or TLS.

It's not critical at all.

I think your smtp server is not right. Please, check it first. This error is not related to the visible pass in BO. Google has no eyes there 🙂

TB updater is different module than Core updater. The first one updates only the modules, the second one updates TB. So you're running ME and have removed ME's core updater and installed the TB core updater and it's giving you this error?

You use ME's core updater or TB one?

Same. A user can purchase 'as guest' numerous times with exactly the same details. They enter the same information. What is bothering you, do you think there's something obstructing them to complete the order?

If the first one is a guest order and during the second one he/she made an account this happens. "New account' for the user type. All details might be the same.

Go to Advanced -> Logs and upload this file at the end of the page. It should decode it and give you the error. Probably some module is not compatible with your current TB version. Any recent changes in TB or your modules?

Yet, again, you can use a google font locally. There are plenty of tools that assist in the code and the process. I do so on each on my stores.

I don't believe I understand quite what you say but... :) I use webp from the second day TB introduced it in the core and I don't know how Google will prohibit you from using this free file format :)

What do you mean 3rd party? Like CDN? All webp images are generated, controlled and served locally. But im south of the Danube, so it might be different :P

This is not a bug. If you have small image why should you enlarge it and present a blurry mess to the customer. If you want higher res image - just start with one if such is available. The system will shrink everything down to your images settings but will not enlarge smaller images. EDIT: Regarding webp - your theme should support it. Go to your theme's config.xml and try to enter <webp>1</webp> <webp>1</webp> just at the end. Then go to Images, enable the now visible webp setting. Regenerate your images, wait until the regeneration is done then clear your cache and check if your front end displays them correctly. MAKE A WORKING BACKUP BEFORE THAT, most themes work but some badly coded ones might ask for jpg! About lazy loading this setting is heavily dependant on your theme and is not set in Images but in your theme configurator (if such support is present). If there is no such setting you might try to use some module but I can not recommend a viable solution as my theme have it embeded.

Try this: https://github.com/thirtybees/thirtybees/commit/136017aedcbf46f708b31df96ea2c11fd8acecf3 This fix is part of 1.5 but you could try it, just keep a backup of the original file.

You definetly should not stick to 1.3. What is your current php version? After 1.3 you should switch to 1.4 then switch to php 7.4 and update to edge. Currently edge is compatible with php8 but you should be careful around your installed 3rd party modules with php 7.4 and 8. Step by step and with our help you should be able to update it to the latest version. Just always keep a backup of your files and your DB on each step so you can revert back. Reasons to update to edge: - code optimization for modern php versions - speed and compatibility imrpovements - bugfixes - at least 10 security fixes since 1.4 - new features

So you're open to loosing orders if users don't have gmail or yahoo mails instead of once in maybe 25 times you have a user with wrong email?