Leaderboard

Blesta version 4.0.0-b4 (BETA 4) is now available. You can download it from right here (Client Area Login Required). If you haven't seen the blog post announcement for 4.0.0 BETA 1, you can read it here. This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.0.0-b1-b4. SEE BETA 4 ONLY For older releases see all Change Logs. What to Test! 1. PHP 7. The focus of this beta was largely PHP 7 support. Check change log for more. Known issues 1. An error is encountered when logging in or out with PHP 7, if errorReporting is enabled in /config/blesta.php

Ok so check the following: 1. Check that the PayPal gateway has been installed and set-up correctly. 2. Check the currencies accepted by PayPal. 3. Check the order form ensure "PayPal" is checked and that the currencies are selected. Then try again, also try "Making a payment" manually by clicking the button on the client area. It should show up on the right hand side.

I'm not sure what needs to be done with the domain registrar modules but I see that Enom has new API information and I would guess other providers do as well: http://www.enom.com/domains/new-transfer-policy/

Only clients can pay with non-merchant payment gateways. Login as the client, or checkout as a client.

I don't recommend downgrade, Older versions have more security issues.

i have re-run the upgrade again and it was fixed now .

When you create a contact you can set permissions for the contact. Both staff, and clients creating sub-contacts. These are not the same as Staff ACLs, but should be sufficient for most cases. In this screenshot, the "Support" permission is from the Support Manager plugin, so you should be able to accomplish what you want with your Cerberus integration.

i will add this to the next version of clean unpaid orders plugins .

Most people won't know that it would break anything by changing the module. Most people won't write a new module with the same meta fields, and want to switch it over. I agree there should be a way to do this, disabling module changes was the simplest way to stop unaware people from making a change that would negatively impact their installation. If you're able to write a module, it shouldn't be too hard to write a query to update the packages to use the new module. In the future I'd like to create more separation from packages and services, and then we can safely allow the module to be changed.