EidolonHost

So much blue.
 
It kind of makes my eyes hurt looking at the navigation bar. I'd recommend a more clearer distinction.

it can be for anything but it has to be tied into the person's license manager plugin(well the api controllers at least)

So... I just wanted to post an update: It appears that the Namecheap module works just fine on Blesta 4.0...
It still won't work on Blesta 3.6.2. Interesting difference... I'm not sure exactly what's different here, though.
Edit: I suspect I know what the issue is... it's likely IPv6 related.
Edit2: Yup, it was IPv6.

... Whoops. >_>
Well, he's got an integration going on. You'd have better luck at Github, I suspect. That's over on https://github.com/CachetHQ/Cachet

In structure.pdt, I believe.

Looks like I'm in the clear after I removed the database entries... I'll give it a while longer, see if it encounters further issues before I call it good but your suggestion did the trick.

This is a great idea that I'd love to see implemented. Anything to further security is good in my opinion, as long as we try to make it as painless as possible.

Oh, be sure to run ~/admin/upgrade guys, there's database migrations that need to run.

I was able to successfully upgrade from a test 3.6.2 instance to a 4.0.0b1 instance. I had forgotten to complete the upgrade via admin/upgrade but even having not done that, it worked pretty nicely.
Then I did the admin/upgrade when I checked out another thread that reminded me of its existence. Things seem to be A-OK here. But I'll try this with a copy of current-production data.

... I completely forgot to do the upgrade. Fortunately, it didn't do anything damaging since I hadn't performed the upgrade...
But, doing the upgrade via web went through nicely. It did redirect to the admin dashboard with a completed successfully message.
php 5.6 here, default install on a development server. This was from 3.6.2 to 4.0.0 beta 1. Wouldn't be surprised if you had a module or something similar causing a white page but... this is basically a very clean install, so it seems to have worked for me in that aspect.
Edit: The upgrade took about 2-3 seconds or so before it completed.

Just remember there are a bunch of open source modules/plugins/templates/gateways/etc from naja7host. That doesn't include his helpful code posts in this forum.  Plus he has been around the forum since the end of 2012.  That gives me a lot to go on to base his coding skill off of as well as his reputation around this community.
You are fairly active on the forums but from what I can see you don't have any open source projects for blesta that I can look at. You haven't yet contributed enough to the community to be considered at naja7host's level. Maybe in the future as contribute more and have more people using your modules/plugins and reviewing them, but not yet.

... I completely forgot to do the upgrade. Fortunately, it didn't do anything damaging since I hadn't performed the upgrade...
But, doing the upgrade via web went through nicely. It did redirect to the admin dashboard with a completed successfully message.
php 5.6 here, default install on a development server. This was from 3.6.2 to 4.0.0 beta 1. Wouldn't be surprised if you had a module or something similar causing a white page but... this is basically a very clean install, so it seems to have worked for me in that aspect.
Edit: The upgrade took about 2-3 seconds or so before it completed.

I'd have to agree with the others... it's best to have a billing-system dial for how many to send at any given time. I would not assume that the mail server will spool it for you and send it out in batches. I would assume that by default you should have the option to control how often it sends e-mail and how quickly it should send that e-mail.
Complying with the CAN-SPAM act in the US and other likewise legislation in other countries would be difficult if you assume that any Blesta user wouldn't mind having their billing server be blacklisted for sending out too much... even if it is legit.

... I completely forgot to do the upgrade. Fortunately, it didn't do anything damaging since I hadn't performed the upgrade...
But, doing the upgrade via web went through nicely. It did redirect to the admin dashboard with a completed successfully message.
php 5.6 here, default install on a development server. This was from 3.6.2 to 4.0.0 beta 1. Wouldn't be surprised if you had a module or something similar causing a white page but... this is basically a very clean install, so it seems to have worked for me in that aspect.
Edit: The upgrade took about 2-3 seconds or so before it completed.

Had a play with the beta just recently. Looks pretty damn good. I'll install a development copy on the testing server I have, which is running php 5.6 although there is the possibility of also running php7... but I'll have to check into that.
I'll report back any issues I find but I must note I like the new look. Seems a hell of a lot cleaner to me, truth be told. I was playing with this on Licensedemo.com so I didn't notice any initial issues, but best to install it on our own server and take a look under the hood as well.

