Paul

When an error occurs, it's not able to complete the import. It's important to correct the issue, re-import on your fresh Blesta database (why we recommend backing up Blesta after installing, then restore your database backup before attempting another import). I would also recommend importing from a cloned WHMCS database so that you can make adjustments to your database. For example, one error was a currency code longer than 3 characters. You'd need to modify any currencies longer than 3 characters to be 3 characters, then retry the import. Same goes for any contacts that are not associated with any clients.

Importer is trying to import a contact that has no client id associated with it. You may have some contacts that are not associated with a client in whmcs, check your database to see. whmcs does very little to enforce data integrity, so when something is expected to exist and it doesn't it causes issues.

Do you have any currencies in whmcs that are longer than 3 characters? currencies.code is limited to 3 characters in Blesta, under the standard, currencies should be 3 characters.. like EUR, USD, CAD, etc. Looks like you may have one that is longer than this in your whmcs.

In your GoCardless gateway configuration (see https://docs.blesta.com/display/user/GoCardless?preview=/10551346/10551350/gocardless-installed.png) have you updated your GoCardless account to use the Webhook shown here? Is your Webook Secret and token correct also?

So you want to pad the invoice to have a certain number of characters? For example, a padding value of 8 would cause the number portion of the invoice to contain 8 characters, e.g. 00000001 00000002 ... 00001234 Then if you prepend the date year in the front you might have: 201900001234 Is that what you are looking for? This could potentially be a setting under Settings > Company > Billing/Payment > Invoice Customization.. but what happens if your invoice number exceed the padding length? For example you have 99999999 what's the next number? Does it expand to 9 characters?

To confirm, under Packages > Package Groups, when clicking on the group and it expands to show the Member Packages, only the Package Name is shown. You want to see the Module and Quantity also? I'll look into that, thanks for the suggestion. This is the number of days after an invoice was already due and the service is cancelled to void the invoice. 0 means that the invoice can't be past due. I would recommend selecting a higher number, like 30 days, but you should base this on your settings for suspending & cancelling services automatically. If unpaid services get cancelled 21 days after the invoice is past due, then you should set this to 22 days or more.

Regarding affiliates, we hope to have an official plugin ready for that soon. In terms of core changes, if they are consistent with the overall direction of Blesta, we would be open to adding those to the core as part of sponsored development. This would make upgrading much simpler in the future. Reach out to sales@ if you want to discuss that in more detail.

Under Packages > Package Groups you can click a group row to expand and show all packages within the group. Sounds like this is the view you want to see? If you have any specific suggestions on how to display packages instead, let us know. This is fixed in https://dev.blesta.com/browse/CORE-3307 for 4.7.2 and 4.8.0 Do you have an example of that email? What is included in this summary email and how often is it sent? Who is it sent to? We recommend marking any packages that are no longer in use as "inactive". We may allow linked packages to be deleted in the future, right now having a cancelled service linked to a non-existing package would be untidy in the database. Thanks for the feedback. If you update services that are currently using the price option to use a different price option upon renewal, the price will be able to be deleted. Under Settings > Company > Billing/Payment (check also client group which can override): Void Open Invoices on Service Cancellation Then check the number of days an invoice can be past due to void the invoice. This will cause the invoice to be voided and the customer will not be able to pay it. Whether a service could technically be re-activated once it's cancelled really depends on the module. If a cPanel account were cancelled, re-activating would require a new account to be created. This may be what is intended, or it may not. The ability to re-activate a cancelled service is something we will likely be adding, but there is some concern about how to approach this, whether to activate through the module or simply change the status back to active in Blesta.

Yes, if you are using piping you pipe all of the addresses you want to use to pipe.php as described in the docs. Blesta will detect the email address the email is addressed to and open a ticket in the support department that matches, based on the way you have configured your departments.

Not exactly sure what you mean by ticket category. You can have multiple departments. The auto-reply for each department is generally the same, from the template "Ticket Received", however you can use logic in the template to display a different message based on the department. See https://docs.blesta.com/display/user/Support+Manager by using the tag {ticket.department_id} and a Conditional Statement. As an example: {% if ticket.department_id = 1} Enter text to be shown if the department ID is 1. {% endif %}

If it works fine without the logo, you can try re-saving it differently and try again. For example, if using Photoshop do a File -> Save for Web. If your are using a JPG try exporting as a PNG instead. If using a PNG, try a JPG. If using a transparent PNG, try no transparency. There is something TCPDF doesn't like about your file, one of those changes will likely get around the issue.

Does this happen to all clients or only some clients? If some, what's the difference between them? TCPDF may be ignoring the temp directory defined by Blesta to write this file. Sometimes TCPDF uses the GD library, so make sure that's active. You may also try removing your logo and background image on your invoices to see if that makes a difference. Could be TCPDF trying to modify those images and failing for some reason. If you are under a jailed environment, try disabling that to see if it makes a difference.

You should try the full path to PHP. Normally this is detected in Blesta and shown under Settings > System > Automation. If your server has multiple PHP interpreters, the full path is absolutely required so that you're running the same version of PHP. If you have SSH, you can try running: php -v To see what version of PHP is in the default path. Then try using the full path to php with -v to see if it's different. Also check your Blesta logs ../logs_blesta/ (Defined under Settings > System > General) to see if any errors are written to disk when the cron run is attempted.

By default /tmp/ is used which references the server's temp directory, sometimes things get in the way of writing to that directory even though it appears to be writable, like Cloudlinux, jailed environments, etc. To test, with a test client that uses your email address, create an invoice or edit an invoice and check the "Email" box to queue it up for delivery. Wait to see if you receive a single copy of it. Your email delivery task should be set to run every 5 minutes. If any clients have been getting spammed, before changing this back edit their invoices and uncheck the "Email" box so that they are not queued to be delivered to them.

Looks like it's trying to delete temporary invoice PDF files and that they don't exist. This may indicate a problem writing them. Your temp directory (Settings > System > General) appears to be set to /tmp/. Does your server prevent your Blesta cron user from writing files to this directory? If so, you may want to relocate it to something like /home/user/temp/. To do so, create the directory above your document root, and update the path in the settings. Make the directory 777.

What version of Blesta are you running? The file logs are not the same as Tools > Logs. Look at Settings > System > General for the Log Directory path. If it's not set, create a directory above your document root and set the path here, make sure the directory is writable. chmod 777 if you are unsure. After the cron runs, check the directory on your server and review the files for any errors at the time your Deliver Invoices task ran. These invoices just not being listed under Tools > Logs > Invoice Delivery just confirms that the email delivery appears to Blesta to have failed, which is why it re-tries.

If the invoice email results in an error or time-out when sending, Blesta thinks it was not successfully sent and retries at the next run. The invoice is not marked as sent. This should be every 5 minutes, so be sure to change it back when you fix the real problem. You need to figure out why Blesta thinks the email isn't sent. Since you moved Blesta, the first thing I would do is check to make sure you moved Blesta correctly. See https://docs.blesta.com/display/user/Moving+Blesta, especially the following warning: Then check your Blesta logs, ../logs_blesta/ defined under Settings > System > General. Look in the log files to see if there are any errors when your deliver invoice task runs. Make sure your server meets the minimum requirements for Blesta.

This sounds like a contract where the customer commits to 2 years, so you wouldn't want to allow cancellation before that. At which point it could either renew month to month or under another contract. We're not opposed to this idea, but it needs to be fleshed out. I would recommend a feature request that includes as much detail as possible https://requests.blesta.com

Just FYI, we are looking to implement this, probably as a core change. See CORE-3024

That's a really good article, kudos to Rack911. Thanks for sharing!

Step 3: Hostname by definition would include anything.domain.tld. If we just said "Domain" I could see how that would be incorrect, which would be different than hostname. What would you suggest we add for more clarity? Blesta detects the hostname during installation automatically. When moving Blesta if the hostname changes it must be updated, which is indicated in the documentation. Not sure what we can do to improve this. Suggestions welcome.

It's mentioned in the documentation on Moving Blesta Final Steps > #3 for hostname, and #2 for updating path settings.

I also suggest running this code to make sure stripe can respond. Must support tls 1.2 https://docs.blesta.com/pages/viewpage.action?pageId=10551368#Debugging/Tools-CheckPHPCURL,outboundTLSVersion

Hostname is the FQDN, if you are using a subdomain then that must be included.

Version 4.7.2 is now available, please see the release announcement. Patching Blesta See Patching Blesta in the User Manual for instructions. 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. Release Notes See Blesta Core - Version 4.7.2. For older releases see all Change Logs.