Paul

Yes, you can install Blesta on a VPS created by SolusVM, and use Blesta to manage SolusVM also. You just shouldn't install Blesta on your SolusVM master server, install it on its own VM that you provision.

I didn't get into the details, but overall it's very attractive. Looks great!

Fantastic! Nice job. I like the Blesta logo in there. Do you offer Blesta with your reseller plans?

CORE-2324 We'll take a look, if we can do something without slowing it down, great!

Your MySQL version seems quite old, but I'm not sure that would have caused the issue. A notice error shouldn't prevent it from executing, so I wonder if something more was going on there. Were you eventually able to get Blesta installed?

Finding the total remaining on all partially paid invoices is considerably slower, so I wonder if this was intentional. Seems like a bug, but a fix may cause the graphs to become very slow on installs with many invoices. Do you have a lot of partially paid invoices?

Should be, yes.

How are you testing? There isn't currently a payumoney gateway for Blesta (though we're trying to fix that).

This only affects older versions of Google Authenticator? If so, why not upgrade?

We have plans to create an affiliate plugin, but I do not have an ETA. We would suggest using the feature-rich 3rd party affiliate system that ties into Blesta well called iDevAffiliate. See http://www.idevdirect.com/idevaffiliate.php Here's information about the plugin they wrote that integrates with Blesta http://blog.idevaffiliate.com/affiliate-tracking-for-blesta-new-plugin/

What version of MySQL or MariaDB? I've not experienced this, but it looks like it happens when running a migration (database upgrade).

So, I think what needs to happen is that the DirectAdmin module needs an update. Really, I think it should work more like cPanel and auto generate a username and password. That, and it should run the hostname through a regex to verify that it's acceptable. Then, all the customer will have to enter is their domain name when placing an order. I don't recall if there was a reason we didn't do it this way initially though, thoughts?

Mike is exactly right. Services will renew on the day they were originally ordered. Two points on this though: You can change a services renew date to make it in "sync" with other services manually, and prorate the difference Services that have the same renew date will be billed on the same date, and appear on the same invoice

Are you using the official Directadmin module? What version is it?

Interesting thread. Sounds like it's sorted. I'll add though, the minPHP framework is not exclusively used for Blesta, and when we update it we take that into consideration. minPHP is used for many different projects, and the goal of minPHP is to keep it minimal. A fork of minPHP with significant changes/improvements is welcomed so long as it doesn't contain any code from Blesta that is not released under MIT.

Do you have one for SolusVM yet?

WHMCS doesn't do much in the way of enforcing data integrity, so the issue is likely to do with that. Blesta expects data where it doesn't exist, or there is data in WHMCS that should be unique that isn't. Works great for some, and not for others. New sign ups, and migrating accounts later could work if there's not too many. You could look to see what client has a key of 90 in Blesta after the import, and determine which client it was trying to import next, and compare with your WHMCS database. It's possible if you remove that client the import may get further or complete.

There is currently no option for this. You can prorate all services to a specific day of the month, but not based on the date of initial order on a per-client basis. I can definitely see the need for this though, and it'd probably make a good feature request.

When you attempt another import, and you doing it on a restored/fresh Blesta database? You won't be able to re-attempt an import if it fails. I ask because of duplicate key errors, though it may be unrelated. You could import data manually, any relationships between tables should be pretty obvious but if you have any questions let us know!

What do you think about adding this under Settings > Company > Client Groups. New section called "Required Client Fields" or something. You would then either check that it's required, and depending on the field, enter the minimum number of characters or possibly a regex. Required Limit/Regex [x] First Name [___________2] [x] Last Name [___________2] [x] Company Name [___________4] [ ] Title [___________] [x] Address 1 [___________6] [ ] Address 2 [___________] ... etc. To add, some fields will always be required and cannot be unchecked, like email and First/Last name... so for first/last name, you'd essentially just set a regex or minimum length.

Do you think the menu should be an option for the theme or something? (*) Click to Activate Navigation ( ) Hover to Activate Navigation I'm not familiar with what would be involved in making it transition automatically on desktop vs mobile. Mobile devices can have large resolutions now, and we don't want to have to maintain a list of browser signatures for mobile/desktop. It would have to be automatic via CSS/Javascript.

Thank you! I think most of the remaining issues are with PHP 7. You don't like to click? If we did hover activated menus, we would have to treat them differently on mobile devices since it's not possible to hover on a phone. Well, at least the phone doesn't know you're hovering. Maybe in iPhone 8.

CORE-2312 may be a PHP 7 only issue.

Welcome! I'm not sure if you'd be able to import 2 -> 1, unless you import them as separate companies within Blesta. If you'd like to give it a try, PM me your trial key (Settings > System > General > License Key) and I'll add an addon company to your trial. If they are in separate companies, they'd be in the same install, and you can switch back and forth between companies to manage without having to log into a different location. Re: Stripe, probably not, I believe they just released that. Give it a spin. It may be something that you would need to migrate manually. Blesta uses "Payment Accounts" for CC and ACH, so depending how they store it it may be imported, but may need some finessing to get working. I'd say, give it a spin, and we'll help with any questions or issues that arise. https://docs.blesta.com/display/user/Migrating+to+Blesta (Shows WHMCS 5.x, but has been known to work with 6, not 100% sure re v7)

Test, test, test, test. I'm finding bugs that should have been reported already. That is all.