Jono

The Yandex gateway is now on github.  As noted in the README, Yandex is still developing their test suite and so this gateway is thus far untested for completing transaction through Yandex.  Transactions have been simulated and functionality local to Blesta has been tested.  Feedback is greatly appreciated.

CORE-2440.  Put simply, services use the package name unless they are told to use the module defined service name.  Probably this task will update them to do that.

Version 4.1.0 is now available. You can download directly right here.

Installing Blesta

See Installing Blesta in the User Manual for instructions.

Upgrading Blesta

See Upgrading Blesta in the User Manual for instructions.

Migrating to Blesta

See Migrating to Blesta in the User Manual for instructions.
 
Overview
Client language selector Out of quantity packages show out of stock on order form New required contact field client group option File based logging of actions and errors Packages no longer require a module New Modules: CentovaCast, TCAdmin, VestaCP, Virtualmin, and WHMSonic New Gateways: Alipay, and PayUmoney Custom language file and many new events/hooks for developers Plesk module updated to support Onyx Fraud checks are run for all orders whether client is new or existing New Importers: Clientexec, CSV (details) Updated WHMCS importer Release Notes

See Blesta Core - Version 4.1.0.

For older releases see all Change Logs.

The Yandex gateway is now on github.  As noted in the README, Yandex is still developing their test suite and so this gateway is thus far untested for completing transaction through Yandex.  Transactions have been simulated and functionality local to Blesta has been tested.  Feedback is greatly appreciated.

I have confirmed this as a bug (CORE-2447).
If you wanted to fix this yourself, in /components/gateways/merchant/stripe_gateway/strip_gateway.php on lines 336, 534, and 956 change
if (!isset($response['error'])) { to
if (!isset($response['error']) && empty($errors)) {  
 
That should prevent this kind of bug from happening.

I have confirmed this as a bug (CORE-2447).
If you wanted to fix this yourself, in /components/gateways/merchant/stripe_gateway/strip_gateway.php on lines 336, 534, and 956 change
if (!isset($response['error'])) { to
if (!isset($response['error']) && empty($errors)) {  
 
That should prevent this kind of bug from happening.

CORE-2439

i have made the change and i will watch the result.

Working on a full solution for this.  https://dev.blesta.com/browse/CORE-912 was meant to give customers the full amount of time they paid for, but I've confirmed that the changes made there are causing this issue.  As a temporary solution for this you can comment out the changes made to the cron for this task on lines 2569-2575:
'date_renews' => ($service->period != 'onetime' ? date( 'c', strtotime(date('c') . " +" . $service->term . " " . $service->period) ) : null )  

cron.php

Working on a full solution for this.  https://dev.blesta.com/browse/CORE-912 was meant to give customers the full amount of time they paid for, but I've confirmed that the changes made there are causing this issue.  As a temporary solution for this you can comment out the changes made to the cron for this task on lines 2569-2575:
'date_renews' => ($service->period != 'onetime' ? date( 'c', strtotime(date('c') . " +" . $service->term . " " . $service->period) ) : null )  

I was looking into this just now and I think this might be happening intentionally.  If we take a look at thesstore_plugin.php on line 212 we see:
$end_date = date('Y-m-d h:i:s',strtotime($end_date. '-30 days')); //set 30 days earlier renewal date I'll probably also leave a comment to Nick on the github issue I see you've created.

Created CORE-2313

Created CORE-2313

Quick update.  Instead of removing the id you can replace it with something unique like "ach_account" and make the same change to where it says "account" here.  This will make the label work properly for highlighting the field.  Minor difference.
$this->Form->label($this->_("ClientAccounts.ach_info.field_accountnum", true), "account");  

Quick update.  Instead of removing the id you can replace it with something unique like "ach_account" and make the same change to where it says "account" here.  This will make the label work properly for highlighting the field.  Minor difference.
$this->Form->label($this->_("ClientAccounts.ach_info.field_accountnum", true), "account");  

Quick update.  Instead of removing the id you can replace it with something unique like "ach_account" and make the same change to where it says "account" here.  This will make the label work properly for highlighting the field.  Minor difference.
$this->Form->label($this->_("ClientAccounts.ach_info.field_accountnum", true), "account");  

Fixed in CORE-2308
In the mean time if you would like to make the change effective before our next release you can modify /public_html/app/views/client/client_accounts_ach_info.pdt where it has:
<div class="form-group"> <?php $this->Form->label($this->_("ClientAccounts.ach_info.field_accountnum", true), "account"); $this->Form->fieldText("account", isset($vars->last4) ? str_pad($vars->last4, 9, "*", STR_PAD_LEFT) : $this->Html->ifSet($vars->account), array("id"=>"account", 'class'=>"form-control", 'placeholder'=>$this->_("ClientAccounts.ach_info.field_accountnum", true))); ?> </div>  
And remove
"id"=>"account",  

Fixed in CORE-2308
In the mean time if you would like to make the change effective before our next release you can modify /public_html/app/views/client/client_accounts_ach_info.pdt where it has:
<div class="form-group"> <?php $this->Form->label($this->_("ClientAccounts.ach_info.field_accountnum", true), "account"); $this->Form->fieldText("account", isset($vars->last4) ? str_pad($vars->last4, 9, "*", STR_PAD_LEFT) : $this->Html->ifSet($vars->account), array("id"=>"account", 'class'=>"form-control", 'placeholder'=>$this->_("ClientAccounts.ach_info.field_accountnum", true))); ?> </div>  
And remove
"id"=>"account",  

Just finished reviewing @timnboys code and we should get that merged soon.  Please let us know if you encounter other problems with the module.

Just finished reviewing @timnboys code and we should get that merged soon.  Please let us know if you encounter other problems with the module.

Just finished reviewing @timnboys code and we should get that merged soon.  Please let us know if you encounter other problems with the module.

The issue has been addressed in CORE-2221.  The decided upon solution was to prevent pending services from making any cancellation calls to the module when they are canceled.  This makes sense because when a user(admin or client) adds a pending service blesta will not make creation call to the module.