Leaderboard

You can still link to a specific package, please see http://docs.blesta.com/display/user/Order+System#OrderSystem-LinkingtoaSpecificProduct I'll send you a link via PM for an example on your order form.

The demo is running v3.4.0 now. It will be helpful if we can pre-populate some KB articles and other data, but that's a task for another day.

This is certainly a possibility. Blesta uses SwiftMailer and there are various transports available for it. New transports could be written to add support for services that are not currently supported. It looks like Mandrill is supported http://help.mandrill.com/entries/23738427-How-do-I-send-with-SwiftMailer-PHP-

If the check did not go through, change the transaction from Approved to Returned. I recommend Returned for bounced checks, as that's effectively what happened. Voiding it as Mike describes will work as well. Once the transaction is no longer Approved, it will be unapplied from the Invoice automatically, re-opening it.

When using a different hostname for each company, the hostnames all simply need to point to the same document root. So, if you have Blesta installed at /home/username/public_html/, then all hostnames for all companies need to point to this server path in your web server configuration. If you're using Apache, then in your httpd.conf, all the virtualhosts would have the same docroot. Please see http://docs.blesta.com/display/user/Creating+Companies#CreatingCompanies-ConfiguringCompanyHostnames for a sample configuration. We highly suggest that if you are going to use multicompany that you install at a sub-domain. For example, billing.domain.com, account.domain.com, my.domain.com, etc. The reason is that you can have an actual website off domain.com as part of a different virtualhost. If you have Blesta installed in a sub-directory, and both domains have the same docroot, then they would also display the same website content. I hope that helps!

The other hostname has to point to the same blesta installation folder.

I'm interested to see that there are others that still find this Blesta functionality confusing. I really think that what Blesta currently refers to as the Renewal Date (or Date Renews) would be best described as the Next Invoice Date. The renewal date should relate to the service itself and not to the invoice scheduling, which can be a date managed by the system internally.

looking good any chance to get that theme?