Paul

We're planning to add new invoice templates, and I'd like to include a version that displays all payments recorded for the invoice. I don't believe we have a task assigned for this yet, though.

Just an update on this, based on the ticket it appeared that IMAP worked when running the cron manually. I don't know if it's an issue with the cron running automatically or not -- if so.. if it works when running the cron manually but not automatically, it is very likely that mailparse is not available via CLI, but is available to the web server.

Try enabling error reporting and see if that white page turns into an error message. To enable error reporting, edit /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1);

You're missing PDO support from your PHP build. PDO is required.

Sounds like you may need to raise the upload_max_filesize setting in your php.ini to increase the allowed upload size.

The most common mistake is not selecting the proper thing under "Security", or having the wrong port. Please take a look at http://www.arclab.com/en/amlc/list-of-smtp-and-pop3-servers-mailserver-list.html They have a good resource for what ports should be used for what security type (TLS/SSL/None), which may help.

What issues are you having with SolusVM KVM?

Are the packages assigned to that group active? What module are they using? A screenshot of your order form configuration, and package configuration may help.

In a future release, we're going to have the upgrade process attempt to update any extensions that need to be also. This should cut down on this.. but for now, it's a good idea to check all plugins, gateways, and modules to see if they need to be upgraded.

Caching is key

The bootstrap conversion does make it much easier to customize Blesta, largely by editing styles or markup within the templates. These changes don't "stick" through upgrades though. This makes it easier for theme developers to create new template packs for Blesta though, and you'd be able to simple upload the template pack, and select it from Blesta for the company. This means your client area can work from a different template set for different companies. We have plans to add options for modifying the header/footer that will persist through upgrades also -- not sure if it will make it into 3.2 or not at this point. This will be useful for embedding google analytics, or other, visual changes that stay when you upgrade. The CMS plugin, that is in charge of the portal will be expanded, making it easier to customize the portal, and eventually, build out an entire website.

We built it with the idea to support contact logins, but the code is not complete. We have to design & implement contact ACLs.

CORE-627, tentatively assigned to 3.2 but it's not guaranteed to be in 3.2

We don't have any plans to be there, though it's not far from us. (45 minute drive)

Yup, added in 3.1. [CORE-503] - Module: cPanel - when creating new accounts include an email address

I'm pretty sure we'll be implementing a feature to prevent invoices from being modified at all -- as a setting. Without the setting, I sort of agree. I find myself having to make adjustments to the due date, usually to give the customer more time to pay because we worked out a special arrangement. It's a lot simpler to change the renew date only, than to unapply credits. Especially since you cannot manually reapply those credits yet. (You will be able to in a future release)

That's good news! Keep us updated, if you don't mind. The alternative would be to suggest a different hosting provider. Ones that don't stay on top of things might be vulnerable to attack. For example, there are lots of hosting companies still running vulnerable copies of WHM**, hopefully they are not one of them. I certainly wouldn't trust my information with them otherwise.

Ok, sorry I missed that. It looks like they are using a cPanel theme called VistaPanel. As far as I can tell, VistaPanel is just a theme, so not sure what else they have done that would require them to proxy the standard API, or block the JSON API. JSON is generally preferred over XML, and cPanel recommends it - http://docs.cpanel.net/twiki/bin/view/SoftwareDevelopmentKit/XmlApi It's probably in this hosting company's best interest to support the JSON API. Especially with the decline in companies that use WHMCS.

Sounds promising, anything to look at yet? We want to publish a roadmap, but still have some work to do to make that happen. It's been in process for a while now.

That's not bad at all. I always look at the time to recover the hardware cost.. a few months, ok.. but I've seen a lot of the Bitcoin mining hardware priced at 6 months or more. By then, it's pretty much obsolete. Too many people buying without thinking things through.

What hosting company is this?

Since the support system is an extension, a feature that only benefits that extension should not be in the core. Perhaps an area, created by the support manager within the client area, in which clients can add additional email addresses for tickets would work in this case.

Haven't looked into GoCoin at all yet, awesome that they work with both btc and ltc. What kind of hash rate are you suppose to get with the 290?

If you're looking to have an extension developed, email Eric. We've talked with him, and taken a look at some of his work and you can't beat his pricing. He has real experience building extensions for Blesta and we feel comfortable recommending him.

Are the other addresses required just to be able to open tickets, or should all addresses be emailed anytime the primary address is emailed? For example, would an invoice be emailed to all addresses, or only the primary? I think your request is pretty clear -- have the ability to add multiple email addresses like phone numbers. But, I think an email address would necessarily need to be able to be selected as the primary. Also, this is implemented in a way, with contacts. Billing contacts should all receive invoice emails for example. I'm not sure if email from non-primary contacts (anyone other than the account holder) are accepted for support tickets, so if tickets are the main concern, this may end up being a slightly different feature request.