Paul

Yes you can upgrade. Download the patch version here https://account.blesta.com/client/plugin/download_manager/client_main/download/176/blesta-5.0.0-5.0.2.zip Unzip and upload the contents of the "blesta" directory to your server, overwriting existing files. Then access /admin/upgrade in your browser and click the upgrade button.

Great work!

Maybe @Jono or @Abdy will have more information on this. However, I think additional auth steps for Stripe might be referring to SCA, but Stripe should handle this.

Looks good, thanks for sharing!

That's correct. If changing the theme, the logo, if set, will have to be re-added.

What specific features are missing?

Thanks for the update, an incompatible extension will do it.

Sounds like the content you entered into the package for the welcome email content contains errors. If you post a copy of your email content, we may be able to tell you what the issue is, but once you correct it it should save.

What was the solution? A couple things come to mind: If the cron runs as a different user as your web server, the ../logs_blesta/ logs directory will not be writable by the web server, or by the cron, which can create various issues Your uploads directory exists and is writable, but is missing some child directories. Here's some details and an outline what that structure should look like: Make sure your uploads directory exists and is defined under Settings > System > General: Uploads Directory. Some tips: - The uploads directory should be above your document root or public_html directory so that it's not accessible directly via the web. - A common path to the uploads directory would be something like: **/home/user/uploads/** - Make sure the uploads directory is writable by your web server and cron users. 755 permissions are usually sufficient, but you may need to set it to 777 - Inside the uploads directory, you should have a directory called 1 (for the company ID), and system. - Plugins typically create their own directories within your company ID directory, but you may need to create them manually. These are the directories you should have under uploads: └── uploads ├── 1 │ ├── download_files │ ├── invoices │ ├── mass_mailer_files │ └── support_manager_files └── system

What version did you update from and to? Did you run /admin/upgrade in your browser, or via the command line? Blank pages mean there is an error, you should check your error logs, typically at ../logs_blesta/

Yes

Thanks for the detailed post. If we implement PayPal Checkout, it would be as a new gateway and wouldn't directly replace PayPal Payments Standard. Users would be able to decide which to install and use. Whether it's technically possible will require a little more research and detailed review of the API documentation. It looks like I created a task recently so we could look into this, per CORE-4084.

Also check that a text version of the email is defined on the Package Welcome Email section. The HTML should be converted to text if it doesn't exist, but it's better if you set it. The logs only show the text version of the email.

Please email sales@ and mention that you'd like to evaluate Blesta under localhost, and include the hostname that you will install Blesta under if you decide to purchase.

Your php.ini has an open_basedir restriction. The best solution is to edit your php.ini, find the open_basedir line and remove the values.. open_basedir = If you want to keep the restriction, you should add all of the paths mentioned in your error to the value.

Yes, absolutely. To add a custom client field go to Settings > Company > Client Options > Client Custom Fields and click the [+] button. Make sure that the Client Group you want it to appear for is selected.

I don't have a working copy in front of me so I can't say for sure, but I *think* it will log them in automatically if their credentials in Blesta are correct. But if they log into Directadmin's panel and change their password there, then it would no longer work.

There is a log in link there yes, but it doesn't yet use single sign on like cPanel.

Open this file to change the requirements: /components/modules/direct_admin/config/direct_admin.php Configure::set('DirectAdmin.password_requirements', [ ["A-Z"], ["a-z"], ["0-9"], ["!", "\"", "#", "$", "%", "&", "'", "(", ")", "*", "+", ",", "-", ".", "/", ":", ";", "<", "=", ">", "?", "@", "[", "]", "^", "_", "`", "{", "|", "}"] ]); Configure::set('DirectAdmin.password_length', 12); As an example, you can change the length requirement to 10, and eliminate the need for a special character by changing it to: Configure::set('DirectAdmin.password_requirements', [ ["A-Z"], ["a-z"], ["0-9"] ]); Configure::set('DirectAdmin.password_length', 10); This would require capital letter, lowercase letter, and a number, that's 10 characters long. Adjust as necessary.

Both work very similarly. Management just means extra options under the Manage button for the client. For shared hosting panels, users can just login to the panel to perform actions so it's usually not an issue. For Config Options, it just means that the module is not expecting any configurable options that would change the way it provisions the account through the DA API.. for example, extra disk quota, mailboxes, etc. That's not supported, so the accounts will be provisioned based on your Package settings.

The widgets are loaded via AJAX but they should be using the same hostname for those requests. I'm not sure why your security policy would have an issue with that, or what the proper solution would be. I guess the question is, what does the rule require, and why does the loading of widgets violate that rule? I suppose you should double check that the hostname is correct under Settings > System > Companies: Edit.

"Order Other Items" is essentially the same as "Use my own", they would just provide their domain name after they select a hosting plan rather than before. You can change the text in the language files under the plugin /plugins/order/ if you want to re-name that button. If it should work differently than "Order Other Items", you can create a feature request at https://requests.blesta.com

Did you upgrade via CLI? If so, it should show the step number. That will be helpful for getting you accurate next steps to complete the update. Feel free to open a ticket with those details, a ticket will get a much quicker reply.

Awesome, it looks really nice! Do you have a dev license from us? An account with dev license will allow you to post on the https://marketplace.blesta.com site when it's ready.

Some people have experienced issues upgrading to 5.0.0. We will be releasing a 5.0.1 patch sometime next week. If you haven't upgraded yet, we would recommend either waiting for 5.0.1, or replacing the /components/upgrades/tasks/upgrade5_0_0_b1.php file from 5.0.0 with the one attached to this thread. This attached file will gracefully handle some commonly experienced issues, and the last task, "updateDatabaseCollation" is commented out so that it will not run. When you eventually upgrade to 5.0.1+, you'll be able to update your database collation in Blesta under Tools > Utilities. If you want to run the collation task to upgrade your database from utf8 to utf8mb4, you can uncomment line 66 from the attached file. You should only do that if you are running MySQL version 5.7.7, or MariaDB 10.2.2 or greater. upgrade5_0_0_b1.php