New security measure that helps browsers load stuff ONLY whitelisted by your content-security policy. The link I included in my previous post should help with understanding this in-depth. You can see this for yourself with https://securityheaders.io/?q=https://eidolonhost.com/
It's still a bit of a work in progress, fine-tuning my CSP policy for the server.

Yep. Equally very simple... and I just realized that's why my Blesta install looked so fucked with Content-Security-Policy enabled... I forgot to whitelist the CDN...
Well... that will be fixed later. But it's likely something to watch out for as people start implementing Content-Security-Policy. Something to note in the docs, maybe?

Had a play with the beta just recently. Looks pretty damn good. I'll install a development copy on the testing server I have, which is running php 5.6 although there is the possibility of also running php7... but I'll have to check into that.
I'll report back any issues I find but I must note I like the new look. Seems a hell of a lot cleaner to me, truth be told. I was playing with this on Licensedemo.com so I didn't notice any initial issues, but best to install it on our own server and take a look under the hood as well.

That is very good to know. I've noticed you have done other modules for the competitor and have released open-source versions as well. I like this, as it provides the buyer with a lot of flexibility.
Still, I hope you do well here.

Nice, welcome back to the land of Blesta.
I was sad to see you guys go when you signed your exclusivity agreement. Hopefully now that you've returned, we'll be able to do more business here.
I suspect that most people will come to you and insist on having a copy of the source in the event you are forced to do what you did last time, from this point on. I know I would, if I considered hiring ModulesGarden for my module development needs.

Nice, welcome back to the land of Blesta.
I was sad to see you guys go when you signed your exclusivity agreement. Hopefully now that you've returned, we'll be able to do more business here.
I suspect that most people will come to you and insist on having a copy of the source in the event you are forced to do what you did last time, from this point on. I know I would, if I considered hiring ModulesGarden for my module development needs.

That is very good to know. I've noticed you have done other modules for the competitor and have released open-source versions as well. I like this, as it provides the buyer with a lot of flexibility.
Still, I hope you do well here.

Keiro, that should not be a problem as we always provide our customers with the source code of their custom software development projects. If we code something specially for you, then the code is yours. This is natural.
If we create and officially release a module completely on our own, then it is usually encrypted, but in most cases we offer its open source version as well.

Nice, welcome back to the land of Blesta.
I was sad to see you guys go when you signed your exclusivity agreement. Hopefully now that you've returned, we'll be able to do more business here.
I suspect that most people will come to you and insist on having a copy of the source in the event you are forced to do what you did last time, from this point on. I know I would, if I considered hiring ModulesGarden for my module development needs.

I hear you. All good points. Blesta is under developed for the hosting industry. 
Blesta's vision of their software vs. reality is where the problem is. I really believe Blesta thought they could develop the core part of the software, make it all very modular, and then developers would take it from there and offer modules based on demand. 
Reality is that there are only ~5 module developers for Blesta, and the market is so small, they get very little out of making modules. Some modules exist, and make a really good impact on the overall software, but you're basically relying on a single person to extend Blesta to the point you need it to be at. The reason is companies don't want the headaches of having to search out developers for features that the industry expects to be standard in any software release now. So the customer base isn't growing much, which means less developers. A classic catch-22. 
An idea I had a little while back would be for Blesta to partner with developers, get all the code going in the same direction, and implement those modules directly into Blesta, and they pay the developers. I'm not going to assume what the finances of that arrangement would be, but it's an idea. 
One other thing that should be done is really start doing focus groups of actual users, of varying company sizes. And then pivoting in small, quick releases, based on that feedback. One of Blesta's competitors just released a feature... auto-update. Because it was the highest voted feature by their community. I won't get into how ridiculous that kind of feature is, because if you can install the software, you sure can update it. Especially since no one in their right mind would auto-update their billing system. But they spent months of dev time creating this feature and trying to hype it up. Stupid stupid stupid. It shows they didn't really talk to the people running their software and relied on community upvotes instead. The opportunity cost is high. 
I'm going to give Blesta a shot after their initial 4.0 release. This release, from what I can tell is more of a major re-factoring and maintenance release, positioning Blesta for better future updates. So I'm not expecting a lot of critical features to be in it, and I hope you aren't either. Documentation is a separate issue. 
I really do hope Blesta comes to understand their core market segment, which is hosting. It's where it was born. The reason for its existence was the faltering of previous competitors. Get that  industry taken care of first, grow the business, and then look at other industries that are struggling to get by with subpar billing systems and hit them up. Don't try to be a generic be-all billing system yet.