lesley

SLA's like that are hard to enforce as well. There are times that you cannot reach a site that everything is fine up to and leaving the data center, it could just be a network peering issue where your isp peers with another network. I see that issue a lot with clients calling in because their site is down.

It cannot be changed, it would break a lot of things. We are literally talking about .5 kb of data, its not going to bloat the database that much.

Great. Hopefully the new stats setup is working perfectly. We just really needed to test some logic on deleting the old modules on upgrade, while at the same time a new build installer missing 23 modules and 1 new module. Should also speed up installations as well.

We are planning to release a release candidate this week I think. We are going to go through the RC process because of the new stat module that eliminates the 23 separate modules. It adds a new controller, so we want to be sure everything is working before we release it. It might also include some scaffolding for new features in the 1.0.5 release too.

Case in point of how it was useful to me last week. I set up carriers on a site using a rate table 2 years ago. The guy calls me complaining about them not working correctly. Basically they were letting Canada orders through at US prices. He blamed me of course. So I checked everything and they were in fact broken. Then I looked at the database and I could tell they had been edited, because right when the issue started happening new carrier IDs were assigned to orders. So I knew it was not my fault and I charged him. There are lots of other uses as well, but there is a real world use.

There is, for historic purposes.

Great, good luck and happy selling.

Are you using our json module too?

True, didn't you change that functionality a while back?

Can you pm me the cpanel / back office login and I can check it out?

Is it just a new domain, or a new server as well?

Hmm did you move, then upgrade? Or did you have a working thirty bees shop, then move it?

Did you change the url in the database in the tb_shop table?

The best solution is to have a module that makes all registrations pending. It should be on the merchant to verify the vat number.

Yeah, they base it on the pricing model of the servers they build on top, so some are more expensive than others.

Click on Data centers, https://www.cloudways.com/en/pricing.php#small-plans You can use it as a testing ground until your host upgrades, or just use it for the one site. The plans start around $12 a month.

Why not just start out on cloudways, they have elastic already. Cloudways builds on top of Vultr, Digital Ocean, Kyup, Amazon, and Google, so they have data centers in 50 cites that you can launch from. There are like 5 different choices in Germany.

Can you test out this commit, https://github.com/thirtybees/bankwire/commit/6c42c12fe4b636d68f99c4db2aee959034b5042e

Can you test out this commit, https://github.com/thirtybees/bankwire/commit/6c42c12fe4b636d68f99c4db2aee959034b5042e

It should be able to work with it, are you having any issues getting it set up?

Old orders. It is used for associating carriers with old orders and old invoices.

@Traumflug You are correct about the deleted carriers, the carriers always stay in the database so they can be correlated to older orders.

I will see what we can get together for 1.0.5. I don't think we can do the security question. Although good practice, it would require core changes that would not be backwards compatible.

Yeah, we will have to see if that is possible with the existing framework, I am not sure, it might be a breaking change with every template.

Good question. What flow would you recommend for converting like that?