Tyson

Plugin-defined menu items in the navigation have static language defined in the database under the `plugin_actions` table. They are not currently translated based on the user's language, so whatever language it is in will be displayed for everyone regardless of language. See also this thread.

Blesta won't know what password requirements you have set in DirectAdmin, so it couldn't enforce them. What we can do is increase the password requirements to require the default DirectAdmin "difficult password enforcement": minimum 12 characters at least 1 upper-case character A-Z at least 1 lower-case character a-z at least 1 number 0-9 at least 1 special character from !"#$%&'()*+,-./:;<=>?@[\]^_`{|}~

Do you still encounter this issue? I wasn't able to duplicate it. In my case, I was using the Namecheap module to register a domain, but with the Wizard List template I was able to complete checkout as expected.

Does Alipay require you to enable API access in their system? The error "Incorrect Partner ID" is the response from Alipay when Blesta tries to request to make a payment. Are you using an Alipay Sandbox account? If so, you need to check the checkbox "Developer Mode" when managing the gateway in Blesta.

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

Per CORE-1232, this is an issue with ionCube and won't be fixed in Blesta. Pass NULL for the key and iv to use the default system key.

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.

Could you provide some details on the coupon's configured settings? Does this only happen on the order form, or when you add the service from the admin interface? If you are able to duplicate the issue, can you provide detailed steps to enable us to duplicate it ourselves?

The SupportManagerTickets model defines input validation rules and what table columns can be saved during an add/edit. My guess is you need to update that model to allow it to save your new columns. Any time you update code to add customizations you risk them being overwritten during updates, so I would encourage you to maintain your own repository of your changes and merge in any updates when you upgrade Blesta so that you keep the plugin up-to-date and working with your customizations.

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.

Unfortunately, there isn't a way to have the setup fee be a multiplier of the variable quantity without updating the source code to essentially add that feature in. If the option could have a static quantity then you could have a static setup fee cost associated with it easily.

It's unlikely we will add support for AJAX order templates to process credits any time soon. That template was not designed to support that option.

Setup fees throughout Blesta currently apply only once and do not themselves have a quantity. This is something we're considering updating to allow a setup fee to apply only once or based on the item's quantity, but that behavior is not settled upon yet.

I believe the CKEditor JavaScript file must also be set to the view in the appropriate controller, e.g. $this->Javascript->setFile('ckeditor/ckeditor.js', 'head', VENDORWEBDIR);

Thanks, this is CORE-2828.

I appreciate the report and we are aware of concerns some have expressed (such as here) with the tax types in some regions. The difference between inclusive/exclusive on the tax rules is purely visual--the tax is shown in the total (inclusive) or it is not (exclusive). We will need to include additional support in the future for package pricing to support "price includes tax" or "price excludes tax", as you are alluding to.

I assume you mean Blesta v4.3.2 (not 3.4.2). There are known issues with Blesta on php 7.2 since php 7.2 now raises errors it did not do before. In any case, the sessions have already been updated in the framework for minphp-bridge and minphp-session. You can overwrite the respective code in your Blesta's /vendors/ directory with the latest tags from those repositories. These updates will appear in Blesta v4.4.0.

Since that plugin's upgrade script failed in the middle of execution, not all of the database changes were made. In this case, you should do two things: Update your config file as I mentioned in my previous post Run the following query on the database: UPDATE `plugins` SET `version` = '2.13.0' WHERE `dir` = 'support_manager' ..then manually upgrade the plugin again.

I'm sorry to see upgrading isn't going very well for you today. Normally there aren't so many issues. It looks like the database server is rejecting a query attempting to add a new date column to the support_tickets table without being null because it's running in strict mode. I suggest restoring and reattempting the upgrade again, but before you do, update your config file (/config/blesta.php) and change the sql_mode to a blank string. i.e. find and change: 'sqlmode_query' => "SET sql_mode='TRADITIONAL'", to 'sqlmode_query' => "SET sql_mode=''", (remove the word "TRADITIONAL") After the upgrade completes, revert this config file change.

Sounds like another table (i.e. system_events) exists, probably from a previous incomplete upgrade. I would recommend restoring the database backup from earlier, and then running the upgrade again. You'll want to make sure that you don't have either the service_invoices table or the system_events table prior to upgrading.

Make sure that you do not have a service_invoices table in your database prior to upgrading. If you do, drop the table, then run the upgrade again. If you still receive the duplicate key error, run the following query on your database: SELECT COUNT(`invoice_lines`.`invoice_id`) FROM `invoice_lines` INNER JOIN `invoices` ON `invoices`.`id` = `invoice_lines`.`invoice_id` WHERE `invoices`.`status` IN ('active', 'proforma') AND `invoice_lines`.`service_id` IS NOT NULL AND `invoices`.`id` = 5 AND `invoice_lines`.`service_id` = 13 GROUP BY `invoice_lines`.`invoice_id`, `invoice_lines`.`service_id` If the result is anything greater than "1" then your database server may not be grouping the result set properly, which explains the duplicate key error since there should be no duplicates in the result. I can't readily explain why that would be, but you could update the upgrade script to ignore duplicates, which should have no adverse effects with the upgrade script. To do so: Update /components/upgrades/tasks/upgrade4_1_1.php At the bottom of that file should be a line: 'INSERT INTO `service_invoices` (`invoice_id`, `service_id`) (' . $sql . ');', Change that to: 'INSERT IGNORE INTO `service_invoices` (`invoice_id`, `service_id`) (' . $sql . ');', That is, just add the word "IGNORE" after "INSERT". Then run the upgrade again and see if it is successful. If so, take a look at the service_invoices table to ensure you have some records and everything should be fine.

Have you taken a look at the documentation regarding email piping?

Just wanted to chime in here that the Blesta version 3-series (e.g. v3.6.0) will never support php 7+. It simply can not. There are backward incompatible changes introduced in php 7 that prevents Blesta v3.6 from being runnable on that version of php. In order for Blesta to support php 7+, Blesta must be updated to resolve those backward incompatible php 7 changes, and in so doing has to introduce backward incompatible changes in itself. This means that in order to support php 7, an update to Blesta requires a major software release (i.e. moving from version 3.x to version 4 following semantic versioning standards). This is precisely what we did do by releasing Blesta v4.0, and with that version you can run php 5.4+ or php 7+ using the provided ioncube-encoded files for php 5, php 7, or php7.1+ respectively. Ioncube itself does not support php 7+ with its php 5 encoded files, so that's why different encoded files must be used for your particular php version.

Is it possible for you to tie into the Appcontroller.structure event and set hidden HTML along with JavaScript that moves it to the location you want on page load?

I'm not sure what you mean by this: As for the idea of falling back to the default template if a file is unavailable, that may be something we could support in the future.