Paul

Very nice work! What do you guys think of the module system in v3 vs v2? Didn't you also build a module for noc-ps for v2?

We are open to that idea.

Blesta will have more features, and more support for dedicated and VPSs as we move forward. So, you're right in drawing a distinction between us and HB. All in due time. I think this thread is more about people's distrust in their business practices, but we certainly feel that people should use what they want to use. If HB is the best thing for your business, by all means, go for it. In my (admittedly biased) opinion, there is additional unnecessary risk with using their software, but I'll leave it at that. Our focus is Blesta, and building the best software we can. The 3.0 release is just the beginning.

It won't happen. It's the same reason everyone has a qwerty keyboard and not something more efficient like dvorak.

I think most people would agree that their software is pretty advanced, and becoming more targeted to enterprise. The problem is that they completely destroyed their reputation. They didn't start out on a good foot either, the first version was a complete rip from WHMCS.. the staff area looked the same, and the database schema was pretty much identical. (I talked to Matt and Aaron from WHMCS directly at HostingCon in Austin about this). They also stole our software license agreement. Talented developers? Yes. Ethical businessmen? No.

I saw a similar story on this recently, I just didn't think the Ћ character was part of the UTF-8 set already.. interesting. Don't think it should be a new letter in the 26 letter alphabet though.

It's like HB changing prices all the time. It drums up debate and results in free marketing.

In v2 we actually had an option to enter the spamassassin binary path, and we would run everything through spamassassin first. I don't think many people used it though. Using re-captcha or areyouhuman here is probably a good idea.

I believe there is an event on service renewal that can trigger the module to calculate and return bandwidth overages for the previous month. It's one of those things we thought about and planned for on some level, but don't have a working example of yet. This could be used for any kind of overage.

This is probably a good idea. And you know what I like about the source being available? You guys can make changes, test them, and share. EDIT: CORE-580

Around 2003 I started writing a billing application for our own internal use, in the middle of the night at home, because nothing really existed. In 2007 we decided to turn it into a product and with Cody's help we released v1. Then we started to get more serious about it and released v2. We had limited success initially, and with v2 it started to gain some traction and we saw the potential. The motivation for us is to showcase our abilities and to build the best software we possibly can. We think we're uniquely qualified to do it. It's not all about money for us.. if we have a choice between making more money and making better software, we will pick better software. Of course, money is nice too and allows us to do more of what we like to do but we put our best foot forward and work with integrity. We do very high end web application development for other companies, and they own the rights to the software we write. Blesta is our own product and where we want to be. I have been involved in the hosting industry since 2000, so hosting billing software is a really good fit.. it's what we know. We have lots and lots of ideas, and if we can get Blesta to where we think it can be you'll see a lot more from us. Complimentary products. We learned a lot with our initial v1 release. Building an application is one thing, building a product is an entirely different beast. It's a lot more work. Honestly, building web applications for other people is in many senses easier.. but it's not as rewarding.

We suggest the default settings for both of those fields, 80 to reject and 10 to review. The defaults are pretty conservative and unlikely to reject or require review for non-fraud orders. If you aren't sure, leave as-is and adjust as necessary once you get a feel for the scores.

Nice! How's the printing, come out good?

Do you find most attacks originate from the same location or email address? I can see an internal blacklist being useful for that 1 pesky person who won't stop opening tickets or placing fraudulent orders but most of the time the stuff we see is distributed.

Thanks for the suggestions, most of these we will definitely be implementing. Our development process is iterative, and we often circle back around and improve existing features. I don't have an ETA for these changes, but I'm curious what the community thinks in terms of priority.. which of these items are most important?

You can add a Tax ID/VATIN under Settings > Company > Taxes > Basic Tax Settings.

It changes with each new session. In config/blesta.php look for this line: Configure::set("Blesta.csrf_bypass", array()); You can add controllers and actions to this array to bypass CSRF checks, for the client login it should be array('client_login::index') so the following should work: Configure::set("Blesta.csrf_bypass", array('client_login::index'));

Anyone else experiencing this? Do you also have Blesta installed in a sub-directory?

I'm pretty sure you will need to disable csrf tokens for the login page in the config file.

UK, Canada, Australia all use Celsius for temp right? I'm finding myself using Google to convert these to Fahrenheit so I can make sense of it!

That's a good reason. I actually get a reminder about auto-renews a week or so in advance so have the opportunity to cancel the auto renew, which I often do for domains I later realize I will never use.

Yeah, it's good through May 30, 2023, don't have to worry about that expiring anytime soon. I wonder what their reason is for capping it to 10 years.

I always have domains set to auto renew, and important domains I usually renew out far in advance.

I think that's a pretty common practice nowadays, especially for domains that have any kind of significant traffic.

It's still a work in progress, I wanted to finish up a little more before I put it up. Shouldn't be long, and it won't be 100% done but would be nice to get some feedback.