Leaderboard

I do like the mobile swipe menus. I'm considering drop down menus, but making it an option. This would fit well with other plans to allow more customization. For example, in the client area I would like the widgets to be able to be sorted by staff, and possibly placed on their own pages and show up in the nav instead of the dashboard.

I think the theme is designed to be like WHM/cPanel Considering a drop down menu option as an alternative in the admin area, but the last thing I want are nested drop down menus like they have that are more confusing. Simple is better.

https://wiki.php.net/rfc/remove_deprecated_functionality_in_php7 Goodbye mysql, hello PDO! It's good some of us thought about this a long time ago.

I think that styling html email is good and using cross client/browser compatible email (also responsive) is better. Moreover add the necessary code html and css to make it through the WYSIWYG editor of Blesta, it is virtually impossible (if it is good, after saving you lose pieces). I image, editing email templates in Blesta, that i can select for each template a "model", stored in company folder: so i can make transactional emails more attractive and effective. I made some changes that work for us: - we get and update an html email from https://github.com/mailgun/transactional-email-templates; - we put one or more placeholders (eg, "@BODY@") in this template; - we put this template in "uploads/[COMPANY_ID]/email_templates" folder and name (e.g. "tpl_email.htm"); - we added in app/models/emails.php after row #806 $email->html = $parser->parseString($email->html, $parser_options_html)->render($tags); the following Loader::loadComponents($this, array("SettingsCollection")); $tmp = $this->SettingsCollection->fetchSetting(null, Configure::get("Blesta.company_id"), "uploads_dir"); $template_path = $tmp['value'] . Configure::get("Blesta.company_id") . DS . "email_templates" . DS; if (file_exists($template_path . "tpl_email.htm")) { $tpl = file_get_contents($template_path . "tpl_email.htm"); $email->html = str_replace('@BODY@', $email->html, $tpl); } Attached you can see one of results. But now i like to have a more friendly management of this feature. What do you think about?

I've not even moved to PHP 5.6 yet but I will be but PHP 7 sounds much better and they did a Windows and skipped 6 (they skipped 9). What do you think about PHP 7? sound better? look better? http://www.phpclasses.org/blog/post/242-PHP-7-Features-and-Release-Date.html

We are looking into adding the noVNC console for KVM, HVM, and possibly signing the jcterm applet to get around that security exception. SolusVM's jcterm applet was recently signed by OnApp.

I think Java security requirements are much higher than they were previously. You may need to add your site to the security exception list from your Java Control Panel before the console will load. Ideally, we'd like to setup an HTML5 version of the console instead.

It sounds like you're confused about how to create services and how they work in Blesta. I'll start by clarifying what you were asking about earlier: If an invoice is generated for a service, the service will only be made active when the invoice is paid. Once paid, the service will remain active. If the service renews on a recurring basis, an invoice will be created before the service renews. If that new invoice is not paid, the service will eventually be suspended for lack of payment. All services are connected to a module. The module essentially determines the "type" of service. e.g. the cPanel module is used to create cPanel services An invoice line item for a service usually follows the format: Package Name - Service Key (from date - to date). This is set automatically when the invoice is created. If you were just starting out with Blesta and wanted to test creating a service for a client, you might do the following: Determine the type of service you want to create. This would be based on a module, e.g. cPanel, SolusVM, etc. Activate the module and setup credentials for it from [settings] -> [Modules] -> (Manage the module). Create a Package based on the module, which will define any settings for the product and allow you to set pricing. Create a package under [Packages] -> (Create Package). There can be a lot of settings, depending on the module you're using, but at minimum, set a Package Name, select the Module you previously defined, define at least one row of pricing (term, period, price), and assign this package to a Package Group. You can create a package group for the package to be assigned if you do not already have one. Create a client under [Clients] -> (Add Client) to which you will assign a service. Once the client is created, you can view their profile from the [Clients] listing by clicking on the link from their Client ID. Once viewing the client's profile, you can manually create a service for them based on the package you created. In the left sidebar, find "Add Service" under Account Actions. Choose the package you created and continue. You will then be asked for more specific options to set for the service (if the module allows for it), as well as basic options about the Term (and pricing) you want to set for the service. You can also choose whether to allow an invoice to be created, or instead create this service for free. Continue to review the details of the service. Then you can create it. Once the service has been created, it will appear in the Services table of the client's profile page. An invoice may also have been created, if you chose to invoice for the service, in the Invoices table. I know there is a bit of a learning curve with how to go about managing services and how they work, but if the documentation is not enough, feel free to ask more questions.

When is that error shown? When viewing the server actions page, or after performing one? It looks like it may be a module error. You can check the Module Logs under [Tools] -> [Logs], and click a table row for a SolusVM entry to check for errors.

Bootstrap is used for the client area, not for the admin area. All of the templates are in /app/views/client/bootstrap/. You can clone the bootstrap directory with a new name, and select it from the Settings, and modify it.

You could probably use aliases to have Blesta installed at /portal on each domain, and have different document roots for the primary sites. I'm not familiar with that in order to help you with it, but it should be possible to do. I like it clean and easy though, so we recommend sub-domains for Blesta installs if using multicompany.

You might receive a 500 internal server error if you have a fatal error or syntax error in the code that is unparseable. If it only affects modules, then my guess is one of the modules is causing it. You can remove all of the module directories from /components/models/ and see if the problem goes away. Then add them one-by-one until you discover the module that is causing the problem.

Your example highlights a problem I have seen myself. The "solution" thus far has been to create a separate account for the client that does not have auto debit set up for manual invoices they wish to pay by check. So, a way to tag or categorize services and manual invoices to omit them from auto debit would be very nice. Perhaps an option that can be enabled on an invoice to omit it from auto-debit. A similar option could be added to a service or recurring invoice to set this flag on invoice creation. Then, at anytime the option could be added or removed from any specific invoice.