Tyson

What do you mean check log in status? Session information is not going to be available over the API. You're not going to be able to determine whether they are logged in unless you log them in, which you can do from the Shared Login plugin.

Looks good! One thing you could do in the future to improve on this is to create a plugin for Blesta that accepts an IP address and uses the GeoIP2 database already supported by Blesta to determine the country (i.e. replaces the geoplugin.com file), then your plugin can do the mapping and return the appropriate currency for the country.

I just tested this and didn't encounter that issue. One thing to consider is that if you are an admin whose language is set to English, you will see English even when you log in as a client whose language is set to Spanish. The client will see Spanish when they explicitly log in to their account (i.e. when you are not an admin masquerading as a client). Another thing to consider is that when the language has not been completely translated in Blesta, there may be definitions that do not exist in Spanish, and so they will fallback to English.

If your support department is set to an "Email Handling" value other than "None" then the Mailparse extension is required, but it is not loaded in your php, hence the error.

We update translate.blesta.com with any changes to language definitions shortly after a Blesta release. Normally, these occur when there are major or minor versions released (e.g. 4.5 or 4.6), but not usually for patch releases (e.g. 4.5.2). Patch releases don't typically have differing language definitions.

If no one else has that problem, then it might be your computer. Have you tried clearing your web browser cache? Have you tried using a different web browser? Are you sure all of the files exist on the file system, in particular, the CSS files? Do you have any custom code that might conflict with the CSS?

You may want to contact @Jonathan since he created that module.

For both of those questions, when you are managing the service in Blesta, uncheck the "Use Module" option. This will cause the action to be performed in Blesta, but will not notify VirtualMin via the API. Also when managing the service, there should be input fields for domain, username, and password. You can enter those in Blesta as they are set in VirtualMin and save them. Just remember to uncheck "Use Module".

It looks like the "input" fields have no border. You may have some custom CSS that disables the border for "input" fields.

$data = [ 'username' => "username", 'vars' => [ 'username' => "username", 'password' => "password" ], 'type' => "any" ]; $response = $api->get("users", "auth", $data, "any"); The parameter names are the keys to the array you pass as $data.

A credit is a payment transaction that is not applied to any invoices. On that "Record Payment" page, simply enter the payment amount, but do not check any invoices to pay from the list. In that case, a transaction will be created and it will not be assigned to any invoices, therefore it will appear as available credit.

The error sounds like a web server issue. You may want to debug the web server to see what is causing the issue (e.g. low resources or bad configuration?) Blesta didn't complete provisioning the service because the error occurred in the middle of the process. If you check your module logs for this action, you may see a request was sent to VirtualMin to create the service, but no response was received back from VirtualMin to tell Blesta the service was provisioned. In that case, you should be able to Manage the service as an admin and set the domain, username, and password for the service in order to match the service credentials in Blesta with the credentials in VirtualMin. Be sure to uncheck 'Use module' when you do this.

Take a look at Users::auth.

Have you taken a look at the module log after you select the CentOS Web Panel module from the Add Package page? The module log will contain the raw input/output data that may give more information on any errors you're encountering.

Enable error reporting temporarily so you can observe what error you're encountering, if it's from php. Then we'll have a better direction to go on fixing it.

There are no more translations saying "A Google translation is currently unavailable." You may see those in archived ZIPs, but not the latest one built every night. We've also now removed several other translations, like "Google Übersetzung", and any that are very obviously inaccurate. The next nightly build will have these removed. Not currently, but I would like to make this easier in the future. You would currently have to find the specific definitions as you continue translating.

You can create a plugin that registers an automation task. It can run automatically by cron at whatever interval or at any time frame you want. When your plugin's automation task is run, you can change the theme for the company. Take a look at the source documentation for Themes::change regarding changing the theme. There are also methods for fetching the available themes so that you can pick one from the list to change it to.

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.

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.

Since you were able to get a different cPanel server to work correctly, I think you've isolated the problem to either that cPanel server or its response. It is possible the response from cPanel could be too large for Blesta to handle in the log, which could be the reason Blesta does not log the issue or save the service as created. This can occur on Blesta before v4.5.0. You can check your MySQL logs for errors to confirm. I would recommend upgrading to v4.5.1, if you aren't already using it, and try again.

It looks like they only support creating subscriptions right now, since they discontinued their previous PDT flow. Do you have any idea when they may release a one-time payment option? I think we would like to integrate both of those at the same time for a non-merchant gateway.

API Documentation?

/components/invoice_templates/*/language/ Search your files for /language/ directories. The invoice logo is scaled down to a width of 140px and a corresponding scaled height.

No, not currently. The system generates the invoice first and then applies the payment to it when/if it is received.

A re-issue typically depends on the module and it's re-issue support, and modules are not callable via the API. Assuming the module supports re-issues, you would probably want to call Services::edit via the API and pass in the re-issue field(s) so that the module will be called and can perform that action on the service.