Tyson

You can use the client ID to fetch the billing contacts, e.g.
<?php public function buildProcess(array $contact_info, ...) { Loader::loadModels($this, ['Contacts']); if ($this->ifSet($contact_info['client_id'])) { // Fetch all billing contacts for this client $billing_contacts = $this->Contacts->getAll($contact_info['client_id'], 'billing'); } }  

Take a look at order embed codes. You can also look at CORE-2583, which implemented this feature for additional details that may not appear in the documentation yet.
You should go to Packages > Order Forms > Settings (tab) in Blesta and paste in your Google Analytics to the Embed Code section. You can specify what pages of the order process it should appear on if that's relevant to you.

Blesta uses the minified version of that file, i.e. "application.min.css". The other file, "application.css", is not necessary to keep in your installation. Both contain all compiled CSS as Paul mentioned.

There are a couple ways to include additional information in that section:
Update the custom module you're using to accept that field. This is usually done if the module itself uses the value of that field for some purpose Create a configurable option under Packages > Configurable Options. Then, assign it to a Configurable Option Group and assign that group to the package. If the configurable option term/period/currency matches what's available on the package, that configurable option will be displayed on the order form.

I think you're referring to the fields required by the module, which are defined in the module's source code you're using found under /components/modules/MODULENAME/MODULENAME.php.

What are you trying to do exactly? If you're creating a new template set, you probably want to write your own JavaScript to use in the client UI.
You could strip out the Bootstrap JavaScript from app.min.js. I believe everything defined before "function(t){t.fn.extend({blestaRequest:function" is related to Bootstrap.

mcrypt is not available by default for php7.3 so you have to use PECL to install it. I followed the tutorial here (Even though it says php7.2)
https://lukasmestan.com/install-mcrypt-extension-in-php7-2/

Thanks Tyson.  That extra detail was enough to get an exception from TrustWave.  The exception is not permanent, but hopefully the Blesta software will have an updated jquery version before the it comes up for review/re-evaluation.
 

The "OrderPlugin.client.name" definition is used in a couple locations:
In the client navigation When listing available order forms on the /order/forms/ URI For #2, the language is loaded from the language file, so it will appear as whatever definition you have set.
For #1, the language is translated to the default language and saved in the database under the `plugins_actions` table. This navigation language does not change, or reload, unless the Order plugin is installed/upgraded, and remains static from there on. We intend to update plugins to support multi-language definitions that are pulled from the plugin's language file instead of the database, but this is not currently integrated into Blesta.

Hi @rebus9,
Blesta does not perform cross-domain AJAX requests without specifying the dataType option, so I don't see how the vulnerability mentioned (i.e. https://snyk.io/vuln/npm:jquery:20150627) could be exploited as it is described. Blesta, actually, does not perform any cross-domain AJAX requests at all except for one in the admin interface in order to load the "Follow @blesta" button in the Feed Reader plugin. Unless you have installed some other third-party extensions with Blesta that do perform cross-domain AJAX requests, I don't think you have anything to worry about regarding that jQuery XSS vulnerability.

We've been WHMCS users for well over 8 years and today we took the leap to Blesta. We will be integrating it with our new platform and slowly moving clients over in 2019. We have grown so tired of the price increases and code refactors over at WHMCS with no real added value for us.

The issue with service options not allowing you to add an option for the Universal Module was an issue resolved in v4.4.1. You should upgrade to that version of Blesta and try again.

The issue with service options not allowing you to add an option for the Universal Module was an issue resolved in v4.4.1. You should upgrade to that version of Blesta and try again.

I would suggest uninstalling and reinstalling the Billing Overview plugin.

Thanks, we'll take a look as apart of CORE-2911

I started using Blesta a couple weeks ago.
 
http://www.throttlehosting.net
I am really liking it. Much better than our previous billing system

It's best practice to use the version of the extension that is provided with Blesta or a newer version if it is compatible.

You should stop using MyISAM tables and use InnoDB. MyISAM does not support transactions, which would be very useful, and is Blesta's expectation to preserve data integrity.

Yes, that's correct.
You won't be able to submit files via the API; you essentially submit a reference to it. The files are expected to already exist in the server's temp directory (or whatever directory is set for 'tmp_name'), and then you provide details of that file (i.e. that reference) in the $files you submit via SupportManagerTickets::addReply. So, in order for you to attach a file to a ticket reply, you will first need to upload the file to the server separately.

Yes, that's correct.
You won't be able to submit files via the API; you essentially submit a reference to it. The files are expected to already exist in the server's temp directory (or whatever directory is set for 'tmp_name'), and then you provide details of that file (i.e. that reference) in the $files you submit via SupportManagerTickets::addReply. So, in order for you to attach a file to a ticket reply, you will first need to upload the file to the server separately.

The client ID already is the auto-increment ID. That value increments every time a record is added, whether it was apart of a failed transaction or not.

It's unfortunate that even with null values set for the optional arguments it still fails.
An alternative would be to call a different API end point that wraps systemEncrypt. For example, you could create a simple plugin for Blesta that defines a model and method that returns the value of a call to systemEncrypt.
// Plugin model class MyPluginEncryption extends MyPlugin { public function encrypt($text) { return $this->systemEncrypt($text); } } Then, instead of calling systemEncrypt directly via the API, you call your plugin method instead.
// API request $response = $api->post("MyPlugin.MyPluginEncryption", "encrypt", array('text' => 'test123'));  

So I and my team made this blesta plugin to automatic manage virualizor packages,
In the configuration panel, You set your currency and price per resource.
Then you configure how many packages you want to randomly generate within that range.
For example, I want 6 packages to range between 2-4cores the plugin will automatically create 6 packages from small-1 to small-6.
This will also create the plans inside virtualizor to ensure virtual machines can be deployed correctly.
Prices will start around
£7.50/mo branded
£14/mo unbranded
 
We may consider selling own license at later date here some examples.
 
 

Thanks, this is CORE-2828.

You would need to update some files. An example is provided in a different thread that only allows email as the username. You would do the opposite and only allow the username to be specified.