Leaderboard

Thanks Paul! my Clients are loving Blesta!

when the staff change status ticket or re-open a closed ticket , it show in the reply page a alert box with the info about the status changed and date . this info is not translated , i have searched some view files but i can't find where i can make it translatable . The status has been changed to XXXXX . Feb 14 2016 12:55 AM by mohamed anouar only the status is in multi-language mode . note i have translated all the language files . and tested with 3 languages . i don't have time to spend in searching files & files to find where this come . wich file i should look in it ? also i think this line should be in multi-languages format . also i norticed that the client side , the titles pages is not showed !!!

Not all gateways require you to be compliant but it is a good idea to be. The non merchant gateways do not require it and some of the merchant gateways don't, including Stripe, Paypal Payflow Pro and possibly others. When we used Bluepay, we had to be PCI Compliant. Not sure what you mean about the domain sales / api.

the payment button is not shown , so the user cannot proceed with the apply credit .

Good eyes! I've made the change and hopefully it works. Thanks again!

another issue is the payment_details , is hidden if payment by CC and ACH is not enabled in the system . normally it shouldn't exist in the view even if is hidden, as it never used it has no sense exist as hidden .

i have forget about this thread . Micke your solution will add a unique title for all the support manager pages . take this one , and every page has it own titles . in client_tickets.php controller under this line : $this->set("string", $this->DataStructure->create("string")); add : $page_title = Language::_("ClientTickets." . Loader::fromCamelCase($this->action ? $this->action : "index") . ".page_title", true); $this->structure->set("page_title", $page_title); now every page has it own title . also is better to add a new phrase language in clients_tickets $lang['ClientTickets.departments.page_title'] = "Support Manager > Select Departement ";

you have the s on {module.name_server}...

You should still store it in the session. What I am suggesting is that when you read it from the session, you set the configuration value afterward. // Selected language $language_code = $this->Session->read('language'); # # TODO: ensure the $language_code is a valid language in the system, # otherwise fall back to the default language # // Set the language Configure::set('Blesta.language', $language_code); Language::setLang(Configure::get('Blesta.language')); The end result is that these values are consistent: $this->Session->read('language') === Configure::get('Blesta.language')

While our commercial server provisioning module does suppport creating Vmware VPSes, I wouldn't recommend it, unless you are targetting the enterprise market (with enterprise pricing ). The license terms of the free version of Vmware ESXi do not allow you to sell VPSes, and commercial Vmware VSPP licensing is kinda expensive.