Tyson

If you were using NetEarthOne or ResellerClub in WHMCS, then the importer could map the domains over to Blesta's LogicBoxes module. You need to have the LogicBoxes module installed in Blesta before running the importer though, so if that was not the case, you should run the importer again.

You may want to private message @Blesta Addons about his extension. Since he created it, he will be in the best position to help with whatever issues you're having with it.

Since the voided invoice is an unpaid invoice, it sends that email template. You can update the email template if you'd like to be more specific. For example, since that email template accepts multiple invoices, you might check that the status of the first invoice and set the subject conditionally:
{% if invoices[0].status == "void" %}Invoice Voided{% else %}Invoice Due{% endif %} I did not test this, so you should before using it.

You should translate languages files indide every plugin .

Thanks, I think that would be a useful addition. We'll look into it for CORE-3066.

Thanks, I think that would be a useful addition. We'll look into it for CORE-3066.

If you're trying to use the API to fetch a non-merchant gateway's payment HTML, see Payments::getBuildProcess as @coreyman mentioned above. The arguments required are the method's parameters.
If you are making a merchant CC payment, look at the other end-points available on the same page.

The module allows you to specify a port, but only a single port, not a port range. You can still set multiple ports on a single IP to use as multiple dedicated IPs though.

I'm new to Blesta and empty installation.
But yes now i added group and one product which i added to the  that group and now AJAX order template shows up.

The problem is that you are trying to access the /cart/ URI on an AJAX order form template. The AJAX order form templates don't have a cart template because the AJAX template represents a single page that makes AJAX requests for most of the checkout process (including the cart), so there is no cart page.
I'm curious how you got to that page, though, are you linking directly to it? If so, take a look at how to link directly to a product.
If you want that link to work, you can update your order form to use one of the Wizard templates instead.

I left a detailed response to exactly this question yesterday
 

It sounds like you want to POST each form to a separate location.
<?php // POST to the valid method $this->Form->create('/validate/valid/', [...]); ... $this->Form->end(); // POST to the index method $this->Form->create(null, [...]); ... $this->Form->end(); Your Validate::valid() method really shouldn't require an argument if you want to POST to it

Your example mixes procedural and class syntax, so I'm not sure if you're running individual functions or if those are methods in a class.
If you are writing procedural functions, simply:
return success(); otherwise for one class method to call another non-statically:
return $this->success();  

Depending on the configuration, you will likely need to reissue your Blesta license to the new domain/location.
If the credentials are all the same.
 
There is a README file included with Blesta that describes how to upgrade. The upgrade documentation is also useful.
Here's what I would recommend in your case:
BACKUP YOUR BLESTA INSTALLATION AND DATABASE (especially /config/blesta.php) Put Blesta in maintenance mode Disable your Blesta cron job Download and upgrade to v4.0.0 as an intermediate step. This is mainly due to there being a lot of changes between v3.6.2 and v4.4.2 to make in one big leap. I would recommend upgrading via CLI mode (instead of /admin/upgrade in your browser) so that the upgrade process cannot time out in the web browser. Upload the contents of the "blesta" directory The upgrade documentation will be helpful to review. There are files you should delete as well, mentioned in the note at the top of that page. Some people have problems if those files remain after upgrade while most others do not. Run the upgrade script (via CLI is preferred) Check your Blesta installation to make sure it is working normally on v4.0.0 Backup your Blesta installation and database again, now for v4.0.0 (You can perform the server/cPanel migration here, or later at step #12-13) Upgrade your server to use php 7.2 (php 7.2+ is only supported on v4.4.0+ of Blesta) Ensure php 7.2 is installed for both CLI and web Download and upgrade to the latest version (currently v4.4.2) - via CLI mode is recommended over /admin/upgrade in your browser Since you are on php 7.2, you will need to overwrite a few files from the "blesta" directory with all the files in the "hotfix-php71" directory. You will receive ionCube errors if you do not do this Upload the contents of the "blesta" directory, which now contains the overwritten files from the "hotfix-php71" directory Run the upgrade script (via CLI is preferred) Check your Blesta installation to make sure it is working normally on v4.4.2+ Update configuration settings, like cron jobs and email templates, if necessary, since many changes were made since v3.6.2 Backup your Blesta installation and database again, now, v4.4.2+ Perform your server/cPanel migration as necessary Be aware that changes to your Blesta location (e.g. by domain or subdomain) may necessitate that you update any third-party configuration to point to the new location. e.g. PayPal IPN URL Log in to your account with us, or your reseller, and reissue the license Click to "Manage" the service representing your Blesta license, check the "Reissue License" checkbox, and submit Visit your Blesta installation at your domain and log in. This will complete the license reissue at your new domain Re-enable the Blesta cron job and observe that it runs tasks as shown on the Settings > Automation page You may need to reconfigure the cron job to run at the new location if it has changed Disable maintenance mode  

You haven't applied the hot-fix it tells you there:
was encoded by the ionCube Encoder for PHP 5.4 and cannot run under PHP 7.1 or later. So you need the hotfix71. Copy the files from /hotfix71/blesta/ to the root of blesta.

cPanel (and essentially all other systems) will not send notifications to services (like Blesta) regarding a password update made through their system.
If the cPanel password needs to be changed, then the user should:
Change it from within Blesta, or Update it in Blesta after having changed it in cPanel

Our Hetzner Module in Chinese look very very nice ? in

There are two separate calls you need to make:
Create a ticket (as @Jono mentioned above) Create a reply for the ticket (as you did in your OP). FYI the first question from a customer that opens the ticket represents the first reply

we are proud to announce the release of our new module Hetzner Cloud Server, the module will allow you to resell hetzner cloud services with white label.
Features
Instant Activation of Cloud Server Automatic Suspension Automatic Unsuspension  Automatic Termination Unlimited Hetzner Projects Client Side
Reboot/Boot/Shutdown Change Hostname Change Root Password Reinstall Show Available IP address Admin Side
Reboot/Boot/Shutdown Change Hostname Change Root Password Reinstall Suspend/Unsuspend Cancel Create/Add Server Show Available IP address TODO List
Add/Remove Volumes (config Options) Add/Remove IPV4/IPV6 (config Options) Add/Remove Cpanel/Softacoulus License (config Options) Allow/Disalow Client To Use Backup Add Snapshot Feature  
ANY Suggestion , FeedBack , Bugs , Please Post it inthis thread .
this Module require a the Vip (GOLD) subscription .
Order Link
 

Yes, you can disable it similar to what is shown above in the configuration file using the plugin controller and method. But since it's in your plugin, you can always disable it from the source by calling Form::setCsrfOptions prior to Form::create, e.g.:
$this->Form->setCsrfOptions(['set_on_create' => false]); $this->Form->create();  

Are you referring to the plugin's cron tasks being active, or the plugin's cron task being run?
Blesta doesn't run plugin cron tasks if the plugin is disabled. I think this has been the case since at least v4.3.

The UTC timezone offset shown in Blesta comes from php's timezone database. You may need to update php to use the latest timezone database if Casablanca is no longer accurate because of a change in policy regarding the timezone.

Thanks! This will be fixed in CORE-3040 for v4.5.0.

If I were adding that myself, I would set an embed code for that specific order page from Blesta under Packages > Order Forms > (Settings tab). Refer to the docs for an example.

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'); } }