Paul

A cached invoice insures that the contact details for the client, should they be updated in the system, are not also updated in previous invoices. There is a staff ACL permission called "Edit Invoice". Unless a staff member has access to this, they CANNOT modify an invoice. If a staff member does have access to this, and edits an invoice, it will be re-cached at that time. So, I don't think this presents a problem. Do not let staff have edit access to invoices, and enable the invoice cache in 5.1 and invoices cannot change. Unless I'm missing something else?

There is a bug in Blesta 5.0, see https://dev.blesta.com/browse/CORE-4229 we have a task to fix this. If you are starting fresh, you could install Blesta 4.12.3, import your ssl packages, then upgrade to 5.0.4, but obviously that's more work. We hope to have a fix for this soon.

The currency shows KES, but on the order form it's shown as Ksh. Are these the same? Is your Default Currency set to KES under Settings > Currencies > Currency Setup? If these are not the same currency, then there is something wrong with the exchange rate under Settings > Currencies > Active Currencies.

Yes, you can do that, however because there are far more database migrations that need to be performed over such a large jump, there is a higher risk of your web server timing out if you perform the upgrade via web (accessing /admin/upgrade and clicking the button). Upgrading via CLI command, would be less likely to encounter an issue. If you are running version 3.x, there are steps needed if upgrading to 4.x. See https://docs.blesta.com/display/user/Upgrading+Blesta We would recommend in that case following these steps, and going to 4.0 then from 4.0 to a newer release. Always make a backup of your FILES & DATABASE, and be prepared to restore them if anything goes wrong in the upgrade. Also, if upgrading to 5.0.4, note that the System Requirements have increased. If your server doesn't meet the minimum requirements, the upgrade will fail.

/logs_blesta/ is an unusual place for the log directory. Since your docroot is /var/www/html/ it would normally reside in /var/www/logs_blesta/ The warning about the ownership not being the same, is probably a result of your web server running as a different user as your cron user. The cron should, ideally run as the same user. Then, when it writes log files, they will be owned by the same user, and there won't be any potential for conflict. In v5, we write cron logs with a different name, so it's not a serious issue, but the warning remains.

Oh, make Blesta match? That requires integrating your website theme into Blesta. Most of the time people just edit 1 file, /app/views/client/bootstrap/structure.pdt which contains the header and footer for Blesta. If you have any custom CSS we recommend creating a new overrides.css file and loading it in structure at the end, and putting your styles there. You can get more help on this via people on our Discord, and there are companies that can do this integration for you for pretty cheap.

In docker the IP often changes, when that happens the license will need to be re-issued. If you can pin the IP in docker, that should prevent license issues. Glad that you found the cause of the blank pages.

It looks like your price is 0, and as a result the total is 0. What are you expecting to see?

I'm not sure what you mean by adding html pages. If you want to create pages that are part of Blesta, then you may be interested in the 3rd party BlestaCMS plugin. Otherwise, I would recommend keeping your website content pages separate from Blesta. You can create navigation links in Blesta if you want to link to external content from your website under Settings > Look and Feel > Navigation.

Under Settings > Company > Currencies > Active Currencies. Edit. Change the precision to the desired value, like 2.

We would recommend using a different subdirectory name, or switching to a subdomain like my.domain.com, billing.domain.com, or domain.com/billing/ that way the client area would be at my.domain.com/client/ or domain.com/billing/client While you can change the client route, and change the name of the client path, it would be a conflict to load it at the root of the installation. Also - welcome!

Attached is an updated version of the import manager. Some users experienced some issues with special characters not being imported correctly from WHMCS. If you experienced this issue, try this import manager. Download, unzip, and replace the default files in /plugins/import_manager/, then install or upgrade under Settings > Company > Plugins. Follow the docs to import here: https://docs.blesta.com/display/user/Migrating+to+Blesta UPDATE 4/16/21: Now imports Stripe tokens and adds mapping files for the following Gateways: Stripe Payments, Authorize.net, PayPal Payments Standard. UPDATE 5/4/21: Fixed issue importing from WHMCS versions older than 8.0. import_manager-2021-05-04.zip Some have reported that the link above does not work for them. If not, you can download it at http://blesta.us/import_manager-2021-05-04.zip

You might consider porting these over to the official Messenger system. See https://docs.blesta.com/display/dev/Messengers It currently only supports order notifications and ticket notifications, but more will be added.

We are considering automatically removing the copyright if the license is unbranded... or adding a checkbox to disable it in the settings. I don't know about loading some other text from the database though, it would cause another query for every page load.

Yes, Blesta can be installed on Windows. You don't need to run composer, it looks like you are missing some files. Download Blesta 5.0.4 from here https://account.blesta.com/client/plugin/download_manager/client_main/download/180/blesta-5.0.4.zip Unzip, the contents of the "blesta" directory should go to where you want to install Blesta, and the uploads directory above your docroot.

It does appear that the user may be lacking some permissions, check that the user has all privileges. The logs you attached don't seem to be related. What version of PHP are you running?

Did you run /admin/upgrade after replacing the files? A blank page is most often associated with an error, usually a MySQL error when it happens as a result of upgrading. It's safe to run /admin/upgrade again if you already did. If you ran /admin/upgrade and still get the white page, check your error logs, typically at ../logs_blesta/ What is written to the logs when you get the white page?

Super weird, but glad to hear it's working!

I PM'd you a trial key.

Did you have any errors in ../logs_blesta/ also, from the import? The first error usually kicks off the others. In this case, it looks like a contact is trying to be created that may not be associated with a client_id. Do you have any contacts in your WHMCS database that have a null client_id? Not associated with a client? If so, this is likely the reason.

I believe the service becomes "active" in Blesta if the transfer is initiated and the registrar returns a successful response to the API command. This doesn't mean the transfer has been completed, only that it's been initiated. Your cron command would potentially be useful for checking whether the transfer has failed, but I would expect the service status to be "active" during that process. Maybe that's not the best way to do it, but I'm pretty sure other modules behave this way currently.

A white page indicates an error, it's likely that you've saved something in the template that is not acceptable. If you are using styles, they should be inline. Regarding the logo not appearing in emails, many mail clients will not load external images by default unless the user select to do so. If that is not the issue, have you checked the source of the email to see if the image is linked correctly?

I'm not sure I understand, what is the full path to your document root, where is Blesta installed, and where as the logs_blesta directory created? logs_blesta should always be created one level above document root.

If this is for embedding an HTML table into your own website that has the pricing, we have created a task here for that https://dev.blesta.com/browse/CORE-4213 and will implement in a future version.

Here's the task: CORE-4213